January 3, 20197 yr Author Sir, I have spent countless hours since your last message (Dec. 31) and following the 22 steps in the instructions you sent and watching videos and reading other articles on the same subject, but NOTHING has changed with my ability to fully use Reality-XP in my FSX-SE system. I have compared the permissions issue to my boxed FSX version and there are no problems there. As I have said several times, this is the most frustrating issue I have ever had with an addon for my FSX-SE system in the five years I've had it. I would hope you could send me a workaround that would really work. Otherwise, I have to settle for your current addon only half working in my FSX-SE system. Very frustrated... Richard
January 8, 20197 yr Hi, I feel sorry for your frustration but at this stage, there is little or even nothing we can really do: the solution is prevented to write files into 'some' of your FSX-SE sub-folders, whereas it is working fine in your FSX sub-folders. The only reason (well most probable just to stay conservative) is a problem of files and folders access rights. Otherwise, it is a 3rd party add-on or 3rd party Windows program preventing any such folder/file modification. I can't fathom how involving this would be to you, but should your 'SteamLibrary' folder is within a protected folder (i.e. "C\:Program Files (x86)" you might want to consider 'migrating' the steam folder into a folder you'd have created manually beforehand, such as "C:\SteamLibrary". I think there is a 'migration' function in the steam app for this.
January 9, 20197 yr Author Sir, I have done EVERYTHING you have guided me to do. Including the following: "Jim Young Forums Administrator Administrators Posted June 11, 2013 This is a permission/sharing problem. You need to go to the C:\Program Data\Microsoft\FSX folder and right click on FSX and select share with all users. You might also do that to the Main FSX folder too making sure you apply to all sub-folders. All users on your computer are not allowed access to everything and you need to make sure everyone is allowed access. Best regards, Jim" As I said before, "That did not work. I still need assistance getting your product to work fully in my FSX Steam edition." Then I followed your guidance of: "...the aforementioned path is for FSX. You'd need to do the same on the FSX-SE equivalent folder!" I did that also. I did it all! STILL NO CHANGE! And, as I have said many times, "...this is the most frustrating issue I have ever had with an add-on for my FSX-SE system in the five years I've had it. I would hope you could send me a workaround that would really work. Otherwise, I have to settle for your current addon only half working in my FSX-SE system." The most recent suggestion you offered of "'migrating' the steam folder" is quite interesting. In the 5 years I've had FSX-SE, ALL add-ons have migrated with/into FSX-SE with NO problems. You are the only one to suggest that and only after all these attempts to FORCE YOUR add-on product to work. And, I am doing all the work! Please provide a solution. Thanks, Richard
January 9, 20197 yr Hi Richard, it is kind of chicken and egg discussion, and believe me, I'm really not trying to put aside any assistance to you, but the truth of the matter is well explained and documented: Windows protects access to files and folder using 'access control lists' (ACL) Whenever you or a program running for you (under you logon credentials) access a file or a folder, Windows checks whether the operation has 'access rights' to complete. Whenever it fails, it is access rights preventing it. There is nothing anyone can do to change access rights but the logged on computer user behind his keyboard. This is all designed since at least Windows NT, further enhanced in subsequent Windows versions, to support multi-user systems and/or to clearly set boundaries between 'regular' users and 'admin' users of the computer. Really, the fact it runs perfectly fine on your FSX installation means there is no problem between our product and your system. The fact it fails to update only 'some' files in your FSX-SE installation means these files, or the folder they are in, or any parent folder up the chain, is preventing our add-on, running under your user logon credentials, to update the files. What else can we do from here?
January 11, 20197 yr Author Sir, Thank you again for your response. As you can probably tell, I am determined to get this to work, even with my limited technical abilities. I want to present the following to you for your review and response back to me if I have this all wrong and have screwed up my system. Please keep in mind that as I have said your add-on product works fine in FSX (boxed) and added in without any problems. With FSX-SE, I finally got the Reality-XP Configuration menu to appear in all aircraft, BUT the "GPS panel" does NOT show up in all aircraft. So with that, here is how my computer system is now set up regarding this whole Reality-XP add-on process: Computer FSX/FSX-SE/Reality-XP “Permission” related settings, as of Jan.8, 2019: FSX-Steam edition (FSX-SE): C:\Users\owner\AppData\RoamingMicrosoft\FSX –SE\sharing (shared)\Security (Everyone) C:\Users\owner\AppData\RoamingMicrosoft\FSX –SE\simobjects\sharing (shared)\Security (Everyone) C:\Users\owner\AppData\RoamingMicrosoft\FSX –SE\fsx.exe\sharing (shared)\Security (Everyone) C:\Users\owner\AppData\RoamingMicrosoft\FSX –SE\ fsx.sex.cfg.\sharing (shared)\Security (Everyone) C:\Users\owner\AppData\RoamingMicrosoft\FSX –SE\ panel.cfg.\sharing (shared)\Security (Everyone) C:\ProgramData\Microsft\FSX –SE\sharing (shared)\Security (Everyone) Note: for all FSX-SE settings in Program Files (86), settings now sharing (shared)\Security (Everyone) FSX boxed (FSX): C:\Users\owner\AppData\RoamingMicrosoft\FSX\sharing (not shared)\Security (SYSTEM) C:\Users\owner\AppData\RoamingMicrosoft\FSX\simobjects\sharing (shared)\Security (owner-PCAdmins.) C:\ProgramData\Microsft\FSX\sharing (not shared)\Security (Admins (owner-PC/Admins) C:\ProgramFiles(86)\MicrosftGames\FSX\SimObjects\sharing (not shared)\Security (SYSTEM) For Reality-XP: All Reality-XP related settings, now set to: shared and in Security to Everyone Also found in C:\Users\owner\AppData, under Recent found rxpGTN-FS; changed it to share/Everyone. Also found in C:\Users\owner\AppData, under Videos found ZIP files rxpGTN-FS.zip; changed it to share/Everyone. When tried to open and unzip files, got error message that my user name and/or password were wrong, or something regarding either or invalid something or exceeded attempts. Please let me have your guidance regarding all this. Thanks, Richard
January 11, 20197 yr 39 minutes ago, RSomerville said: As you can probably tell, I am determined to get this to work, even with my limited technical abilities. Hi, I thank you for your enduring patience and as you can tell, we're determined to help you too! On 1/7/2019 at 7:41 PM, RXP said: should your 'SteamLibrary' folder is within a protected folder (i.e. "C\:Program Files (x86)" you might want to consider 'migrating' the steam folder into a folder you'd have created manually beforehand, such as "C:\SteamLibrary". I think there is a 'migration' function in the steam app for this. You're probably missing the most important of them all: the folder into which the FSX-SE program, gauges, scenery, aircraft etc.. are installed. See with FSX, it is:C:\ProgramFiles(86)\MicrosftGames\FSX\SimObjects\ The equivalent with FSX-SE is (default path):SteamLibrary\steamapps\common\FSX\SimObjects\ Wherever you've installed the 'SteamLibrary', it is there you'd need to cross-check access rights.
January 11, 20197 yr Author Sir, Thank you again for your response. You said: You're probably missing the most important of them all: the folder into which the FSX-SE program, gauges, scenery, aircraft etc.. are installed. See with FSX, it is:C:\ProgramFiles(86)\MicrosftGames\FSX\SimObjects\ The equivalent with FSX-SE is (default path):SteamLibrary\steamapps\common\FSX\SimObjects\ Wherever you've installed the 'SteamLibrary', it is there you'd need to cross-check access rights. I searched everywhere and I do not see 'SteamLibrary' anywhere. I did find a "LibraryFolders" in SteamApps, but nothing in it. Please advise, Richard
January 11, 20197 yr Well, your FSX-SE is installed somewhere, chance is it is in your 'SteamLibrary' folder. Given you don't have a 'SteamLibrary' folder, you're certainly using the default location instead. A quick internet search with 'SteamLibrary folder location' keywords gives plenty of info like: https://support.steampowered.com/kb_article.php?ref=7710-tdlc-0426 https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129
January 12, 20197 yr Author Sir, My system does not have a 'SteamLibrary' folder. It has a main 'Steam' folder where everything related to 'Steam' is located. The folder is located within the "C\:Program Files (x86)" folder. I have examined all files related to FSX-SE and Reality-XP and the access rights, that I can find, and they are the as I previously described - "sharing (shared)\Security (Everyone)." I have extensively reviewed and compared both my FSX and FSX-SE files. As I have said before Reality-XP works fine in FSX and added in without any problems. With FSX-SE, the Reality-XP Configuration menu to appears in all aircraft, BUT the "GPS panel" does NOT show up in all aircraft. HERE is the key thing I have noticed regarding Reality-XP in my FSX-SE system is that Reality-XP DOES NOT work in the FSX-SE DEFAULT aircraft, BUT it does work in my added on aircraft such as from A2A and Carenado and others. How would you address this odd situation? Thanks, Richard
January 12, 20197 yr 1 hour ago, RSomerville said: Reality-XP DOES NOT work in the FSX-SE DEFAULT aircraft, BUT it does work in my added on aircraft such as from A2A and Carenado and others. This further confirms the theory of access rights: 3rd party vendor installers create their aircraft folder with (100% confident) 'every' access rights, whereas stock aircraft get installed with the original FSX-SE installer and the original 'restricted' access rights. Please note again: there are 2 (not 1) Steam folder: one for the steam program, one for the steam applications you've purchased trough steam. The whole question is the later, not the former. Please try to connect the two together: what is the full path to the stock FSX-SE B58 aircraft panel folder on your hard drive?
January 12, 20197 yr Author Thank you again for your response, I searched for the 'second' Steam folder. I saw only one that I thought would work and changed it to match the access settings. That did not work. Here is the path you requested: C:\Program Files (x86)\Steam\SteamApps\common\FSX\SimObjects\Airplanes\beech_baron_58. For me, it's still a mystery. Richard
January 12, 20197 yr These are folders which you must check access rights: C:\Program Files (x86)\Steam\SteamApps\common\FSX\SimObjects\Airplanes\ C:\Program Files (x86)\Steam\SteamApps\common\FSX\SimObjects\ C:\Program Files (x86)\Steam\SteamApps\common\FSX\ NB: access rights gets inherited down the chain, so you verify the chain up starting from the innermost folder up to the outermost parent (FSX). I'd suggest you compare the access right to a 3rd party aircraft folder located inside SimObjects\Airplanes which is known working on your system, to the access rights of Airplanes, SimObjects and FSX to spot whether there are any differences. Besides, we've released a new version v2.5.11, including a few changes in the 'menu' code, which may prove worthy on your system.
January 12, 20197 yr Author Sir, I have checked everything and verified everything as you suggested - still no change. How do I get your new version? Is that an update or a whole new product? Richard
January 12, 20197 yr Author Sir, With all due respect, I do not understand how to get your new version from what you provided above. I may be technically limited, but I am not dumb. What "Settings Panel" and where is that? I went to your website and did not see anything relative to "v2.5.11 New: Autopilot NAV->APPR automatic sequencing..." Please communicate plainly for my level of understanding. Thanks, Richard Richard
Archived
This topic is now archived and is closed to further replies.