Having some trouble with my projected material when it’s nested within a component. The component is a section of a larger landscape. I used projected material to get the landscape to fit the contours but when I separate out a section of it like the image below, the projected image shifts, when I enter the component, it’s in the correct place again. Any ideas how to fix this? Cheers.
Thanks for the file. I’ll look at the ‘Material’ issue later.
Not related to the problem but maybe worth mentioning:
Create a new layer, say ‘vegetation’ and assign it to the forest (component#9 is huge to display).
Then when turning off ‘vegetation’ rotating, panning and zooming is much smoother while working with the model.
The model is sluggish.
As Wo3Dan says, assigning Groups and Components to hidden layers will make the model easier to navigate.
There are several other issues to address as well.
Item 1 may well be the cause of the projected material problem.
The model is located some 546km from the Origin.
SU’s OpenGL rendering engine will not perform well at such a distance from the Origin.
Move the model to the Origin.
2) Group Axes Location
As mentioned above, the two terrain Groups are some 546km away from Origin.
However, their internal axes are located at the Origin.
Again, OpenGL rendering will have issues at such a distance.
See this video tutorial about the Axes Tools plugin used to fix the problem.
Use simple low-poly geometry to model small simple objects.
Overly complex geometry has a tremendous impact upon model performance and in the end, bloats the file.
The bridge railings extruded from 24-segment circles are overkill.
8 segments would suffice. Even fewer would be fine if closeup views aren’t necessary
Good to see that with @Geo’s help you have sorted out the ‘material’ shift problem.
Is there a particular reason for having a bottom surface as detailed as the terrain surface? It’s a copy of the top with all its faces and hidden edges. Way too much. If you could simplify the bottom surface, you would decrease the model file size and make it better to manage. Just a suggestion.
You are correct, it is a copy of the top surface. I had some issues with gaps between the terrain and the paddy fields. Used vector push pull on the terrain to basically make the walls of those pits. My computer is quite high spec so it runs without any lag and the model would only be used for a few more weeks before we start over again in a smaller scale. Having said that, I have just deleted the bottom surface and that reduced the file size by about 20MB.