Misc GTR2 16th Anniversary PATCH Part-1 16.0.0

[The Iron Wolf]

I don't see where you tested a fresh GTR2 ?

Installed GTR2 Steam to my main sim tower ( old gmotor is on my 3400G )
set compat W7 and admin for all users
Ran GTR2 once check
Ran CrewChief ( I keep a old version installed in TOOLS runs from a fresh Windows )
Started CC updated to latest version installed back to TOOLS not C:\
Re-start, downloaded the 3 packs
picked a name
added GTR2 location
re-started CC clicked Start
Started GTR2 through Steam
Ran quick race with ai control ( not at rig )
Worked fine as far as I can tell
So try a fresh GTR2
Always keep a backup of a fresh GTR2 install (before anything is added)

P.S. Jempy right , I said I had changed admin but when I just checked I had not

You probably know that, but just in case - keep in mind you don't need steam to run steam GTR2.exe. After you download the game, you can copy it out of Steam and then use that clean copy for new GTR2 copies. In fact, if you check plugin manual, I do not recommend running game from under Steam - it could cause problems. Same about compat modes - setting them is asking for trouble with this plugin. But, of course up to you

 

[Durge Driven]

Yes I know all that no matter it can always help someone else
That is why I always speak in 3rd person

I don't run GTR2 in steam and my standalone versions are slip streamed for my GTR2 / PnG / GTL / rFactor "essentials mods" which have every file every mod packed for jsgme / ovgme and are no longer available, so they would make no sense to most.

That is why I use fresh steam so to test default files

 

[The Iron Wolf]

I just realized that I have many computers, so I decided to do a test on them for fun. Luckily, GTR2 is tiny and copyable, so I put it on a USB stick and went on adventure.

In DX9 mode, Plugin worked with no problems on all the four computers I tested (3 laptops and one older PC).

My fork of DXVK worked correctly on a laptop running Nvidia Quatro GPU. However, I was not able to get it to set correct resolution on PC running AMD RX 580. And, DXVK did not work at all on Intel integrated GPUs.

All in all, I have no idea why Plugin does not run for some people (DX9 is the default configuration, because of the reasons above).

 

[jgf]

I just realized that I have many computers, so I decided to do a test on them for fun. ...

All in all, I have no idea why Plugin does not run for some people (DX9 is the default configuration, because of the reasons above).

This may not be pertinent but I'll toss it out for reference. All DX is backwards compatible; DX11 contains everything in DX10, DX10 contains everything in DX9, etc. But, not all software is forward compatible; starting with DX10 MS consolidated the functions into fewer, larger, files. Most newer software calls functions by name so there is no problem, windows finds and loads the file; but some DX9 software calls the functions by path and name, and windows reports a "file not found" to that program. The function is there in DX11 but not on the requested path. So no matter what new DX you have you may have to install the old DX9.0c alongside it. When windows receives a function call it will start with the most recent DX files and work its way back til it finds the required function.

A few years ago someone delved into this and noted which files were the problematic ones, then made a universal DX "update" containing just the necessary files; this seems to cure the vast majority of DX9 related issues.

 

[theguy69]

I just realized that I have many computers, so I decided to do a test on them for fun. Luckily, GTR2 is tiny and copyable, so I put it on a USB stick and went on adventure.

In DX9 mode, Plugin worked with no problems on all the four computers I tested (3 laptops and one older PC).

My fork of DXVK worked correctly on a laptop running Nvidia Quatro GPU. However, I was not able to get it to set correct resolution on PC running AMD RX 580. And, DXVK did not work at all on Intel integrated GPUs.

All in all, I have no idea why Plugin does not run for some people (DX9 is the default configuration, because of the reasons above).

Does choosing the crew chief option from HQ Anniversary patch change something in the exe? Or is it juust that the files are copied? The exe for whatever eason is just not running without compatibility mode. Also if I run just the gtr2config wuthout administrator it creates the gtr2 config file in the documents folder instead of the games root directory.

Edit - Installing crewchief plugin fixes this behaviour and the game no longer creates config file in documents folder but the game doesn't start either. Just black screen for like 2 seconds and then back to desktop. Could you please suggest what else I can try?

 

[theguy69]

Is everybody else able to run the digital exe without windows compatibility mode on windows 10?

 

[Jempy]

I wonder wether you didn't forget something ( something that HQ Anniv readme mentions ):
- Microsoft Visual C++ vc redist 2010 sp1 with MFC security update (required for Steam/GTR2 DIGITAL EXE)
- Microsoft Visual C++ vc redist 2015-2019 (required for CrewChief)

Win10 for me and Digital exe runs without compatibility mode.
And 2 different installs are working but located on another disk than C: and not in Steam or a Steamapps separate folder.

 

[The Iron Wolf]

I wonder wether you didn't forget something ( something that HQ Anniv readme mentions ):
- Microsoft Visual C++ vc redist 2010 sp1 with MFC security update (required for Steam/GTR2 DIGITAL EXE)
- Microsoft Visual C++ vc redist 2015-2019 (required for CrewChief)

Win10 for me and Digital exe runs without compatibility mode.
And 2 different installs are working but located on another disk than C: and not in Steam or a Steamapps separate folder.

Plugin manual also mentions all redists GTR2 and Plugin needs, however, in my experience you would get message box about missing dependencies - I got it on all 4 PCs I tested yesterday, and I had to install redists listed in my manual.

@theguy69 - unfortunately, I am out of ideas - if you have all the right files copied, running Win 10 64bit, and it still does not start I sadly have no clue, and judging from my own experiment yesterday I am now confident it should work even on AMD GPU (in DX9 mode). And I know that Retrolux runs this Plugin on AMD CPU no problems.

HQ Anniversary just copies files. .exe included there is slightly modified, but those modifications should be safe with my Plugin. I'll check later today if Plugin runs with .exe from Anni.

 

[theguy69]

Plugin manual also mentions all redists GTR2 and Plugin needs, however, in my experience you would get message box about missing dependencies - I got it on all 4 PCs I tested yesterday, and I had to install redists listed in my manual.

@theguy69 - unfortunately, I am out of ideas - if you have all the right files copied, running Win 10 64bit, and it still does not start I sadly have no clue, and judging from my own experiment yesterday I am now confident it should work even on AMD GPU (in DX9 mode). And I know that Retrolux runs this Plugin on AMD CPU no problems.

HQ Anniversary just copies files. .exe included there is slightly modified, but those modifications should be safe with my Plugin. I'll check later today if Plugin runs with .exe from Anni.

Oh well! Its a shame. Thank you for your time trying to help resolve this and while it doesn't work on my machine I still wanna thank you for the amazing work you have put in the plugin. Its really awesome thaat you've been able to add all these amazing features to this sim

 

[theguy69]

One last thing guys, I ran gtr2 from the gtr2_setup with log file enabled and this is what I got in trace.txt file. Let me know if it means anything t you guys or if you notice something unusual

Spoiler: trace.txt

TRACE LEVEL = 100
NetComm.cpp 8040: NetComm checking command line: "-trace=100"
game.cpp 661: Entered Game::Enter()
osman.cpp 469: Entered OSMan::Enter()
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
setup.cpp 1268: Could not find .HDC
vidman.cpp 1011: Entered VidMan::Enter()

 

[The Iron Wolf]

Oh well! Its a shame. Thank you for your time trying to help resolve this and while it doesn't work on my machine I still wanna thank you for the amazing work you have put in the plugin. Its really awesome thaat you've been able to add all these amazing features to this sim

thank you for your kind words. Sadly, because how invasive and complex this Plugin is, and because I can't have access to every single PC out there, sad reality is that there will be PCs where this simply won't work.

One last suggestion: if you did not do that already, please, try doing everything manually, don't use scripts etc. Make sure your CC is latest version, and if possible try as clean GTR2 as possible - don't mix many things in. Then, follow my manual to the letter, copying files manually. jgf has a point BTW - it won't hurt reinstalling redists from "Requirements" section of the manual. Also, you do not need to run CC app for Plugin to work (although CC app is fully integrated with the new game features I added).

I tried GTR2.exe from HQ Anni, it worked.

In other good news - I got DXVK to work on AMD RX 580. I forgot that by default, Windows blocks powershell scripts. Once I changed the policy and ran my workaround script DXVK ran fine. So, 2 out of 4 secondary machines (far from high end specs BTW) are fully compatble with my plugin, only Intel graphics is a problem (but plugin still works correctly in DX9 mode there).

PS: if you get it to run, let me know what it was.

 

[Jempy]

It works only by following with precision what's mentioned in the manual.
Anything not done correctly according to those instructions will not allow GTR2 to work correctly without any crash.

With such an immediate crash, @theguy69 ... a trace file doesn't give any clue to the problem.
If the game is launching and the crash happens when only launching a session on track, the trace file in this case can tell enough to mostly solve the problem.

NB read, apply and be cautious to respect all advices to the letter and it will work.

 

[theguy69]

thank you for your kind words. Sadly, because how invasive and complex this Plugin is, and because I can't have access to every single PC out there, sad reality is that there will be PCs where this simply won't work.

One last suggestion: if you did not do that already, please, try doing everything manually, don't use scripts etc. Make sure your CC is latest version, and if possible try as clean GTR2 as possible - don't mix many things in. Then, follow my manual to the letter, copying files manually. jgf has a point BTW - it won't hurt reinstalling redists from "Requirements" section of the manual. Also, you do not need to run CC app for Plugin to work (although CC app is fully integrated with the new game features I added).

I tried GTR2.exe from HQ Anni, it worked.

In other good news - I got DXVK to work on AMD RX 580. I forgot that by default, Windows blocks powershell scripts. Once I changed the policy and ran my workaround script DXVK ran fine. So, 2 out of 4 secondary machines (far from high end specs BTW) are fully compatble with my plugin, only Intel graphics is a problem (but plugin still works correctly in DX9 mode there).

PS: if you get it to run, let me know what it was

I tried changing windows powershell scripts but it didn't work. The game just does not work without compatibility mode. Are all of you guys able to run the game on win 10 without any patch without compatibility mode? Also if I try to run game in win8 compatibility mode it crashes with error 0xc0000005. This application was unable to start correctly

 

[The Iron Wolf]

I tried changing windows powershell scripts but it didn't work. The game just does not work without compatibility mode. Are all of you guys able to run the game on win 10 without any patch without compatibility mode? Also if I try to run game in win8 compatibility mode it crashes with error 0xc0000005. This application was unable to start correctly

If you are running CC plugin you do not need compatibility modes and admin, because I actually figured out why compat modes were needed and fixed that problem via the plugin, at least on Win10 (in the future, more work might be needed as Win10 gets old). In fact, compat modes will harm the plugin, as it uses some modern OS capabilities (you may get lower framerate and crashes depending on what plugin features are on) . Problem is - plugin does not work for you it seems

For running without the Plugin, simply follow HQ Anniversary readme.

 

[theguy69]

If you are running CC plugin you do not need compatibility modes and admin, because I actually figured out why compat modes were needed and fixed that problem via the plugin, at least on Win10 (in the future, more work might be needed as Win10 gets old). In fact, compat modes will harm the plugin, as it uses some modern OS capabilities (you may get lower framerate and crashes depending on what plugin features are on) . Problem is - plugin does not work for you it seems

For running without the Plugin, simply follow HQ Anniversary readme.

I got it working. I don't exactly know how and why my fix is making it work but its working.
What I did? I installed Microsoft Application Compatibility Toolkit from the Microsoft Assessment And Deployment Kit from here https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

Now I started Microsoft Compatibility Application Toolkit by running the exe in Compatibility Administrator(32 bit) folder ( C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Application Compatibility Toolkit\Compatibility Administrator (32-bit) ) and created a custom database and added Application Fix. In the application fix I added gtr2 digital exe and in the compatibility fixes window(there are like 436) I ticked the "VirtualRegistry" fix and clicked run and gtr2 was running with crew chief plugin. Now I saved this database as sdb file and right click on the database in ACT and clicked install and now gtr2 runs with crew chief plugin.

I don't really know what exactly the "VirtualRegistry" fix does. The description in ACT is, "Hooks all the registry functions to allow virtual keys, redirection and expansion values.". I don't really understand what this means currently but it has fixed gtr2 and now gtr2 is running with crew chief plugin and doesn't instantly CTD. I would greatly appreciate if maybe you or anyone else on this thread with more knowledge than me could explain to me why exactly this compatibility option is making gtr2 work.

 

[The Iron Wolf]

I got it working. I don't exactly know how and why my fix is making it work but its working.
What I did? I installed Microsoft Application Compatibility Toolkit from the Microsoft Assessment And Deployment Kit from here https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

Now I started Microsoft Compatibility Application Toolkit by running the exe in Compatibility Administrator(32 bit) folder ( C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Application Compatibility Toolkit\Compatibility Administrator (32-bit) ) and created a custom database and added Application Fix. In the application fix I added gtr2 digital exe and in the compatibility fixes window(there are like 436) I ticked the "VirtualRegistry" fix and clicked run and gtr2 was running with crew chief plugin. Now I saved this database as sdb file and right click on the database in ACT and clicked install and now gtr2 runs with crew chief plugin.

I don't really know what exactly the "VirtualRegistry" fix does. The description in ACT is, "Hooks all the registry functions to allow virtual keys, redirection and expansion values.". I don't really understand what this means currently but it has fixed gtr2 and now gtr2 is running with crew chief plugin and doesn't instantly CTD. I would greatly appreciate if maybe you or anyone else on this thread with more knowledge than me could explain to me why exactly this compatibility option is making gtr2 work.

Great stuff here I installed ACT as well last week to investigate that RX 580 problem I mentioned.

My guess is that you have some special security/Group Policy configuration applied to your computer. It can be through work, or through some tool you installed, but I am just guessing. My plugin itself is not currently using registry, but perhaps some libraries do, and sounds like they were failing previously. This is quite crazy.

 

[theguy69]

Great stuff here I installed ACT as well last week to investigate that RX 580 problem I mentioned.

My guess is that you have some special security/Group Policy configuration applied to your computer. It can be through work, or through some tool you installed, but I am just guessing. My plugin itself is not currently using registry, but perhaps some libraries do, and sounds like they were failing previously. This is quite crazy.

It indeed is crazy. I am wondering if I should make a seperate tutorial post for this for other people who run into this issue. At any rate I am glad I can now use your absolutely kick ass plugin now!!

 

[The Iron Wolf]

It indeed is crazy. I am wondering if I should make a seperate tutorial post for this for other people who run into this issue. At any rate I am glad I can now use your absolutely kick ass plugin now!!

I know your intentions are good, but it could cause more harm than good, by adding more confusion. If you own that laptop you are running (I mean, it is not some corporate device or something) I am pretty sure you won't need this workaround if you do a clean windows reinstall. This is some unusual security configuration if you ask me, plugin is used by hundreds of people without such issue.

Well, have fun

 

[Daltonegra]

Question.

I have a full PnG installation / mode 2 / GTR2 files removed - JUST PnG. With CC plugin. Derived from steam version.

Can I add this HQ anniversary patch over this mod? I have searched but didn't found direct answer.

Regards, Jure.

 

[GTR233]

Question.

I have a full PnG installation / mode 2 / GTR2 files removed - JUST PnG. With CC plugin. Derived from steam version.

Can I add this HQ anniversary patch over this mod? I have searched but didn't found direct answer.

Regards, Jure.

of course it works but when you run GTR2_SETUP.CMD you must follow specific options that I have highlighted in screenshots below (you can set other options pages as you like) : original png3 ui has got a memory leak so you must update it with one of mines that I have patched (you can keep png3 design or try other hq gtr2 ui if you prefer), install png3 hq anniversary patch to fix some bugs (either with my physics or with original physics, you will get moving wipers with both), install my png3 safety car patched (original has got a delayed start bug that I have fixed), install my png3 iroc driving school to enable driving school for png3 (there is none in original mod), as you use crewchief then install specific crewchief wipers (you will have specific wiper button so you can turn them off/on whether it rains or not).