Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[WormSlayer]

This thing is freaking huge! It also had too many polygons so I had to split the legs into separate objects but couldnt figure out how to package them all together so it's just 5 bits in a rar file XD

ReaperDestroyer.rar (4.7 MB)

[ZeosPantera]

I see you got yourself a bit of a bug problem there son.

[WormSlayer]

It's only supposed to be 160m tall but a decimal point slipped somewhere and it looked awesome so I left it

[adriaan]

looks nice! having issues too with the colors being to washed out. all have the same material settings yet some parts are more visible then others. look at the small platform. its really light from far away. but close everything else is washed out and it become dark

[M7]

The washed out issue is due IMO to the size of the object. I did import once by accident an oversize building (like 20 times the intended size) and it was washed out like these. After i resized the building to normal size, the textures look normal.

[adriaan]

but there must be something we can do if we want colossal ships?

[WormSlayer]

After some more experimentation with massive things, it seems like the engine adds atmospheric haze to the model based on the camera distance from the pivot point, rather than the actual object faces?

[cameni]

Yes, atmospheric computations are optimized by computing it for the whole object, since they change little for normal-sized objects. This speeds up the shaders that would otherwise have to compute the atmospheric lighting for every vertex, for no apparent gain on most objects.

However, for huge things like these we'd need to branch the rendering to go per-vertex.