TextRich

I don't understand this part. What do you mean by "has a green checkmark"? As in "Enabled" with Red being "Disabled"? Or one out of the three check mark boxes is green and the others are red or? Being more specific with the issues now would provide more clarity. Many thanks. Just to save a bit more time down the road, do you recall where you purchased your UTX USA from? And when? I can't help but wonder if your installer was made BEFORE FSX:SE was even released.

Paul, I wonder if you did not see options for both because at the time you installed UTX you did not yet have FSX:SE, so the installer did not detect two simulators? If you uninstall and reinstall UTX, you should be given options. So have you tried that? If you feel it would be easier to have a clean slate and completely uninstall both FSX (and uninstall UTX as well), that's fine, sometimes it is less work that way to be honest. However I would personally suggest that you not re-install the boxed edition at all. As long as you have the Steam edition you will not need the boxed edition at all, and it will just get in the way of future add-on installations. Approximately 95% of available FSX add-ons are easily compatible with the Steam edition and a few more % of that only needs minor tweaks to be compatible. In addition you won't have to worry about reactivation issues with the boxed edition. If you try uninstalling everything and reinstalling only FSX:SE, and you STILL have issues, then there is another fix that is very likely to work, but it is a quite intensive fix (registry editing) so I would prefer to save that for when all else fails. I don't know how well Revo does in wiping out registry entries.

Hi Paul. No, I indeed have Ultimate Terrain X. I believe you have version 2.3, just like I do. I take it my installer's screen shot differs from yours? This is the one I own. http://www.flight1.com/products.asp?product=utxusa As long as your version says version 2.3, it shouldn't matter. It may be possible we purchased UTX from different vendors so the installation packages look slightly different.

Since I care about this so much, I went ahead and re-installed UTX in my computer. ;-) I think what happened is either: a) when you installed UTX, you accidentally chose Boxed FSX instead of FSX (Steam). or b) You installed UTX for your old boxed FSX BEFORE you purchased and installed FSX:SE. See the screen shot for what you should do if you install UTX after FSX:SE: This is what I suggest you do now: 1) Go to Programs and Files in Windows (you can find it in the white search box). Scroll down to Ultimate Terrain X - USA V2.3. 2) Click on it and select Uninstall. Confirm/OK all subsequent dialogues. 3) Find your UTX installer. It is probably in the folder Flight One Software and the installer's name is UtxUsa23IM.exe. I wouldn't know where you downloaded it. You may need to re-download it if necessary. 4) Right-click on that installer and select Run as Administrator. Confirm everything, and select FSX Steam Edition for both the top and bottom (the bottom is for the optional UTX Lights. Go ahead and install that too if you want). 5) In my Steam install, the UTX folder is located in C:/Steam/steamapps/common/FSX/Flight One Software/UtUsaFx/. In that folder right click on UtSetup.exe and select Run as administrator. 6) HOPEFULLY You will get 3 green check marks!!! If you then see a big red X that says Disabled, go to Terrain-->Quick UTX Enable/Disable to Enable it and get a green check mark instead. You will then be good to go. By the way I tried my Product.INI edit and the fix I suggested works for me. Those two steps I tell you to run as administrator will hopefully force UTX to install correctly. Some Windows systems have too much file protection going on and I'm hoping to avoid having you to change the file protection settings. This is my current suspicion because your Product.INI file has only two lines while the one I have has many lines in it. I have almost no file protection in my FSX setup to make add-on installing and editing easier.

OK that is very good to know. That Product.ini file, open it again. I assume it looks like this: [settings] SceneryComplexityMin=1.0 SceneryComplexityMax=1.36 Under SceneryComplexity Max, copy and paste these two lines: SceneryCfg=Microsoft\FSX-SE\SCENERY.CFG FsxCfg=Microsoft\FSX-SE\FSX.CFG So the final file should look like this: [settings] SceneryComplexityMin=1.0 SceneryComplexityMax=1.36 SceneryCfg=Microsoft\FSX-SE\SCENERY.CFG FsxCfg=Microsoft\FSX-SE\FSX.CFG Save it and try running UTX again. The reason those two lines were not there in the first place is that the default settings have not been changed, so there was no reason for the lines to be written in the .ini files. I don't see anything in the manual about manually changing the paths for the AppData/FSX-SE/ folder, so I am hoping adding those two lines to the .ini file will do the trick.

You mean delete the oldest, right? I hate when those settings files get corrupted and there is usually no way of knowing unless one removes the settings and documents folders for FSX and try running it again to create new folders and files. It probably happened to me only once but I see people posting in forums with such issues regularly.

Before we continue any further, Paul, in the AppData/Roaming/Microsoft folder, do you see both a FSX and a FSX-SE folder, or only a FSX folder? Please confirm.

Hi Paul. I see the new errors as a good thing because it shows that you are making progress. :-) For the 404 error, the web address is incorrect. It should be: www.simforums.com/forums/ That new path you see with an /AppData/ folder is the settings folder that FSX:SE creates when it is run for the first time. FSX.cfg is the file that has all your FSX settings and scenery.cfg is your scenery library. These settings are NOT installed in your normal Steam FSX folder. The reason for that is that you can safely uninstall and reinstall FSX and not lose your settings. Before you blame Steam, it is the same way for boxed FSX. In addition, AppData is normally an invisible folder in Windows. You can make it visible by opening any File Explorer window in Windows 10 and checking the box indicated in the below image by my black arrow. After you have checked that box, I suggest you do next: 1) Run FSX:SE. Say yes and OK to any and all messages that may appear. 2) Start any free flight. It can be the default one with the flying Trike. 3) When you are airborne, quit FSX:SE normally. It may take 30 seconds or so for Steam to fully shut the software down. 4) In Windows go to the C folder, then Users, then paulc, then AppData, then Roaming, then Microsoft. 5) Do you see only one FSX folder, or do you see a FSX folder and also a FSX-SE folder? FSX-SE is created by FSX:SE if Windows already has boxed FSX in its registry. This is done so boxed and Steam FSX do not conflict with each other. Right now we want FSX only and no FSX-SE. IF YOU SEE A FSX FOLDER ONLY Open that folder to verify you have FSX.cfg and scenery.cfg files in that folder (any other files are fine). If you do not see .cfg, in Windows explorer, check the box above the Hidden Items box (File name extensions) to force Windows to show you extensions (like .cfg, .txt, .htm, etc.). If you do see them, then run UTX again and see if you get the error message again. IF YOU SEE A FSX-SE FOLDER ***DO NOT DO THE FOLLOWING STEPS BELOW IF YOU DO NOT SEE A FSX-SE FOLDER!!!!*** I saw this in UTX's forums and I figure this will be the easiest fix: 1) Go to the folder that has UTX USA. I think it will be in C:/Flight One Software/UtxUsaFsx or something like that. Again I do not have that software installed now, so if you see a similar name, please take the initiative to go to that folder. :-) 1a) Alternatively, you could go to the icon you use to launch UTX in Windows. Right-click on it, select More, and then Open File Location to reveal the folder. Or right-click on the alias for UTX. The main point of 1 and 1a is to go to that folder. :-) 2) There should be a file called Product.INI in that folder. Right-click on it and select copy, and then right-click on an empty part of the folder and select paste. It makes a backup file in case anything goes wrong. 3) Right-click on Product.INI and select Open With. I suggest using Notepad but Wordpad works as well. 4) There should be a section that reads something like this: [Product] Region=USA Version=2.3.0 Platform=FSX Product=Ultimate Terrain X - USA [settings] NoWarningCheck=0 Developer=1 DefaultWaterTextures=0 DefaultTextureRes=1024 HaloTexture=0 Path=C:\Steam\Steamapps\Common\FSX Registry=Software\Microsoft\Microsoft Games\Flight Simulator\10.0 SceneryCfg=Microsoft\FSX\SCENERY.CFG FsxCfg=Microsoft\FSX\FSX.CFG TerrainCfg=C:\Steam\Steamapps\Common\FSX Exe=fsx.exe In the SceneryCfg line, change \FSX\ to \FSX-SE\. In the FsxCfg line, change \FSX\ to \FSX-SE\. 5) Save the file and close it. 6) Try running UTX again and report back. I do have another possible fix in mind, but let's say it may be a little intimidating. So I will hold off on that idea until you try the above procedures.

Have you run the SPAD.neXt software? It must be running, prior to starting up FSX. The panels won't work if SPAD is not running. It is recommended to right-click on the software and run as admin (or set it in Windows so it always run as admin). EDIT: one more thing - when SPAD.neXt first runs, click on the icon showing flight panels on the left. For each panel, make sure Virtual Power is turned on (you probably have one, I have three of them). If you do not see your panel, it may need to be plugged into a different USB slot or plugged into a powered USB hub - I get that problem once in a while with my Multi Panel but never with my Switch and Radio panels. Also, if you still struggle, go to Windows Programs & Features and ensure the Logitech drivers are uninstalled. They may conflict. I have SPAD running without Logitech/Saitek drivers.

The "Use Registry" button is only clicked on if the path shown on the top box is correct. If it is not correct, do not click on Use Registry. Instead use the Browse For Folder button to find the correct path (like you just did - C/steam/steamapps/common/FSX) for the bottom box (I think you can actually type on it instead, but am not 100% sure). When done, click on OK. That is what the paragraph under Figure 8-2 means by "override." The OK button will only use what is on the bottom box and not on the top box, thus overriding what is on the top box. You should then hopefully be able to use UTX as you have normally in the past after that. You probably knew that already, but ensure FSX is NOT open and running whenever you are using the UTX Setup Utility. Fingers are crossed for three check marks soon!

Paul, your computer is working. That is not an issue. Your FSX:SE installation is working. That is not an issue. You want to use UTX USA with FSX:SE, which has been confirmed by me, a fellow FSX:SE and UTX user, as being possible. However, you are getting a path not found error. That is your issue. The extra effort I am referring to is following the same solution given to you over several posts and/or looking at the UTX USA manual. You were given a link for the manual, a screen shot with its exact web address, and right now I am telling you that you can even Google and find that manual. The screen shot, taken from the manual, is the exact instruction required to solve your issue: Now it is on you to, yes, put in the extra effort to click on several things in the setup program to tell it where your main Steam/steamapps/common/FSX/ folder is. Computers and their software cannot think for themselves. They rely on correct instructions and file paths. They don't care about how much money you spent on it or how badly you want to see accurate highways and coastlines in FSX:SE. If they give you errors, it is on you to do the work to resolve them. You have asked the correct questions and now you have the instructions on how to resolve that error. Now it's time for some extra effort. UTX is not able to fix its error by itself. If you do not feel you can click on a few things as instructed to resolve it, then no problem at all. FSX is still a great simulator even without the extra perks that UTX brings to it.

I stand by my posts, PCohen. If you looked at the second image in post #122, you will see the full website address for the UTX guide that would certainly help you. You can type each character and hit Enter yourself if it is more comfortable for you. The problem with this message board is that long web site addresses are not displayed in full, so normally you need to click on them and not copy and paste the truncated address. I really enjoyed using UTX with FSX before I switched to Orbx. FSX scenery at maximum settings does not have what UTX has. It's the truth, unfortunately. If you do not feel the extra effort on your part required to make the add-on you paid for work with FSX:SE is worth it, then that is your prerogative.

vul, have you tried downloading the Getting Started guide? First of all you would benefit from downloading/installing FSUIPC version 4 (free demo is good enough). SimConnect is already installed with FSX. Enable both in FSUIPC's Setup Wizard. https://www.spadnext.com/forum/viewtopic.php?f=4&t=226 To be honest I haven't tweaked that software all that much. I just connect my panels, run SPAD.neXt as administrator, and then run FSX. Try a default aircraft in a free flight, powered on, and everything should work. Read the guide and feel free to ask here or in SPAD's forums. The Getting Started guide is quite expansive and my energy would be better spent asking specific questions as they come up as needed. I'm not sure what else budget level panels are available and compatible with both FSX and MSFS. I think a lot of sellers you have heard of only tried Logitech's drivers for FSX, gave up, and aren't aware that a much more powerful version than Logitech's software exists for them. I love my panels and SPAD and the community can try to pry them out of my cold and dead hands.

Correct. For PCohen's issue now, he needs to tell UTX USA where his base FSX:SE installation folder is. UTX doesn't need his AppData or FSX.cfg at this point.

CLICK ON THE LINK. Do not copy and paste it to your web browser. https://static.scenerysolutions.com/Doc/UltimateTerrainXUsaV2.pdf I repeat: CLICK ON THE LINK. Clear now?

I for one like endings with positive notes! I have been following this thread. Well done and enjoy.

Don't copy and paste the URL you see. CLICK ON IT. This forum truncates long URLs and those should not be copied and pasted on your browser. After the .com/ it reads like this: Doc/UltimateTerrainXUsaV2.pdf

Paul, yes, it is Setup-UTX-USA. Do not use the word "installer" in this thread anymore, you are beyond that stage as far as UTX is concerned. ;-) See the instruction manual: https://static.scenerysolutions.com/Doc/UltimateTerrainXUsaV2.pdf Go down to Figure 8-2 (its page number are all 2 so find it by figure number) and it will show you the Change Simulator Location window. Click on Sim and then select Change Sim Location. I don't mind the new MSFS for beginner simmers who just want to enjoy the scenery and group flights. I personally have the Premium Deluxe but I am still waiting for the sim to be more fully developed. For now I am still flying in FSX most of the time.

On top of the other posters' recent comments on your photos, I believe your SPEED button needs to be activated and the A/T ARM needs to be ON. In the diving photo A/T is on but SPEED is not on. I fly with a Saitek Flight Panel so I don't always pay attention to the aircraft's autopilot panel itself. However I am reasonably for the default 737 both need to be engaged so you do not eventually lose speed with the nose up.

Please read post #111, Paul. I am 99% certain it is the solution to your latest issue.

ac10310, I am wondering if you accidentally set the V-Speed (Vertical Speed) too high. It will cause the aircraft to try to nose up and speed up to match your entry . The default 1800 is safest but I believe I have heard that most Boeing usually go at 2500. Rick's suggestion to take a screen shot of your AP panel is a great idea. I fly the default Boeings and Airbus all the time and do not have issues with using the AP shortly after manual takeoffs.

Great point loki. The latest installer is for version 2.3. However, Paul, while I did not re-install UTX (I don't want it to mess up with my new Orbx settings), I remember from your latest post that when UTX is launched, three green boxes show up. That is NOT the installer! That is the UTX Setup Tool! If the setup software says it cannot find FSX:SE, then you must go to its settings and tell it where the FSX:SE path is. It is possible you installed UTX first, then moved your Steam directory out of Program Files x86, and UTX still thinks your FSX:SE folder is in Program Files x86. In the tool click on the top menu bar that says FSX, then select Change FSX Location. If the top address (Registry) is correct, click on Use Registry. If it is wrong, use Browse for FSX to find the correct location for the bottom address and then click on OK when done.

Skywatcher12, what are your system specs? It is relevant to me because I do not get noticeable stutters running FSX:SE with FSUIPC 4.75 on a modern system. Like I have read from others in your FS9 thread, a 1% performance drop is expected and not a game breaker. There is always a cost to performance with each add-on active in the background. I'm sure the more FSUIPC features you disable (such as autosaving every 1 minute) the better the performance will be.

Jorgen is correct, Paul. I just went out of my way to attempt to re-install UTX version 2.3. I got an error message too. What you need to do is to right-click on the installer's EXE (in the Scenery Solutions folder) and select Run as Admin. Don't worry, as long as you trust the program, it is totally safe, and it only needs to be done once. The installer will then better locate the FSX:SE files. Please see the attached screen shots for proof that UTX 2.3 does indeed work with FSX:SE. The second photo won't appear unless you run the installer as Admin.