OACMPDM4 missing texture

[Bishop-333]

[Bishop-333]

all the walls around are extremely dark and we cannot even see if it's a wall or void

[Bishop-333]

z_oacmp1v4_beta-220411

[NeonKnightOA]

Indeed, lighting is a problem with this map. I'll be sure to take a look.

[The-Gig]

I don't remember the reason why you recompiled the map in the first place... maybe the original compiling by Akom had better lighting?

[NeonKnightOA]

It did, but only when compiled with Q3Radiant. When compiling with NetRadiant's q3map2 the map went dark.

[NeonKnightOA]

If Q3Radiant didn't generate non-GPL-compliant files, we wouldn't have to undergo 90% of the problems with this pack. *sigh*

Sometimes, as much as I love the spirit of the GPL license, I really hate the restrictions of the license itself. Quite restrictive for a license that prides itself in supporting "freedom".

[The-Gig]

On a side note about ligthing, don't forget to check that all the shader files are in your shaderlist.txt... iiic years ago you mentioned some oacmp maps looked very dark after you compiled them due to that.

PS... technically, q3radiant/q3map source code has been released under gpl... I don't know the reason why there isn't around a functionally compatble build compiled starting from such gpl code, without the changes introduced by NetR/GtkR/q3map2... Or maybe there is/was?

[NeonKnightOA]

It's GTKRadiant the one that was released under GPL. Q3Radiant is still closed source.

[The-Gig]

Are you sure?
Here https://github.com/id-Software/Quake-III-Arena/blob/master/README.txt it mentions Q3Radiant and q3map (which are also the names of these folders https://github.com/id-Software/Quake-III-Arena/tree/master/q3radiant and https://github.com/id-Software/Quake-III-Arena/tree/master/q3map)...

[NeonKnightOA]

Took me a while but I found leilei's comment on q3radiant.

Akom probably maps for OA using a Quake3 installation, which kind of goes against the whole this-isnt-q3 independence of the project.
I believe I posted before on NOT recommending old q3radiant and q3map

Unfortunately I haven't found the previous not recommendation on q3radiant. But yeah, over time I grew up tired of GPLv2, its problems, the compliance and how in some situations it causes more headaches than solutions when it should be the other way around.

[NeonKnightOA]

I'll try recompiling this map without the -dark switch to see if that's the cause.

[NeonKnightOA]

https://mega.nz/file/bMZkRJBa#J_rUm2nz2SpiMFl6kBY0eMceeCLOJ1PLfnz_-CQRzCw
New test version. I've relit the whole map. Turns out the lights weren't shaders but textures, and the light in them was... quite dim. So I've created separate shaders for each light that seemed to solve the issue (still had to apply a light actor on top of them, though). Only two lights missing. Also separated the stars into a separate skybox.

[The-Gig]

What do you mean with "two lights missing"? (UPDATE: I guess this #43)
Anyway, I tested 230430 version and noticed that the outside of the spaceship is too bright now, if you see the attached screenshots (taken with the same crappy integrated Intel Graphics), some brushes of the spaceship are basically unnoticeable.

Furthermore, I'm not sure about the new skybox. I mean, maybe in the classic version it was a bit strange that some stars were so close to the playable area... but now the stars trails bend? Maybe it's on purpose, to think about some "space warp" technology which creates a sort of "bubble" around the spaceship?

230430 version:

OACMP Vol1 V3 version: