



If Steam is installed on another drive then look on that drive for "\Steam\steamapps\common\gamename, where gamename=FSX or FSX-SE.Īdvanced users know how to make additional steam game libraries below folders they designated. The above is the most common (default) path to the ROOT of the FSX install if Steam is installed on your C: drive. How can I modify the installer to point it to the correct folder - is that possible? For anyone who has installed Steam on their C: drive and NOT ever had the boxed version of FSX installed, the full path to the correct folder is: I also tried the Steamapps folder to no avail. I don't have the boxed DVD version so I'm assuming from your post that the default folder is C:/.Steam. P.P.S: In case anyone still cares, I've attached a screenshot of my MiniDisplay configuration.Originally posted by mjosephsn:i relocated the installer executable in the Steam folder, ran it again and received the same message. P.S: Now working after reboot, even after re-enabling MiniDisplay. I do my maintenance from a different account, and it is inconvenient to change the path each time. I disabled the MiniDisplay plugin in hopes of at least being able to use MP, but it still hangs at "Starting plugins." (logs attached)īTW, how can I get MP watchdog to *always* zip the logfiles to a public folder. I don't find anything useful in Event Manager, just the hang reports from each time I have killed MP client. deleting both inpout32,dll and hwinterface圆4.sys.This behavior persists after trying both of your suggestions: Site : Void SetLine(Int32, System.String, ) Source : MiniDisplayLibrary Stack Trace: at .ScaleoEV.SetLine(Int32 line, String message, ContentAlignment aAlignment)as I care to let it produce. Exception: System.NullReferenceException: Object reference not set to an instance of an object.Īt .ScaleoEV.SetLine(Int32 line, String message, ContentAlignment aAlignment) Message: Object reference not set to an instance of an object.
