[NEEDS INFO] stromkeep broken?

when I open stormkeep in radiant ... and hit compile ... it will fail to compile the vis stage saying that there it cant find the bsp ....

however ... if I select everything and replace all the textures with something boring from trakk5 ... it compiles just fine ...

is this only an issue with me? or does anyone else get this too

... xonotic 0.6 ... mint 12 linux ...

It complies fine on mine. No errors or anything. Xonotic 0.6. Slackware 13.**.

thats strange ...

ill wait on this till after I update to mint 13

edit :: aa ... what compile setting did you use? ... if you did bsp only ... of couse its going to work ... it failed for me on one of the higher quailty test compiles

still need to narrow it down more ... but it appears that I have issues with the lava shaders

I compiled it at "(final)+ambient occlusion" setting. Still no problems.
(

Code:

[q3map2] -meta -v -samplesize 8 -minsamplesize 4 "[MapFile]"
[q3map2] -vis -saveprt "[MapFile]"
[q3map2] -light -randomsamples -samples 4 -lightmapsize 512 -bounce 8 -fastbounce -bouncegrid -dirty -dirtscale 2 "[MapFile]"
[q3map2] -minimap "[MapFile]"

)

P.S. I am using NETradant from Ingar's NetRadiant Packages.

hutty, clean up your OS! I got the intention that you broke something again...

clean mint 13 install
netradiant git
stormkeep xonotic 0.6

same error

ok ... i have narrowed it down ...

if I replace both of the lava shaders (moving and not moving) and the red-line bouncepad effect shader .... it will compile ...

I'm still digging into this issue ...

all other (quake) sources just say that the error "is caused by another" ... ... which is not helpful at all ...

aa ... are you on a 32 or 64 bit system?

(im on a 64 bit ...)

Yes. 64 bit.

more wierdness ...

i'm working on a custom map ... and if I try to use the ground-drylake02 shader ... the same thing happens ...

even wierder ...

I have the same issue with the purple lava texture ... switch to the blue one ... it compiles just fine ...

Care to share the log for your tests? That would be at least slightly more helpful.

not sure what you mean by log ....

He means the text output which shows all the actions, so including the compile log.