-= Gametoast.com =-

Well, i really don't know how call this topic, anyway this is my problem:

I'm working on a map of the Geonosis Arena (yep, another one).

When I spawn my trooper, near me i can se the arena: but if I look most away from me... ...it's invisible.

Only if i zoom with my gun i can see completly the arena: Can anyone help me to fix this problem? thanks

Its a sky file settings issue, increase the view distance (line might be named different, not sure off the top of my head), and you'll be fine

that looks like a sky problem possibly or the actual object itself (i'm thinking sky because it's blending into the background

go into abc.sky file in data_abc/worlds/abc/world1 and delete all the stuff under sky info so the only thing you should have is dome info with your dome .msh called

I did what YaNk said, and it's better but not fixed: This is my AGA.sky (AGA=my map name ): I deleted that part you said but it still unsolved. What should I do?

PS: I didn't do what Super_Clone said just because YaNkFaN was more clear, so no offence to you, Super_Clone.

Unfortunately, what Super_Clone said is correct. The arena is vanishing at a certain point and showing up when you zoom in because the sky file is putting a limit on how far you can see. If you search for this number (I can't recall it off the top of my head) and increase it, you will be able to see farther and thus see the full arena. I hope I cleared things up a bit.

EDIT - Skimmed through your sky file, just noticed it.
It seems the thigns you deleted are what you needed. So maybe you could borrow bits from a stock sky file to fill in the gaps. Unless you made a backup before you deleted anything?

Heheheh... Trust me, I have experience with stuff, even if I never use it, I still learn it

exactly what i was saying by getting rid of the sky info it sets that value to infinity. @delta try deleting the lowres texture part

LowResTerrain()
{
Texture("geo1");
PatchResolution(8);
}

from the sky file. Then clean and remunge and see if it works

Wouldn't it not be advisable to let the engine determine how it renders everything, especially not knowing what exactly its defaults are? (I've not seen anything that suggests the ranges are set to infinity, or high enough to seem so.) I would say it's better to actually edit the values as needed, so you can control what is or isn't rendered. I can't really explain as well as I'd like, so I'll refer you to these posts.

http://www.secretsociety.com/forum/disp ... sp?mid=611

http://www.secretsociety.com/forum/disp ... sp?mid=895

I would consider these important, as it will determine actual framerate ingame. The more you're rendering, the greater the workload for the system. I think it would be considerate of us not to simply let the game render objects unnecessarily, since not everyone will have a high end system.

Edit: To stick to what I meant to do, those parameters should be in placed back in the sky file, even if you need to copy it from the map template, then edit the values until the arena shows up as desired.

it's actually less rendering because of the fact that after a certain distance the game starts to use lowres textures. If you then have to apply fog or a color to those textures it takes more to render. Yes you could set the value in the sky info to 5000 or some ther high number but it's much easier and much more efficient to just remove it completely. If you want to put it back by all means put it back but change the values to extrememly high numbers. Most maps in BF2 use this because of their small size and the developers wanted small visibility ranges.

This goes a bit beyond just being a technical issue. While I doubt whatever the engine defaults to is insane (likely somewhere close to what would run well with the better machines of the day), it must be increasing the values and therefore the amount of objects rendered, according to what you mentioned earlier. If that default can't be quantified, how can one be sure the settings are optimal? I wouldn't call that efficient, though it's certainly easy. A good mapper should always consider how these settings will impact a system other than their own. A map that's only playable for the higher end systems (due to high values that the user can't control) won't be as well recieved as one that plays well on a fair range of machines with varying capabilities. In the end, we're modding not simply for ourselves, but for our fellow gamers as well, or else we'd never release our work.

YaNkFaN wrote:exactly what i was saying by getting rid of the sky info it sets that value to infinity. @delta try deleting the lowres texture part

LowResTerrain()
{
Texture("geo1");
PatchResolution(8);
}

from the sky file. Then clean and remunge and see if it works

I did this^ but it looks just like before.

Add this to your .sky file: Make sure it goes before everything else.

@AQT: Well, that did worse...