Terrain & Patch probs, works on 1 pc not other...

(Axedup) #1

Hi,

Ive got all the latest tools for q3map and gtk etc… and Im getting this problem. It works fine on my pc (where created and compiled), but when tested on others, I get a problem where the terrain goes…weird? :???:

Can anyone pinpoint or lead me down the right path to salvation, where I can get to the root of the prob.

Im thinking perhaps the “other” pcs need to have the various commands and textures associated with q3map (cel etc…) to work properly.

Ive tested it with / without foghull inplace, make no difference to other pcs, but ok on my pc.

Pic from my pc…

Pics from other pc…

Is this the case?

Thx in advance :wink:

Axedup

(Raven) #2

Are you sure your shaders are on the other PC’s in their proper places? Just a shot in the dark :slight_smile:

(Axedup) #3

Yep, its all set up in pk3 files for a mod, so it should be all cushdi :slight_smile:

P.S - Ignore the missing texture on the wall, its the terrain thats doing the weird stuff…

(Cardigan) #4

hehe, I had something like this for ages (on my own pc) and I thought it was q3map2 causing the prob and gave ydnar loads of hassle about it ( :bash: sorry! :D) and it turned out my video card drivers were just dodgy - I was using a beta release of the nvidia detonators and when I downgraded to the official ones the ‘bug’ disappeared… Looks almost identical from your pics, but with mine it flicked between how it was supposed to look and how it looks in your pics every other frame or something. Anyway, check the drivers! :slight_smile:

(Raven) #5

Thank you for the info. Cardigan. I have never seen that and would never have thought of it as a possible cause :slight_smile:

(Axedup) #6

Nope sorry m8, thats not the answer.

They have tried to install the drivers and it makes no difference to their pc’s when they run the map.

Any other ideas?

Thx

Axedup

(disTrust) #7

hmm, packed the terrain .pcx as well?

(Axedup) #8

Hmmm, I dont think u need it in the pk3, I think its only used for the complie of the map.

Not sure though.

Tried it on a fresh q3 install on my pc, and without the *.pcx its ok… :???:

(disTrust) #9

hmm, i m not 100% sure but i think u need it in ya pk3.
even on a fresh install it might pick it from the folder u have it in (exept if u installed on a different hd/partition).

(ydnar) #10

The terrain PCX _indexmap (nee alphamap) is only used during compile and does not need to be distributed with the map.

y

(disTrust) #11

oh ok :cool:
will save me the efford to search em next time:)

(Axedup) #12

:eek: BUMP :eek:

Sorry lads, I must find a cure :???:

Thx

Axedup

(RabidCow) #13

Its a long shot, but did you check for duplicate brushes? I just had a case where a brush was inadvertantly put inside another and it looked just fine on my pc and then a tester showed me the horrible z-fighting that was visible with their pc. I didn’t know the problem existed. The two pc’s had the same video cards and drivers BTW. I don’t know why there was never any indication of the problem on my pc…other than that…are you using internal or external lightmaps? Have you tried making a single lightmap for the terrain?

(Axedup) #14

No thats not it, the actual crater texture is set on a patch mesh and the rest of the ground is a terrain entity.

What the prob u had sounds like a 16bit / 32bit display difference. Everything looks cool in 32bit but when in 16bit eugh!!! but thats not whats happening here :frowning:

Thx anyway :wink:

Axedup