Bugs and Requests
Lots of good stuff is coming...CoolColJ wrote:please, please, allow support for custom Nk files and user entry of Nk files!
You have mentioned often how SU lags with high-poly models. I agree that it sucks but do you not use layers? Also, turn off textures and profiles. Why don't you use dummy components for your alien artifacts? It seems like you have finished modeling them and are just playing around with different settings anyway.
Another thought: I think SketchUp disables hardware acceleration by default (I don't know why...) Be sure that it is turned on in your SU settings.
Sorry if these ideas are no-brainers...maybe someone else might find them useful if they don't help you.
Cheers and thanks for the feedback...
Yeah I layer most of my stuff now and turn em on and off. That's ok, but it doesn't really help much in the right button click lag or the menus and such. And if I want to scale the high poly object or select it, then things die pretty quicklyWhaat wrote:Lots of good stuff is coming...CoolColJ wrote:please, please, allow support for custom Nk files and user entry of Nk files!I will be sure to include support for custom NK files soon.
You have mentioned often how SU lags with high-poly models. I agree that it sucks but do you not use layers? Also, turn off textures and profiles. Why don't you use dummy components for your alien artifacts? It seems like you have finished modeling them and are just playing around with different settings anyway.
Another thought: I think SketchUp disables hardware acceleration by default (I don't know why...) Be sure that it is turned on in your SU settings.
Sorry if these ideas are no-brainers...maybe someone else might find them useful if they don't help you.
Cheers and thanks for the feedback...
Dummy components will help once I get everything set, which I should try, as I haven't used that feature yet....
SU is such a great program, but Google have got to optimise and overhaul the code!
Whaat -
There is some issue I've had with the UV indexes. I only noticed it recently when I started to play with this scratch map
the scene renders as it should with all my UVs saved and properly assigned, but the next time I load up the scene and export the scene out, the scratch map UV is rendering differently. Then when I reload the indexes for that material and export out again it renders fine
I thought the UV and assigns were saved with the scene, so is it a bug?
I used the same map on mulitple things BTW, bump, exponent, clip mapping etc
There is some issue I've had with the UV indexes. I only noticed it recently when I started to play with this scratch map
the scene renders as it should with all my UVs saved and properly assigned, but the next time I load up the scene and export the scene out, the scratch map UV is rendering differently. Then when I reload the indexes for that material and export out again it renders fine
I thought the UV and assigns were saved with the scene, so is it a bug?
I used the same map on mulitple things BTW, bump, exponent, clip mapping etc
Multiple UV sets are buggy when applied inside groups or components. You may also get weird results if you are rendering while 'inside' group edit mode.CoolColJ wrote:Whaat -
There is some issue I've had with the UV indexes. I only noticed it recently when I started to play with this scratch map
the scene renders as it should with all my UVs saved and properly assigned, but the next time I load up the scene and export the scene out, the scratch map UV is rendering differently. Then when I reload the indexes for that material and export out again it renders fine
I thought the UV and assigns were saved with the scene, so is it a bug?
I used the same map on mulitple things BTW, bump, exponent, clip mapping etc
Try exploding the geometry before saving the UV sets, then see if it works.
There are still lots of bugs with the UV mapping code. The most reliable method of using multiple UV sets is to use them only on exploded geometry.

