Region compile error

(Cronium) #1

Long time no see :wink:

I have a small problem with region compiling. When i try to devmap my region i get an error message: “Map with no shaders”. Hmmm… Help?!

(MadJack) #2

How does it do for the whole map? Same prob?

(Cronium) #3

no, it work without probs when i compile the whole map…

(LaggingTom) #4

I just got this problem to, if it helps, I think it has something to do with my terrain being made by Easygen

(Shaderman) #5

Try the following steps:

  1. Open the map you want to get your region from
  2. Make the x/y view to show what you want to use for your region
  3. Region --> Set XY
  4. File --> Save region (for example region.map)
  5. Reopen the region.map you saved in the step before
  6. Place one info_player_deathmatch, one team_CTF_bluespawn and one team_CTF_redpawn in this region map (if they haven’t already been inside the region you selected).
  7. Compile and run it
(LaggingTom) #6

Ah, reopening the .map region and compiling it works. Thanks! :slight_smile:

(kamikazee) #7

This is a slightly faster way:

I do all steps until the ‘save region’ but since I do ‘save region’ and save it as region.map
Now, this is 1 time only:
I edit my .proj files in the script directory. This file contains the BSP commando’s that radiant will show.
I added 1 command which compiles a certain map, here the region.map.

This way, I don’t need to open the region map, compile, re-open my original map and find my ‘currently-working-here’-spot.
I can now just click the command in the BSP menu, and it compiles region.map. Then I go to ET and load region.bsp.

I can’t recall the exact commands as I don’t have the .proj file here, but it’s quite straighforward.

(thore) #8

I’ll give it a try. Sounds like a nice “hack” :wink:

(Shaderman) #9

Very nice kamikazee :wink: The only disadvantage might be that you’re compiling with an older version of q3map2 then (the one that came with radiant) unless you edit your project file and point to a newer version (don’t know if this works though).

(kamikazee) #10

How do you compile otherwise?

And IIRC, the Q3MAP(2) path variable is set by Radiant, so that should point to the right one.

(Shaderman) #11

I use the newest version of q3map2 with q3map2toolz as GUI.

And IIRC, the Q3MAP(2) path variable is set by Radiant, so that should point to the right one.

I’d say it points to the one that was installed with Radiant (I think it’s 2.5.11) and not to other/newer versions. Anyway, the older version should be ok for most compiles :wink:

(kamikazee) #12

Actually, if you got a GUI you don’t need to tinker with these settings ase they are meant for Radiant. :wink:

I want to warn you that you must pay attention when you do ‘save region’! Since you set a hard-coded name, you could get the habit to click the map you want to save to in a rush. This way, you’ll overwrite the map with a small region map. (duh)

I don't take any responsability for physical, psychological or any other damage because of this hack.

This was just to make sure no-one sues me here, you see. :smiley: