|
Post by Travis on Feb 21, 2023 17:53:27 GMT -5
David,
I've resent the email, plus I've copied the text into a PM here.
Please respond in mail though... this (free) forum isn't the best place to post lots of images, etc.
Best,
|
|
|
Post by davicho61 on Feb 22, 2023 6:01:24 GMT -5
No mail, but I send you an email. Thanks!
|
|
|
Post by Travis on Feb 27, 2023 18:36:22 GMT -5
I have your email, but you didn't get mine.
I'll be back in the forum after my dinner and PM you with my response.
Best,
|
|
|
Post by davicho61 on Mar 13, 2023 14:00:52 GMT -5
Hello Travis, only to tell you that I just installed the simMarket version and right now works FSC1.8.2
|
|
|
Post by Travis on Mar 21, 2023 21:43:15 GMT -5
That's great! You now have a clean platform with which to begin working. When we have something for you to try, all I'll ask is that you make a clean "copy-and-paste" backup of your current \FSCaptain\ folder. Doing that would give you an easy way to restore what you currently have.... We've started what I hope is "final testing" of 1.8.4 Alpha, and when we're confident that normal flight operations have not been affected with unintentional bugs, we'll prepare a public release. We should be ready by mid-April. Thinking about the recent FS9 problems that you and one other Captain have seen, I've come up with three scenarios to explain them:
- A recent public-facing FS9 build included SC-32 or SC-64 gauges. Oops. The upcoming 1.8.4 Alpha release would correct this.
- Last year's switch to building with Visual Studio 2019 introduced an incompatibility with FS9. Ouch! I'd have to resurrect my old coding PC with VS 2017 and build the FS9 versions with it.
- Last year's switch to building with Visual Studio 2019 meant some Captains may not have updated what used to be known as their Visual C++ Libraries. This is not very likely as the Administrator shouldn't even run... but it would be an easy correction to make.
Thanks for your patience!!
Best,
|
|
|
Post by Gabbiano on Sept 24, 2023 4:03:00 GMT -5
Hello everyone! I also encountered the same problem since I recently reinstalled FS9 and FSC. I noticed that when I opened FS9, after a while the windows to select the flight simulator in use also opened and this caused the crash.
I solved it by repeatedly pressing the reject button (also on FS9) and the simulator opened. Pio I also restarted Admin.exe and re-scanned the airports, but without Make RWY and the problem was resolved.
I'm currently arguing with the error list as it gives me the error "Returned -90 when called" (I will open a ticket when I don't find the solution)
|
|
|
Post by Travis on Oct 4, 2023 23:07:27 GMT -5
Hello Gabbiano,
I'm sorry to say that we have lost our last FS9 tester, so we are at a loss to provide our normal assistance.
From reading your post, you mention that after opening FS9, "the windows to select the flight simulator in use also opened and this caused the crash."
I am very unsure, as I do not know why you would see a 'window to select the flight simulator in use' from your simulator.
Several versions ago, FSCaptain abandoned the ability to call the Administrator from within any simulator.
And the only space in our FS9 code which would ask to 'select the flight simulator in use' is in our Administrator.
Our FCDU.EXE could ask this question, but it is not used for FS9,
So I would need you to please try again and email me a new explanation of what happens, and I would need your ADMIN, FSCAPTAIN and FCDU logs from your new attempt.
Best,
|
|
|
Post by Gabbiano on Oct 8, 2023 3:27:33 GMT -5
I fiddled around a bit with the simulator and installers to solve some problems. I solved the 'window to select the flight simulator in use' by uninstalling all of FSC (including the folder) and reinstalling version 1.8.3. Instead I solved the "Returned -90 when called" problem by replacing "SceneryScanner.exe" taken from version 1.8.2
|
|
|
Post by Travis on Oct 8, 2023 16:29:36 GMT -5
Instead I solved the "Returned -90 when called" problem by replacing "SceneryScanner.exe" taken from version 1.8.2 That's not a great solution - the 1.8.3 SceneryScanner has some fixes of other earlier issues, and it introduces a new set of features. My guess is the "-90" that you reported could be due to a scenery-specific issue. But without SceneryScanner logs and your runways.txt file I can't say. But if you have no complaints for the moment, let's look forward. Version 1.8.4 Alpha has a newer SceneryScanner with at least one fix for a "-90" issue arising from FS9 scenery being used in FSX. So perhaps this will fix your problem... or point me to a future fix? I hope to publish this Alpha Release by next weekend. "Final Testing" is going slowly, but steadily. Best regards,
|
|
|
Post by davicho61 on Oct 9, 2023 11:30:09 GMT -5
Hello Travis, Until now no more crashes with 1.8.2 and looking forward for 1.8.4
|
|