@themuffinator thanks for the heads up. Their latest release indeed fixed the issue.

Probably worth mentioning the shader issue in q3e was addressed shortly after the Github issue was posted.

@Takkie: github.com/ec-/Quake3e/issues/76
Enjoy the rest of your vacation :)

@themuffinator Unfortunately I can't check my setup until next week because I am on vacation :) But I use the latest official ioquake3 build. ( from ioqiake3/get-it/). And I agree your test results point clearly to the quake3e engine.
So your suggestion to take this issue up with their team @github to check it out would be great. Might solve some other issues we are unaware of too. And until the fix we can use the little patch.
BTW I think it is great you checked shader issue out so thoroughly!
Edited 14.83 minutes after the original posting.
Edited 16.63 minutes after the original posting.

@Takkie: Only happens for me in newer versions of quake3e. I tried ioq3 builds from 2014 and 2018 - both don't have an issue with any shaders in the map. Multiple builds of CNQ3 are fine, too.
It's possible that the shader handling code was modified in ioq3 between 2018 and now, then ported over to quake3e. How old is your ioq3 build?

Edit: Just tested with the latest ioq3 build and I still don't have any shader issues. I'm not sure what else it could be but a problem with quake3e?
Edited 37.07 minutes after the original posting.

I wonder if quake3e is the problem because I have the issue on ioquake3 and quake3e.
I don't know what engine the LiveView uses but that one has also the issue. For now I can't check if I also have the issue with the vanilla quake3 engine. I am not 100% sure if I checked it (but it would be something I'd do before creating a patch). My guess is that the shader file was created on a Linux (or an other non windows) system and that windows handles the parsing of the { and } and the [enter] differently.
Edited 1.37 days after the original posting.
Edited 1.39 days after the original posting.

Seems like an issue exclusive to quake3e. I will raise the issue on github if someone else can confirm it's only quake3e and its forks which has the problem. I think it's better to fix where the problem started rather than patching the map.

At a guess, something changed in the parsing for the shader file between version 1.31 (released 21st Dec, 2001) and version 1.32 (released 7th Oct, 2002) for the Quake 3 engine. Version 1.32 was a big update and in preparation for the source code release. It would make sense that a error in the parsing of the shader files would be picked up in this release.

Can it be that problem only occurs on the current windows version?
That would be strange. A 'simple' text file read differently by different systems..
I am a bit relieved that the Liveview has the same issue because I really started to doubt myself :eyes rolling:
Edited 2.65 minutes after the original posting.

@Takkie: On Linux, with ioquake3 and the standard Q3A engine with only pak[0-8].pk3 and this map, I have no issues.

You are correct that the LiveView version is showing a major shader issue. I checked the local (backup), ..::LvL download and the MHGaming FTP download. All three are the same (tested sha256 and file size and dates).

I have not opened up the shader as I can not reproduce the error. If you do have a patch file, left me know and I'll add it to the review.

Edit: Patch file has been added to the review, thanks Takkie!

I am having a shader problem with this map. When it was first released it was no problem. But just recently I downloaded the map again and with that map there is a shader problem. I checked it by removing all additional content from my baseq3 and I still had the issue. Then I checked the shaders myself and after re-organising all the { and } I found a typo.
It is very strange because the first time I downloaded the map (when it was released) it didn't have this issue. To double check I downloaded the level again and it had also the shader issue. I have made a patch but first I think it would be good if someone can confirm the issue by downloading the current map from the
..::lvl server and load it up. BTW. If you check the mksteel.shader yourself, good luck because it is quite messy and I ran through it a dozen times to find the typo. Because I find the map amazing I put in the effort to correct it (at least for myself)
=====
edit: I just did a quick check with the LiveView and it has the same shader problem.
Edited 8.52 hours after the original posting.

Ahhhh..

Feels so skulltag in that one map I remeber having so much fun on last year with other people in a Co-Op.

Meeeeeeemmmmoooorrrrriiiiiieeeeessss

Its a beauty. 9/10

I love the window vistas in the map, those green rocks outside the window look cool. Nice application of style. Definitely a map to download.

Fun w/ Corkscrew on the LAN!

She's a bute!

Real Nice map.
Looks good.
Plays smooth.
At first it felt small.
Later it felt bigger and bigger.
Now... It's a huge map.
A blast on InstaGib/railor mod.
I would give it 10x 9.

Damn detonators... Installed the latest one and now framerates are okay, my bad... Another thing, also tried 1v1 on lan and it's great!

Very nice map, excellent on lan 1vs1! Plays really well, keep up the good work dood :D

The Red Armor is kind of lonely in this map.

It is okay, but it doesn't have that gameplay polish that only a handful of levels have anyway. =P

/me hits the download button for papri-k, who won't regret it

;-P

Really cool map! But the shiny metal surfaces are a bit to much, looks to busy (less is more sometimes).

I like the inclusion of the silent soft "no damage" carpets :)

9/10

Cool map, but very heavy on the framerates. On my PIII 800 w/ 512 mb and a GeForce3 my framerates dropped below 20 in the MH/RG area, I had to scale down some things to make it playable. I'll give it an <8>

I remember seeing this awhile ago... only thing that bugged me is that the "blue theme" is getting kinda old (Lun3dm2, hub3tourney1).

That doesn't mean it doesn't look good... it's purrrrdy :P

9 from me

Nice, doom flavoured map. My CPU wasn't complaining and it's plain old crap-ass. Certainly nothing compared to the looks :-) The game plays out pretty well too. If you haven't played this, you owe yourself a go...10/10.