Post news RSS Statement to the canceled release today

Unfortunately I have to cancel the planned release today due to some serious issues.

Posted by on

Statement to the canceled release today

Unfortunately I have to cancel the planned release today due to some serious issues. After final testing last night I can report the following:

Star Trek Voyager Elite Force and its Expansion Pack can be installed on Windows 10 64 Bit perfectly.

But: Last year Microsoft has removed old Safedisc/Securom copy protection drivers from all Windows versions back to Windows Vista. Not sure how it is with other versions but for Windows 10 the old work around and reactivation procedures will not work any longer, obviously since a major windows update from end of 2016. Holomatch Mode is not affected and will work nevertheless.

The only solution for the Single Player Mode so far seems to use modified execution files, with removed CD-check. But this is not that easy regarding how the patched executable working with new opengl DLLs and some other issues…not mentioning the legal questions. In my opinion using and sharing patched executable shouldn´t be a legal matter, since the source code was fully released with no restrictions and the game and its engine seems to be open source in fact…but I have to discuss this question.

Okay, stay tuned…I will think about a solution. Will you keep posted.

DON

Comments
Marcomix
Marcomix

...damn. I was hyped.

Reply Good karma Bad karma+1 vote
don_quichote Author
don_quichote

I am sorry for my followers and everyone else waited for this day... I am on it and hope to fix it asap.

Reply Good karma+2 votes
moduser
moduser

Scotty beem me up !!

Reply Good karma Bad karma+2 votes
MundaneRaptor
MundaneRaptor

My install seems to be working fine, you using the international version?

Did a little digging, evidently you can sign securom yourself according to rock, paper, shotgun (https://www.rockpapershotgun.com/2015/08/17/windows-10-safedisc-securom-drm/). There was a tool that did it for you but the article is fairly old & the linked to site is now down, luckily there's a Microsoft page on how to manually sign securom (https://docs.microsoft.com/en-us/windows-hardware/drivers/install/test-signing-a-driver-file).

I used to mod EF as well, there are still quite a few of us left who remember fondly our time in this game. Can't wait to see this mod in person.

Reply Good karma Bad karma+2 votes
don_quichote Author
don_quichote

Did you try that? I know about that option but I also read that this solution is outdated and Micorsoft closed this gap for safedisc/securom drivers.

You know... its no problem for me to use an executable with removed cd-check strings ;) There are basically two problems now... 1. it still remains unclear for me if this is now a legal procedure that I could share; 2. Somewhere in the code was written that the single player executable will not load a costume opengl32 DLL from the main directory, which is essential for the new shader engine. I can only solve this problem by re-naming the stvoy.exe (for example to stvoySP.exe). But when I do so, then the game starts with the new shader injector but unfortunately it comes to another ugly shadow glitch...

Reply Good karma+1 vote
Guest
Guest

My german version is also working without any issues on Win10 64bit.

Reply Good karma Bad karma+1 vote
don_quichote Author
don_quichote

Hi, I would assume that you are running the original game without the Expansion Pack? In this case, the problem does not occur ;) Buuut... on the other hand I also noticed that my mod is not working anymore without the Expansion Pack. No idea why at the moment. You see...I have to think about some issues again ;)

Reply Good karma+1 vote
Guest
Guest

I am running with expansion pack! I'm speedrunning the game so i played the singleplayer kind of consistently for the last 3 years and I didn't have a single issue on two different PCs with Win10 64bit.

Sure enough take your time, good work like this should not be rushed :) Just wanted to give you input that things are running smoothly for me.

Reply Good karma Bad karma0 votes
don_quichote Author
don_quichote

You can launch the game on Windows 10 64Bit, fully updated, with installed Expansion Pack and with the original and untouched 1.2 stvoy.exe? Curios.

Reply Good karma+1 vote
Guest
Guest

This comment is currently awaiting admin approval, join now to view.

Guest
Guest

I can run it all fine too on Windows 10 64-bit. V1.2 with Expansion installed. No issues.

Reply Good karma Bad karma0 votes
don_quichote Author
don_quichote

Curious... thanks for the info.

Reply Good karma+1 vote
Guest
Guest

Hey, I must be just in time, I literally just dusted off my old Elite Force CD-ROMs and installed it on Windows 10 for a bit of nostalgia and found this page. Any news on the release?

Reply Good karma Bad karma+1 vote
don_quichote Author
don_quichote

Friday... :D

Reply Good karma+1 vote
Guest
Guest

This comment is currently awaiting admin approval, join now to view.

STA2UA
STA2UA

Which Friday do you mean?

Reply Good karma Bad karma+1 vote
don_quichote Author
don_quichote

Well, yes actually the Fridy on Sunday July 9th was meant :D

Reply Good karma+1 vote
Guest
Guest

sooo? =(

Reply Good karma Bad karma0 votes
don_quichote Author
don_quichote

No worries new official and definite release date ist Sunday 9th July.

Reply Good karma+1 vote
MoritzJT
MoritzJT

Hey don_quichote have you tried renaming it to some more generic titles like quake3.exe or even ef2.exe?

It's either the graphics driver or some other windows magic that utilises the different loading paths and shader extensions.

I got my stvoy.exe to quake3.exe and run reshade 3.0.4 perfectly fine with EF1 and what is that shadow glitch you are talking about. Framedrop?

Reply Good karma Bad karma+1 vote
don_quichote Author
don_quichote

Hey MoritzJT, yes I discovered also, that the renaming to Quake3.exe will solve the problems. But on my machine it seems to work less stable since I noticed spontaneous framerate break ins...but besides of this it works fine now ;)

Reply Good karma+1 vote
MoritzJT
MoritzJT

r_primitives 2 to the help
also cap the FPS at 125
also...

NVIDIA Profile Inspector can force extension string limits - should avoid any shadow glitches, even if the exec remains stvoy.exe

Reply Good karma Bad karma+1 vote
Guest
Guest

This comment is currently awaiting admin approval, join now to view.

Post a comment
Sign in or join with:

Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.