March 9, 201610 yr I have had an issue where SIMstarter will not modify the scenery.cfg file no matter what profile or scenery sets I choose. scenery_lastSIMstarterProfileRun.cfg is being written correctly, but it is not being copied over to scenery.cfg. I have a feeling it may have to do with the OrbX region switching
March 9, 201610 yr Commercial Member Hi, please: - post the SIMstarter.log file - tell me which version of SIMstarter you are using : : : aviation.pero-online.deDeveloper of SIMstarter NG P3D & Homecockpit Builder
March 9, 201610 yr Author The log file is empty, even though debugging is turned on in the options. I am using version 2.7.4. Every one of the User Profile .cfg files in the SIMStarter\Uer Profiles folder. (PREPAR3Dprofile02_config.cfg for example) is pointing to the same scenery set .cfg file (scenerySet=PREPAR3Dscenery1.cfg;), and that file has the Mastery Scenery set which is everything that I have installed which is not what I want. I'm not sure why this is as every profile is setup differently. I tried deleting all the User Profiles .cfg files and all my profiles are still there. Is there another folder where they are stored? Edit: Running as administrator recreated all the .cfg files I deleted as a test in the SIMStarter\User Profiles folder, but I have no scenery sets or anything saved. If I run as a normal user, my sets are still there but the program does not modify scenery.cfg again.
March 9, 201610 yr I had the same problem, but I don't remember 100% how I fixed it. I think, I went into the settings where you can specify the path to the scenery.cfg. Even though the path was in there correctly, it still didn't work. As far as I remember, I went into the context menu for the path and simply set the path again (to the same location) and then it worked. But as I said, I'm not 100% sure if this was the solution. But there was a rather easy fix for it. Maybe you can give it a try... [email protected] ∣ Asus ROG Strix B650E-E ∣ 64Gb@6000MT ∣ NVidia 5090 FE
March 10, 201610 yr Commercial Member Strange. I never heared about such issues before. Please send me: - folder ".\Userprofiles" - file "SIMstarter.ini" - file "SIMstarter.log" in a zip file to my email adress. You'll find it clicking "About" in SIMstarter. : : : aviation.pero-online.deDeveloper of SIMstarter NG P3D & Homecockpit Builder
March 10, 201610 yr Author I'll do that as soon as I get home. I did find out that SIMstarted was using C:\Users\Josh\AppData\Local\VirtualStore\Program Files (x86)\SIMstarter as it's root folder instead of c:\Program Files (x86)\SIMstarter. Running it as Administrator worked after i copied the profiles over to the correct folder.
March 16, 201610 yr Author I have moved SIMstarter out of Program Files and onto my D drive but now I get an error saying "Access to the path "C:\ProgramData\Lockheed Martin\Prepar3d v3\Simobjects.cfg is denied". I've never had this before so somewhere along the line my permissions have been messed up. I haven't changed anything to do with permissions so it must have happened when running SIMstarter as admin. When P3D loads it is not using the modified scenery.cfg file again either. It uses the one in the VirtualStore folder unless i run as admin.
March 17, 201610 yr Commercial Member Strange one. I never got such an error since the beginning of SIMstarter. The "Virtual Store" error indicates, that this happend because of the installation path and active UAC within window. To prevent such errors you should move SIMstarter outside of "C:\Program Files (x86)" what you have done now. The current error looks like a permission problem. So please double check the permissions and run SIMstarter with administrator rights. If all this does not work please wait until SIMstarter NG comes up (soon, whatever that means). I won't spend any time debugging SIMstarter because every free times goes to SIMstarter NG. Which P3Dv3 version are you using? v3.2 is not supportet with SIMstarter. NG will for sure. : : : aviation.pero-online.deDeveloper of SIMstarter NG P3D & Homecockpit Builder
Create an account or sign in to comment