• New Horizons on Maelstrom
    Maelstrom New Horizons


    Visit our website www.piratehorizons.com to quickly find download links for the newest versions of our New Horizons mods Beyond New Horizons and Maelstrom New Horizons!

Solved Windows 10: Low Frame Rates Despite (BECAUSE OF!) Good Hardware

The difference is that ...

Initializing DirectX 8
Techniques: 20 shaders compiled.
Techniques: 211 techniques compiled.
Techniques: compiled by 381377464 ticks.

Release d3d8
Undefined error
Release d3d
Undefined error
Unloading
System exit and cleanup:
Mem state: User memory: 0 MSSystem: 0 Blocks: 0

The interfaces in the program library of source code ...
This is from AOP1 CT.
It works with Windows 10
Here DirectX 8 is detected.
At PotC it is not recognized.

@Simunkulus
From Windows 8 no longer. It has DirectX 11. See the SDK's on.
Only Windows 7 supports DirectX 10 and 9.
Windows 10 has DirectX 12. It supports only DirectX 11.
There are no longer supported older games.
The compatibility mode does not help here.
 
Last edited:
But we know that PotC does work on Windows 8 and 10; there is just the framerate issue.

@Jan Marten, would you mind sharing the files for your "Storm 2.5" version of PotC?
I'd quite like to give that a test myself to see what happens! :cheers
 
This has nothing to do with the framerate.
The problem is the legacy interfaces.
DirectX is the program library that controls everything.

The set of data into memory ... and remove it from the memory .. play a role here.
 
Last edited:
What you should know Pieter.
In the near future, we will publish an updated version of AoP1-CT.
The test prove, that it is stable on Windows 10.
We will try it .... I want to use some things from PotC.
There will be no further official information.
 
@Jan Marten Maybe it will help if you install Directx_June2010_redist.exe.
It solved some Direct X Problems for me. I run Win 8.1.
 
The DirectX runtimes from June 2010 will work in Windows 10 just fine, but you have to install them manually. Windows 10 will however stop older copy protection from running, and AOP had the worst copy protection ever invented in Starforce, this could possibly be why you are having problems running it in Windows 10. Are you using a cracked exe or the original?
 
Thagarr said:
The DirectX runtimes from June 2010 will work in Windows 10 just fine, but you have to install them manually. Windows 10 will however stop older copy protection from running, and AOP had the worst copy protection ever invented in Starforce, this could possibly be why you are having problems running it in Windows 10. Are you using a cracked exe or the original?
Click to expand...
I am against DirectX runtimes from June 2010. That is not the solution.
I have the original engine.exe. She has no copy protection.
It was published with the game in 2009 in the magazine "Computer Bild" in Germany.

www.dezeeroovers.net/CT/doc/010.png
 
Last edited:
Jan Marten said:
I am against DirectX runtimes from June 2010. That is not the solution.
I have the original engine.exe. She has no copy protection.
It was published with the game in 2009 in the magazine "Computer Bild" in Germany.

www.dezeeroovers.net/CT/doc/010.png
Click to expand...

Might I ask why you are against using the DirectX runtimes? I have them installed on Windows 10 and have absolutely no issues using them. :shrug

Interesting, I was not aware they had distributed the game with a magazine. Every release that I was aware of was saddled with Starforce. Just out of curiosity, what version number is that exe?
 
version number 2.5
Counterquestion - Thagrr
Why take an old DirectX. If it works with DirectX 12.:shrug
 
Jan Marten said:
version number 2.5
Click to expand...

Interesting.. that is the exe version number? I thought the latest was 1.41, or maybe 1.42 with the patch? It's been a while, I don't remember exactly.
Counterquestion - Thagrr
Why take an old DirectX. If it works with DirectX 12.:shrug
Click to expand...

Most older programs will run with DirectX 12, but the original calls are written for the DirectX 8 and 9 library's. DirectX 12 translates those calls to similar functions in the newer libraries. I am certainly no expert, but the way I understand it, the translation takes a bit of time, and the newer function calls don't work exactly the same. With the old runtimes, there is no translation and the calls do exactly what they were supposed to do.
 
AOP1 has better graphics than COAS.
Reason: The interfaces in the program libraries.
You can influence them from the outside in the engine.ini.
Are not interesting the config.exe and engine.exe
It does not matter which version you have.
I have something rewritten the source code.
Then compiled. The same config.exe and engine.exe run with AOP1 and AOP2 without problems.
So they are not the cause of problems. There are the program libraries.
 
With program libraries, do you mean the files in the PROGRAM and RESOURCE folders?
Or the MODULES?
 
I managed today to bring the artwork of COS on the sharpness of AOP1.
The slider of the graphics options to go now at COAS under Windows 8.1.
COAS is brighter, as AOP1
 
@Jan Marten you could consider using a wrapper like ReShade or ENB to make it use DX9 instead of DX8 and see if that does make it work on W8 or W10
 
@Hylie Pistof if you aren't using enb or reshade could you extract this to your potc folder (not program, the folder where the exe is located) and use the LAUNCHER.exe to start the game.
Please let me know if this works. It should cap your fps at 60
 

Attachments

  • FPS_LIMITER.zip
    223.2 KB · Views: 397
It DLed fine for me. I am trying it and all I get so far is a DOS box. Now what? It does not work so far, and yes I turned off all other fps limiters.
 
You must log in or register to reply here.
Back
Top