-= Gametoast.com =-

For some reason, the Kamino water in my map disappears when I look at it from certain angles. I copied all the water and fx stuff I needed from the Kamino assets, and I set up the water settings in Zero Editor to match the ones from the shipped Kamino.

Well, I think I have everything I need. Here's my files for reference:

KN1.req KN1.fx Help would be much appreciated. If you need me to post something else, ask away.

Have you used water befor in othre maps?

Also, I asked why water didn't work on my custom maps, and I guess some computers just can't work with your custom maps with water, maybe yours is in-between being able to use it and it crashing because of it.

I didn't say crashing, I said it's disappearing when I look at it from certain angles. Honestly, did you even read the title of the thread?

EDIT: Here's a couple pictures for reference.

Looking straight across, but not directly at the water. Looking directly at the water. Zoomed in and looking directly at the water, same angle as last picture. Again, help would be appreciated. If someone needs me to post another file to check it over, just ask.

Xavious
Did you try matching your .sky files settings to that of Kamino?
I am assuming you already matched the .fx file to get the water in the first place

FragMe! wrote:Xavious
Did you try matching your .sky files settings to that of Kamino?
I am assuming you already matched the .fx file to get the water in the first place

Yep, I copied all my sky stuff from the Kamino sky file.

Why don't you just try using water that's not Kamino water, and then adjusting the color settings/textures later. That'll help figure out whether the water itself is the problem or something else.

Also, try adjusting your vis settings ingame; it could just be that it's a "your-computer" thing.

Maveritchell wrote:Why don't you just try using water that's not Kamino water, and then adjusting the color settings/textures later. That'll help figure out whether the water itself is the problem or something else.

The thing is, to my knowledge, any other water would crash the map if I used it to cover the entire map.

Maveritchell wrote:Also, try adjusting your vis settings ingame; it could just be that it's a "your-computer" thing.

I'll give it a shot, but I doubt it'll work, seeing as I don't get this problem while playing the shipped Kamino.

I had a similar problem with Urban map, objects would flicker on and off depending on the angle that you looked at them, and would usually come back if you zoomed in.

I think it is caused by too many objects being rendered at the same time. I tried various sky file nearscenerange's with a bit of success. (not total though). I had to lower the values considerably so the view distance was less (therefore less rendered).

I'm not entirely sure that this applies to the ocean, but I have a hunch that it might.

q's
1. Is your terrain the same size as kamino's?
2. Did this bug occur from the start, or as you added objects?

My reasoning is that if your's is the same size as Kamino, there should be no issue and there must be another variable. If your's is bigger than kamino, then you could be pushing the limits of the engine.

In the fx file there are: You might as well try lowering the divisions to ease polygon load (If I'm assuming its function correctly). I'm not sure what LODDecimation is, but if you could somehow use that to lower the quality and improve performance, that would also be beneficial. (In one of the pictures even, I see that a nearer (possibly higher) LOD disappeared but in the distance there is some water out there (presumably lower LOD). Perhaps LODDecimation is that it divides in 2 when it downgrades the LOD?

You could also mess with the LOD and view distance slider in video options and see if those have any effect.

RepSharpshooter: I think it is caused by too many objects being rendered at the same time.

I agree. There is that Aclamator jutting off in the distance, which might have something to do with it. But before you do that I would try to adjust your LOD distance, because a similar thing happened to me and it turned out my graphics settings were to high.