New Release D3D9Client Development

[Mr. Residuals]

Strange, for me my D3D9 client wont save the advance settings. I'm using Orbiter Beta with the lates D3D9 client version for Beta.

 

[Mr. Residuals]

Strange, for me my D3D9 client wont save the advance settings. I'm using Orbiter Beta with the lates D3D9 client version for Beta.

It seems as if every time I exit out of Orbiter with my settings it just reverts back to default.

 

[Max-Q]

Strange, for me my D3D9 client won't save the advance settings. I'm using Orbiter Beta with the latest D3D9 client version for Beta.

My Orbiter Beta with D3D9 does the same thing. I have to manually edit the configuration file to make the settings stick.

 

[Face]

Perhaps this saving bug has something to do with the process termination hack. Check if it works with the shutdown options set to "deallocate" instead of "respawn".

 

[Mr. Residuals]

Perhaps this saving bug has something to do with the process termination hack. Check if it works with the shutdown options set to "deallocate" instead of "respawn".

Can't find that setting on my Hp laptop.

 

[Max-Q]

I tried all three shutdown options. Still no luck, in won’t save the settings.

 

[Face]

Can't find that setting on my Hp laptop.

It is an Orbiter setting. You can find it on the "Extra" tab.

 

[Mr. Residuals]

Perhaps this saving bug has something to do with the process termination hack. Check if it works with the shutdown options set to "deallocate" instead of "respawn".

Mine is already set to deallocate.

 

[jarmonik]

Where is your Orbiter installation ? If it's in a C:/Program Files/ then it might suffer some access rights issues. Also is the D3D9Client.cfg write protected somehow ?

Anyway, I have moved the state save from the end of the program to a start of it. So, next version should save it when simulation starts. I did suffer about the same problem my self couple of days but the problem disappeared as suddenly as it had appeared. So, the cause remained a mystery.

I wonder, would it be possible for an add-on to change working directory and getting the file misplaced as a result somehow.

 

[Max-Q]

The only add on I use in my beta install (other than D3D9, obviously), is NASSP.
The location is not protected, and my Orbiter2016 D3D9 saves the settings just fine.
I don’t think D3D9client.cfg is write protected, because I can edit it using Notepad++ just fine.

 

[Mr. Residuals]

C:/Program Files/

Yup that is where mine is.

 

[kuddel]

@DDasng1352 : I would then recommend to add the "write" right to the User account at that folder:

1. Right-click on the folder (C:/Program Files/Orbiter or what its name is);
2. select the "Security" Tab;
3. then click the "Edit..." button and confirm the windows UAC prompt;
4. select the User account (something like "Users (YOUR-LAPTOP\Users)") in the dialog that appeared;
5. now tick the "Write" checkbox and confirm (you can click "Apply" before "OK" if you wish ).

P.S.: I hope I got the naming of the dialogs/buttons/entries right, as I am using a German locale Windows.
P.P.S: I used to have one folder under C:/Program Files/Orbiter, that contained all my different Orbiter installations (like C:/Program Files/Orbiter/D3D9DevTrunk, C:/Program Files/Orbiter/NASSP or C:/Program Files/Orbiter/D3D9Dev2016). That way you only have to give the write-right to that one folder (C:/Program Files/Orbiter) and all subsequently added folders will automatically inherit the write-right in the future.
Giving the write-right for users to C:/Program Files folder however is not recommended! It's after all a security feature.

 

[Mr. Residuals]

@DDasng1352 : I would then recommend to add the "write" right to the User account at that folder:

1. Right-click on the folder (C:/Program Files/Orbiter or what its name is);
2. select the "Security" Tab;
3. then click the "Edit..." button and confirm the windows UAC prompt;
4. select the User account (something like "Users (YOUR-LAPTOP\Users)") in the dialog that appeared;
5. now tick the "Write" checkbox and confirm (you can click "Apply" before "OK" if you wish ).

P.S.: I hope I got the naming of the dialogs/buttons/entries right, as I am using a German locale Windows.
P.P.S: I used to have one folder under C:/Program Files/Orbiter, that contained all my different Orbiter installations (like C:/Program Files/Orbiter/D3D9DevTrunk, C:/Program Files/Orbiter/NASSP or C:/Program Files/Orbiter/D3D9Dev2016). That way you only have to give the write-right to that one folder (C:/Program Files/Orbiter) and all subsequently added folders will automatically inherit the write-right in the future.
Giving the write-right for users to C:/Program Files folder however is not recommended! It's after all a security feature.

Just did it, but I got some failures.

 

[Mr. Residuals]

Just did it, but I got some failures.

It says I don't have access to it, probably because I'm not the admin.

 

[Mr. Residuals]

@DDasng1352 : I would then recommend to add the "write" right to the User account at that folder:

1. Right-click on the folder (C:/Program Files/Orbiter or what its name is);
2. select the "Security" Tab;
3. then click the "Edit..." button and confirm the windows UAC prompt;
4. select the User account (something like "Users (YOUR-LAPTOP\Users)") in the dialog that appeared;
5. now tick the "Write" checkbox and confirm (you can click "Apply" before "OK" if you wish ).

P.S.: I hope I got the naming of the dialogs/buttons/entries right, as I am using a German locale Windows.
P.P.S: I used to have one folder under C:/Program Files/Orbiter, that contained all my different Orbiter installations (like C:/Program Files/Orbiter/D3D9DevTrunk, C:/Program Files/Orbiter/NASSP or C:/Program Files/Orbiter/D3D9Dev2016). That way you only have to give the write-right to that one folder (C:/Program Files/Orbiter) and all subsequently added folders will automatically inherit the write-right in the future.
Giving the write-right for users to C:/Program Files folder however is not recommended! It's after all a security feature.

So far for me, it's a short-term fix, it only last like 9 minutes.

 

[Arvil]

Mine are C:\Orbiter, then I keep download zips at C:\Orbiter\Downloads, then installations are C:\Orbiter\Orbiter1, C:\Orbiter\Orbiter2, like that. One of the few apps on the root directory.

 

[JDat]

Mine are C:\Orbiter, then I keep download zips at C:\Orbiter\Downloads, then installations are C:\Orbiter\Orbiter1, C:\Orbiter\Orbiter2, like that. One of the few apps on the root directory.

So? Most useless answer. Does this directory structure solve problem? YES or NO?

 

[Arvil]

Always worked well for me. This is maybe the third computer I’ve had it on. I don’t have the permission issues with having it inside other Program folders.

Edit: I had Orbiter since 2005. The .zip file download was the only installation method available at that time. Since then the installation file method was introduced, but, I’ve always preferred the .zip files. If something gets corrupted, I just backup the scenario files I want, delete the bad Orbiter folder, then unpack the .zip folder I already have into a new folder, add the scenarios, and play from there. Nothing ever written to the Windows registry.

 

[Mr. Residuals]

I always put orbiter in a program file, but when I do that the saving doesn't work.

 

[dbeachy1]

BTW as a matter of best practice / compatibility, it's best to always install Orbiter to a normal folder that has write permissions, such as C:\Orbiter. Installing Orbiter to something like C:\Program Files\Orbiter will cause permission headaches, as files under C:\Program Files are supposed to be admin-only anyway.