OR-Flickering Water

[tie]

This has been picked to death already I'm sure but, has anyone come up with a hack to fix the flickering water issue in some routes? I've been reading what to do at
https://bugs.launchpad.net/or/+bug/1463537. But I see no difference in the changes when I tinker with the editor.env file. It still flickers.

[Vince]

Flickering water may be the result of the layers defined in the *.env files being spaced too close to each other.
Compare those that work with those that flicker.

regards,

[tie]

Yep. Looking at a particular *.env right now that's being used. Badlands summer right now. At certain camera angles, say 1 deg turn, the water disappears entirely. I reverted back to default as well, it flickers also, but not as much.
I'm no expert at this, but I'll tinker with some of the water settings. Of course I already backed these files up. Fools dive in where angels fear to tread lol.

[charland]

I have this issue in the first two DAR routes. I have the watermid and top water at the same elevation and it works fine in MSTS but keeps changing back and forth in OR. I had to drop the watermid texture to -.01 to get it to stop. The result is no flickering but the edge of the water where it meets the terrain shows... that's what I wanted to get rid of in the first place.

Paul :-)

[tonyhap]

Why not use just one layer for all water? I reckon the only reason for multiple layers is to provide some form of parallax viewing that will give the water some feeling of depth when the point of view is moved. But does anyone ever notice that?

Is there another reason for multiple water layers?

Regards,
Chris

[peterman]

Why not use just one layer for all water? I reckon the only reason for multiple layers is to provide some form of parallax viewing that will give the water some feeling of depth when the point of view is moved. But does anyone ever notice that?

Is there another reason for multiple water layers?

Regards,
Chris

I personally find that you need a minimum of two layers of water in OR... one for colour and the second for waves. Both .ace files need to have an alpha with it. A third layer would be needed if you want to model a lake bottom other than a TerrTex .ace.

Rory... just a thought here. The model instancing option in OR causes flashing on vegetation and water when checked on my route. I'm wondering if perhaps one of the layers is flashing on your route giving that flickering effect?

Peter

[tie]

I personally find that you need a minimum of two layers of water in OR... one for colour and the second for waves. Both .ace files need to have an alpha with it. A third layer would be needed if you want to model a lake bottom other than a TerrTex .ace.

Rory... just a thought here. The model instancing option in OR causes flashing on vegetation and water when checked on my route. I'm wondering if perhaps one of the layers is flashing on your route giving that flickering effect?

Peter

Never thought of that. I'll check. Thanks Pete

[ftldave]

The beloved Sea View Island route has the awful water flash when I first tried to run it in OR. Substituting different .ace layers hasn't fixed anything, my first attempts, and being islands, lots of water throughout the route. Any suggestions would be greatly appreciated.

[crstagg]

The beloved Sea View Island route has the awful water flash when I first tried to run it in OR. Substituting different .ace layers hasn't fixed anything, my first attempts, and being islands, lots of water throughout the route. Any suggestions would be greatly appreciated.

Archie Campbell says: "Don't run Sea View Island route!"

[peterman]

The beloved Sea View Island route has the awful water flash when I first tried to run it in OR. Substituting different .ace layers hasn't fixed anything, my first attempts, and being islands, lots of water throughout the route. Any suggestions would be greatly appreciated.

As I suggested in post #6... uncheck the model instancing found under video tab in your options.

Peter

[ftldave]

Archie Campbell says: "Don't run Sea View Island route!"

Well, at least I didn't get the infamous "THAT'S NOT AN OPEN RAILS PROBLEM!!!" response.

Thanks, will disable model instancing and re-test.

[geepster775]

Archie Campbell says: "Don't run Sea View Island route!"

Archie Campbell or Archie Bunker?

[geepster775]

Well, at least I didn't get the infamous "THAT'S NOT AN OPEN RAILS PROBLEM!!!" response.

Yea, but for you, it will never be that easy to fix. The team actually has a blueprint item to make your experiences with their product as lousy as possible.

[cjakeman]

Not sure yet if there remains an OR problem which can be fixed.

Never thought of that. I'll check. Thanks Pete

What was the outcome, tie? Does it get rid of the flickering?

Thanks, will disable model instancing and re-test.

As I suggested in post #6... uncheck the model instancing found under video tab in your options.

So, fltdave, did Peterman's suggestion help?

The team actually has a blueprint item to make your experiences with their product as lousy as possible.

What exactly do you mean, geepster775 (and I do wonder why are you posting so aggressively. We're all volunteers here.)


Best wishes,

[tie]

Yep Chris. Many environment settings still flickered even without instancing checked.