[Commander Zane]

Ctrl + Shift + S, it no longer unlocks the Tech Room listings for ships / weapons, missions, and cinematics.
Anyone else get this, was the feature removed?

[Exeter]

I just gave it a go and it works for me.  I did have to unlock each category individually, but it's been so long since I've tried it, I can't remember if that's how it's always worked.

[jkalltheway]

maybe check if ur capslock key is on. Maybe that's messing with it?

[Commander Zane]

It isn't, and I don't imagine that Caps Lock would be a factor in that.

[Polpolion]

You mean it just randomly stopped working? What build are you using?

[Commander Zane]

Tried the latest Nightly build, tried RC3, nothing.

[Aardwolf]

Maybe it's a difference between Debug and Release builds?

[captain-custard]

i thought the tech room was F3 but then  again i get things confused

[asyikarea51]

I always saw the F3 tech room as a "fluff-free" ingame model viewer for troubleshooting while the normal tech room has all the usual story stuff in it for immersion...

[Aardwolf]

"Tech Room" = the menu thing that says tech room. F3 = "Ship Lab" or "F3 Ship Lab"

[Commander Zane]

Maybe it's a difference between Debug and Release builds?

Don't believe so, I can try that again just to double-check, but I'm fairly sure there shouldn't be a functionality difference between R and D builds.

[Dilmah G]

Which campaign do you have selected? I believe this can sometimes be a factor.

[Commander Zane]

Any. Tried the FreeSpace 2 campaign, Blue Planet, and Procyon Insurgency. They all used to work before.

[Commander Zane]

Anyone have an idea of what's going on? Campaign doesn't make a difference, no build makes a difference, it just no longer works.

[Aardwolf]

Big things I'd guess we'd need to know would be: what .exe, and what are the file-paths it's looking in. The first is easy to figure out, the other is listed in one of the debugging files somewhere.

There is of course the slight possibility that everyone so far (including myself) has been to lazy to check themselves, and there might actually be an obvious bug in need of fixing.

Edit: I've actually tested for myself now, and I see no problem. I'm using 3.6.10 final, mediavps, Main FS2 Campaign.

[Commander Zane]

It's a pretty clean install that I put in about a week ago.

[The E]

I tested it using Blue Planet, Crossing the Styx and Silent Threat, with 3.6.10 Final as well. No problem here.

[Commander Zane]

What the hell then?
It's a CLEAN install so everything should be dandy.
I can't do any of the mission experiments I want to do on other campaigns because of this.

[Galemp]

Is your keyboard working?

[Commander Zane]

Yes.