b3burner Posted May 9, 2015 Share Posted May 9, 2015 Well, I had always wanted to try it, and early this morning was my first chance. After hearing nightmare stories about the lack of professionalism that you'd see (as compared to VATSIM), and how the kiddies run a muck, I found it to not be exceedingly bad after all. Maybe I found a good group. The meeting was in Cork, Ireland. Had a couple questions about it: 1. I saw someone with a B727 Champion Air that is the same exact model I have in my collection. That just seemed like way too much a coincidence. More than likely was the simulator just grabbing the closest thing I have in my collection to represent his plane-- since his was most likely non-stock? 2. When keying the mic is there really a true distinction between CapsLock (transmit) and Shift + CapsLock (transmit all)? Or does it depend on whether ATC opens the conversation up to all to begin with? 3. Is Multiplayer more likely to cause 'sim1.dll' crashes that regular free-play? I ask because before this morning, I had never had a sim1.dll crash, and then in multiplayer it happened twice. Again, seems like quite the coincidence. (But the good news is that the UIAutomationCore.dll errors appear to be finally leaving me alone!). Somewhere I read that reading a bad texture off a plane can cause it, and it occurred to me that I haven't added many addon planes to my FSX as of yet, and so maybe it was somebody else's plane in the multiplayer session that triggered it. Likely? Or probably not? If the "sim1.dll" error is likely something else wrong with my program, what might be the first thing I should do? 4. Steam never gave me the option of installing FSX in the C-root directory like I would have preferred. It stuck it in Programs Files (X-86), and now I'm hoping (being a windows 7 user) that's not too big an issue. I wouldn't know how to reinstall the whole thing over again if I had to. It's not like it came with discs. They own it, not me... even though I paid for it (I think). -- John Link to comment Share on other sites More sharing options...
loki Posted May 9, 2015 Share Posted May 9, 2015 Well, 4. Steam never gave me the option of installing FSX in the C-root directory like I would have preferred. It stuck it in Programs Files (X-86), and now I'm hoping (being a windows 7 user) that's not too big an issue. I wouldn't know how to reinstall the whole thing over again if I had to. It's not like it came with discs. They own it, not me... even though I paid for it (I think). -- John Steam does allow you to install games elsewhere. In the Steam settings you can setup multiple library locations, which you can then choose from when installing a game. It is also possible to move a game after it has been installed (including to a new computer) using the steps below. https://support.steampowered.com/kb_article.php?ref=7710-tdlc-0426 Link to comment Share on other sites More sharing options...
b3burner Posted May 10, 2015 Author Share Posted May 10, 2015 Loki, Thanks for the reply though this does bring up more questions than answers for me: 1a. Are you saying that I can simply cut and paste to a new location the FSX folder that Steam has already created for me (from my purchase back in late January), without doing an un-install and a whole new fresh install? ------------------- This is news to me, because back when I first got my new computer people advised me not to move my already exisiting FS9 from my H-drive (external hard drive) to my C-drive, because of already exisiting registry files that tell my computer of the H location. That it was best to do a fresh disc install of FS9 and put it directly in the C-root, under C:\FS2004\..., which I did. -------------------- 1b. Now are you saying that those rules no longer apply, and I'm free to move an already existing folder of FSX manually to a new location, without worrying about registry files, and without worrying about a fresh install in the new location? 2. The instructions say, "#3) Delete all of the files and folders except the SteamApps folder and the Steam.exe. 4) Cut and paste your steam folder to the new location, for example: D:\Games\Steam\..." 2a. But is there a way to just go C:\FSX\... direct? 2b. Or follow the directions to the letter as written and I have to keep the main "Steam" folder? If 2b. is the more correct method, then the best I'm going to do for a direct C-root directory install is going to be C:\Steam\..., and there is no way to go C:\FSX\... 3. Ultimately at the end of the day, are the exact details of whether or not the steam folder gets included or not, not nearly as important... just so long as the whole thing is removed from the 'Program Files (x86)" folder? -- John Link to comment Share on other sites More sharing options...
b3burner Posted May 10, 2015 Author Share Posted May 10, 2015 3. Is Multi-player more likely to cause 'sim1.dll' crashes that regular free-play? I ask because before this morning, I had never had a sim1.dll crash, and then in multi-player it happened twice. Again, seems like quite the coincidence. (But the good news is that the UIAutomationCore.dll errors appear to be finally leaving me alone!). Somewhere I read that reading a bad texture off a plane can cause it, and it occurred to me that I haven't added many addon planes to my FSX as of yet, and so maybe it was somebody else's plane in the multi-player session that triggered it. Likely? Or probably not? If the "sim1.dll" error is likely something else wrong with my program, what might be the first thing I should check? Any thoughts on this one? Link to comment Share on other sites More sharing options...
loki Posted May 10, 2015 Share Posted May 10, 2015 If you have only have the sim installed, or maybe just have a some freeware add-ons, it is possible to copy the FSX folder to a new location. Flight1 has a tool to repair the registry entry. This works with FS9 too. http://www.flight1.com/view.asp?page=library The main issues with doing this have to do with third party add-ons, usually commercial ones, that have made their own registry entries that reference the original sim location. Those instructions I linked to will move the entire Steam installation to a new location. It is also possible to create multiple libraries through the Steam settings and move games to them, while leaving Steam itself installed in the original Program Files location. 3. Ultimately at the end of the day, are the exact details of whether or not the steam folder gets included or not, not nearly as important... just so long as the whole thing is removed from the 'Program Files (x86)" folder? Yes, the main point is just to be anywhere outside the protected system folders, such as Program Files. Link to comment Share on other sites More sharing options...
b3burner Posted May 10, 2015 Author Share Posted May 10, 2015 Ok Loki... good enough. Gotcha' thanks. I'm curious if moving FSX out of the Program Files folder might cut down on my various .dll errors and unknown errors that crop up from time to time... or most likely not? Link to comment Share on other sites More sharing options...
pvarn Posted May 10, 2015 Share Posted May 10, 2015 The only real advantage of moving ANY program (particularly games) outside protected directory locations is for the convenience of modding. In the protected areas, you need administration rights and the account control nags. Outside program files, those problems go away. As far as dll crashes and broken installations of add-ons which do not understand the Steam directory structure, no, those problems will not go away on their own. When users choose to install add-ons using automated installers or by extracting archive collections, both are prone to errors and these cannot be totally eliminated. Your problems can be corrected by carefully inspecting the Windows Event Viewer, reporting the results here and carefully applying suggested resolutions. I would suggest that ultimately, it's YOU not the program which benefits the most from simplifying your FS installation path. -Pv- 2 carrot salad, 10.41 liter bucket, electric doorbell, 17 inch fan, 12X14, 85 Dbm Link to comment Share on other sites More sharing options...
b3burner Posted May 10, 2015 Author Share Posted May 10, 2015 Pv, Okay thanks for the helpful hints. I am running FSX Steam stock, bare bones, no special addons-- other than two freeware planes I imported from FS9 that I like. And those are nothing too terribly special... believe-u-me! LOL If Loki's "got his ears on" and happens across this post... Loki, I can tell you that my reinstall of FSX-Steam to another location was successful, though I did wind up having to follow the instructions to the letter. C:\FSX... all by itself without any regard for the Steam folder whatsoever wasn't going to cut it. FSX steam by it's very nature looks for the steam program and the file that helps open it (be it online or offline). If it can't find it, it tells one that there's an error and to look for solutions as to why it couldn't find it, etc. etc. So to make a long story short, I opted for a C:\Steam\steamapps\common\FSX... setup, and my goal of getting it out of the "Program Files (x86)" folder was successful. Now whether I could have foregone the "Steam" folder and started at the "steamapps" folder, and completely removed the "FSX" folder from the "common" folder and bypassed it to go directly ...steamapps\FSX..." --- I do not know. The directions from the Steam link didn't say to do that, and I didn't want to take chances. If it works now and it's out of the program folder, I figure it's wise to not mess with it any further. Link to comment Share on other sites More sharing options...
loki Posted May 11, 2015 Share Posted May 11, 2015 Glad you got it working. Don't think there is an easy way to just do the C:\FSX setup with Steam. I added a second Steam library on a second drive, and Steam still created the \Steam\steamapps\common directory structure. For quick access you can just create a shortcut on your desktop that takes you straight to the FSX folder. Link to comment Share on other sites More sharing options...
b3burner Posted May 11, 2015 Author Share Posted May 11, 2015 For quick access you can just create a shortcut on your desktop that takes you straight to the FSX folder. Yup... present and accounted for! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.