Rendering fixes (January 2016)

[zeuxcg]

We shipped some rendering fixes for previously reported issues (thanks to @ConvexRumbler for working on them!)

• Part colors/normals are no longer randomized if outlines are disabled on the entire place or all surfaces of the part are SmoothNoOutlines. Essentially you either get outlines + tone shifting or nothing for every part. If outlines are enabled globally but only partially disabled on the part (e.g. some surfaces aren’t SmoothNoOutlines) we choose to preserve tone shifting since we can’t make this choice per-surface.

• Surface GUIs should no longer be visibly offset from the part surface.

• Water/part sky reflections should no longer lag behind sky changes as much as they did previously

• Decals on CSG parts should no longer interfere with unrelated Neon parts in the level

We also have accidentally broken fog when trying to fix fog animation which will be fixed next week.

Please post in this thread if the fixes have any negative side effects or if you still have a problem that we believe is fixed.

[zeuxcg]

The next few fixes that are on the table are:

• Automatically use dedicated GPU in cases when we don’t
• Fix some issues with VRAM reporting causing severe degradation of humanoid texture quality
• Fix fog regression and actually fix fog animation

As usual, if you have a rendering bug, post it in the relevant section and it will be added to the list & prioritized accordingly. Now that we shipped Xbox I’m hoping for a much faster turnaround.

[einsteinK]

Part colors/normals are no longer randomized if outlines are disabled on the entire place or all surfaces of the part are SmoothNoOutlines. Essentially you either get outlines + tone shifting or nothing for every part. If outlines are enabled globally but only partially disabled on the part (e.g. some surfaces aren’t SmoothNoOutlines) we choose to preserve tone shifting since we can’t make this choice per-surface.

Without outlines

With outlines

I don't notice tone-shifting for the outlines one... Maybe a TINY bit, but could be my eyes playing tricks. **EDIT**: It might be there, but almost unnoticeable...

[digpoe]

Try turning outlines off for the surface you’re viewing the parts from - it may make it more noticeable.

[buildthomas]

@zeuxcg

Surface GUIs should no longer be visibly offset from the part surface.

This one nearly deserves its own appreciation thread, thanks!

How does this behave for larger distances? (It used to be that the offset would become larger for long distances from the origin.)

[Maelstronomer]

@zeuxcg

Please post in this thread if the fixes have any negative side effects

http://devforum.roblox.com/t/was-there-a-change-in-the-fog-shader-for-lower-graphics-yesterday/21263

Thanks buildthomas for linking this thread!

[jcfc]

Thanks for the fog update, this has already had a positive impact on a project I’m developing.

[Mister_Mystery]

Decals on CSG parts should no longer interfere with unrelated Neon parts in the level

Also, Textures on CSG parts no longer make all the other faces render with the Neon material, which is the real reason I’m so excited.

[zeuxcg]

@AdmiralLennox

Also, Textures on CSG parts no longer make all the other faces render with the Neon material, which is the real reason I’m so excited

Yeah, that’s what I meant.

[zeuxcg]

@einsteinK

EDIT: It might be there, but almost unnoticeable…

It will be easier to see on low quality where we disable outlines.

[Partixel]

My reaction to this thread:
1… YES YES YES
2… YESSSSSSSSSSSSSSSSSSSSSS
3… faints

I still haven’t been able to read the 4th fix…

[Crykee]

Thank you! We really needed the Part colours/normals not to be randomized for our game It’s lookin’ good

---

[TheNexusAvenger (Nexus)]

Noticed a small issue with SurfaceGuis at fast speeds (160 Studs/Something at about 10,000 studs or so from the origin). Having a 0.001 offset would be fine for me, just not 5 studs.

[einsteinK]

@FromLegoUniverse

at about 10,000 studs or so

10k studs… per second… what are you even doing?

[EchoReaper]

@einsteinK

10k studs… per second… what are you even doing?

I think he means going fast while he’s 10k studs from the origin

[TheNexusAvenger (Nexus)]

@einsteinK

10k studs… per second… what are you even doing?

Oops, forgot to mention my speed is 160 studs per something, with my X being 10,000 studs

[Aurarus]

Can we have an option either as a developer or the player to set the fog to whatever default we deliberately set it as

The thicker fog with lower graphics, even prior to the bug, is super annoying. It ruins the atmosphere, much moreso than models/ blocks popping in and out.

[zeuxcg]

Is this only happening if you move fast? Or is it just about being at 10k from origin?

[TheNexusAvenger (Nexus)]

@zeuxcg

Is this only happening if you move fast? Or is it just about being at 10k from origin?

I will check and edit this post. My guess is only moving, but I will check.

Edit:
Monitored it more closely, and it starts to have ZIndex issues at 3,000 studs while moving.
Here is what happens at 10,000 studs, not moving (and somehow landed upside down):

[zeuxcg]

Ok, cool. Can you attach or PM me a model with part of the level where this happens? I believe we tested at 10k studs but it depends on other things like camera setup.