Jump to content

Invisible Terrain, Very Strange


Recommended Posts

Posted

I've recently encountered a new problem, in which terrain entities become invisible, yet structurally still active, after compiling maps.  I've never had this sort of issue before, and typically incorporate terrain developed in Easygen in my maps.  I've already determined that there's nothing wrong with my shader or alphamap files, yet for some strange reason any terrain entities become completely invisible in game.  I believe it has something to do with my compilation process, perhaps q3map2 isn't recognizing my shaderlist.txt?

 

In troubleshooting the anomaly, I downloaded the "Terrain" prefab, placed the alphamap pcx in my base folder, the shader in base/shaders, added the shader to shaderlist.txt, and compiled the map.  The terrain was invisible in my compiled .bsp, yet visible in the already compiled bsp that comes with the prefab.

 

This has been a very annoying problem to suddenly arise for seemingly no reason, and I would very much so appreciate any assistance or advice.  Thanks in advance.

Posted

@@Vegeta Send your compiler commands, your version of the .map and a link to the original .map file.

 

I have recently spent quite some time looking through .map files and should be able to spot anything that's off in there. Maybe your Radiant install is screwing the .map up in some way.

Posted

@@AshuraDX
 
Here's a link to the .map
https://www.dropbox.com/s/0n1xuoesrzfi8f5/skybox.map?dl=0
 
And the compiler log

 

  Reveal hidden contents

 

 

I'm not sure what you mean by my version of the .map versus the original, sorry

Posted

@@Vegeta

the .map file seems fine at a first glance, all brushes in the func_group are set to detail and I'm not seeing any typos.

and I'm not seeing anything fishy in that log.

Sorry mate, I have no clue what's wrong.

Posted
  On 11/9/2017 at 11:31 PM, Vegeta said:

That's too bad. I think I'll try re-downloading q3map2 and the GUI to see if that changes anything

Oh. I recently had some issues with q3map2 GUI on Windows 10.

It would not register changes done to the map and produced ugly artifacts that I would not get while compiling from Radiant or via commandline. I can't tell if the problems were caused by using the gui on win 10 or by targetting the 64 Bit version of q3map2.

 

But maybe you problem is of similiar nature?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...