Hello all,

I have recently created a huge map (takes 1 minute 30 seconds to cross it) in gtkradiant and compiled it as BSP -meta (through the menu) for SOF2.
The sky and walls seem to be having the problem (they are all caulk type).

When I launch the map, it loads, I spawn, but..
my textures melt into each other (I'm sure most of you have seen this particular effect, also with faulty maps) and they seem to 'swim around'..

I have no leaks. Perhaps this is a memory issue? I don't know..



Would like to hear from you guys what you think this is.

Many thanks in advance,

Treval

My setup:
XP Pro SP3
GtK Radiant 1.4
Compiler: q3map2
SOF2 version: 1.01






edited on Oct. 19, 2009 02:22 pm by Treval

edited on Oct. 19, 2009 02:25 pm by Treval

Funny that none of you have heard of the skybox.
Thanks a lot for the replies.

I think I will move to another forum.

Are these custom or standard textures?

Cheers

do you wanna be able to come at all the parts of the map ? like you can use the whole map ? try to add some common textures.

i'm not known to SOFII, i play COD, but i think not using one of the common textures like No portal ( in cod radiant ) is the problem.

It looks like the HOM effect (Hall of Mirrors). Various things can cause it, most commonly a leak.

However, you stated no leak.

I've seen this happen in SOF2 under two other circumstances:

1. the surface is too long. Break it up.

2. the game doesn't like the brush. delete it and re-add it. Yes... I said the game doesn't like it. I've seen this similarly happen.

Regarding point #2... the game is having trouble drawing the portals correctly. It thinks the player can't see it when the player actually can. Recreating the wall can sometimes move the brush in the compiling order whereas VIS now sees it.
You may also have to add some portals manually.

As Foxhound asked... is the sky text custom or stock? Are you applying the sky texture as a skybox and not as a regular world texture?

And sorry for the lack of responses.. but the SOF2 is not as young as it used to be and therefore topics for it get lost in the mix and sometimes require a simple bump.

LennardN95 writes...

01001101010001010101010001000001010011000010000001000111010001010100000101010010001000000101001101001111010011000100100101000100
lol

LennardN95 writes...

01001101010001010101010001000001010011000010000001000111010001010100000101010010001000000101001101001111010011000100100101000100
lol

Correct. This was the problem. SOF2 can't handle areas that stretch out of miles (literally). How would it draw them? lol
I've used standard textures.


What is a portal?


Recreated it twice. It was worse when I used caulks.
It seems to be a distance problem for sure.


I don't have a sky. I just have a big ceiling.

To get a rudimentary understanding, take a look at this post:
http://www.modsonline.com/Forums-top-98234-0.html%23663727

You should try experiment and learn how the engine and compile process work. Then you should be able to understand how to solve related issues.

Basically you are going to want to physically create new nodes using hint brushes. These will create physical splits in your map that the player doesn't see, but the game does see. It will increase your polygon count, but it should help with your HOM issue.

Also, your map should not contain a single wall that goes on for a long distance. This, while producing the error you just saw, could also produce additional errors. It is poor design for this game engine and should be rethought.