I tried adding a printf() at the top of main(), but control does not even reach that point when the app pauses. I think the pause is a Windows thing - maybe it's analyzing DDLs it has to load to make sure they don't contain viruses? If the printf() won't print anything until after the pause is completed, I don't know of a smart way to let the user know to just hold on.

Interesting is that once I've waited a minute for Radiant to launch, if I try it again even with newer builds it does not seem to wait, or at least not as long.

A bit of WTF with regards to fixing the slow initial start bug:



I'm not sure if any Windows programmers around here might have any insight.

QuakeLive doesn't seem to be supported, yet.

I don't understand why people continually talk about "making a map for Quake Live". How is this in any way technically different from making a map for Quake III (Team) Arena?

I don't understand why people continually talk about "making a map for Quake Live". How is this in any way technically different from making a map for Quake III (Team) Arena?

It's not as convenient as Q3 mapping since (among other reasons) Radiant won't read QL encrypted pk3s so you have to manually extract all the textures which is a pain in the ass.

I assume it uses the same textures as Q3 and TA, apart from some Quake Live branding maybe, or is that not correct? So I still don't see why QL's content being encrypted is a problem. And if the texture names are different, its nothing a simple find/replace won't solve.

I'm just thinking people are using it to come across as "interesting" or something and perhaps they're hoping that their map will somehow be noticed by id Software and be put up in the QL map set.

But lemme tell you this: your* half-assed map intended for QL probably has only a fraction of a chance being included compared to a totally awesome, innovative Q3 map that doesn't mention "Quake Live" anywhere.


*) "your" as in the general public, not muffinman specifically

QL has quite a number of exclusive textures.

Let's put it this way: if you make maps for Q3, nobody will play them because the community is dead. If you map for QL there is that very small chance that your map might be added (unless your name is ShadoW , then it's almost guaranteed to be added) and if it is added then there can actually be people playing your map, maybe even in competitions! What I'm saying is that either way the only enjoyment people will get out of your map is playing against bots, unless your map is added to QL. So why not try to achieve that?

Also, why would a Q3 map have a higher chance of being added to QL than a community QL map? Purgatory is a good example of a community QL map that got added to QL officially. It's got nothing to do with being 'interesting', just moving on with the times.

Another argument is that the Q3 mapping community is also dead compared to 10 years ago, and QL is attracting new people to the game. If we can make QL level design as uncomplicated as possible to get into, then we might be able to get new mapping talent in future. If we have QL players starting out making offline maps for QL (which is possible because once again, all recent Q3 maps are practically offline maps) then it can only be a good thing.

In any case it'd probably be damn easy for whoever's programming Radiant to add proper QL support so why not?

Let's put it this way: if you make maps for Q3, nobody will play them because the community is dead. If you map for QL there is that very small chance that your map might be added