|
Post by Travis on Nov 6, 2014 11:11:42 GMT -5
Ian,
You'll get that Overspeed penalty in the Q400 until I can get Beta 4 out the door.
Check your Company Flight Log in the Admin and see if that flight actually scored a penalty or did it just write that to the FCDU log. I'm guessing the latter, as my "write it to the log file" warnings didn't consider the various "disable" switches. But the scoring routine does factor that in.
In any event, Beta 4 won't be handing out erroneous penalty warnings in the log files.
And as for fixing the inappropriate penalties, that will have to come after 1.5.1 is official, and I'll modify your Company Flight Log personally. (And for any other Q400 Captain as well.)
|
|
|
Post by Travis on Nov 6, 2014 11:14:44 GMT -5
FCDU.GAU:: 12:20:32 ERROR: Unimplemented Avar: (A:AMBIENT TEMPERATURE,celsius) I'll need Dutch's guidance on properly eliminating this (it takes handing of a complicated stack of values inside the SimConnect interface and while I think I know what to do, I have to have him vet my changes). So for Beta 4 I'm testing the efficacy of using TOTAL AIR TEMPERATURE instead.
|
|
|
Post by mjl1966 on Nov 10, 2014 19:42:10 GMT -5
1. Dispatch a flight. 2. Open FSX. 3. Start ACARS, start normal load. 4. "Main exit opening" message appears in banner. 5. FSX crashes.
Duplicated three times in a row, the first, second and third times starting a normal load with the new patch. (This failed "out of the box.")
---------------edit--------------------
But wait, there's more.
It turns out that the "Cancel" button on the Load Maps tab doesn't. I took an existing loadmap and started adding precise settings (type, units, value) and then changed my mind and hit cancel. BUT the changes were actually saved. So, now, of course, the values set for the stations exceed the limit of "0" which is set automatically for a "non precise" map. I'm betting that's probably the cause of the crash once this is loaded up in the ACARS.
Short version: cancel actually saved invalid load map without error which then caused crash.
--------------------edit (again)----------------------
OK, confirmed that my suggested cause is all wet. Even with correct load map, FSX crashes when I select "Normal load" on the ACARS. The doors open and it crashes. So, pretty much dead in the water here.
|
|
|
Post by Lucas on Nov 12, 2014 5:22:36 GMT -5
Aah, one more thing my friends. This is minor issue however... In JS41 (only), ACARS, at Specify PAX page, payload and amount of PAX are correct (as in Dispatch set). But after press EXEC (on incoming Flight page), there is only 2 PAX (payload stays correct). Of course I can revise it, however I decided to report it... With regards, Lucas
|
|
|
Post by peter on Nov 12, 2014 5:35:37 GMT -5
4. "Main exit opening" message appears in banner. 5. FSX crashes. Have you installed the uiautomationcore fix ?
|
|
|
Post by Travis on Nov 12, 2014 12:51:31 GMT -5
5. FSX crashes. Duplicated three times in a row, the first, second and third times starting a normal load with the new patch. (This failed "out of the box.") MJ, This sound like something the enhanced logging in Beta 4 might be able to capture. If you wouldn't mind, backup your current FSCaptain & Gauges folders, and install Beta 4, then email us the FCDU & Admin logs from the crash. Time for my typical questions: - When did this behavior start? When were you last able to load an aircraft?
- Has this occurred on more than one aircraft?
- Have you installed FSX again recently?
Noted for further study... "Cancel" should indeed not write anything.
|
|
|
Post by Travis on Nov 12, 2014 12:54:09 GMT -5
In JS41 (only), ACARS, at Specify PAX page, payload and amount of PAX are correct (as in Dispatch set). But after press EXEC (on incoming Flight page), there is only 2 PAX (payload stays correct). Of course I can revise it, however I decided to report it... Thanks for the report Lucas! I have your files still, so perhaps this weekend I will try to replicate this with my sadly-underused JS41.
|
|
|
Post by mjl1966 on Nov 12, 2014 18:43:41 GMT -5
5. FSX crashes. Duplicated three times in a row, the first, second and third times starting a normal load with the new patch. (This failed "out of the box.") MJ, This sound like something the enhanced logging in Beta 4 might be able to capture. If you wouldn't mind, backup your current FSCaptain & Gauges folders, and install Beta 4, then email us the FCDU & Admin logs from the crash. Time for my typical questions: - When did this behavior start? When were you last able to load an aircraft?
- Has this occurred on more than one aircraft?
- Have you installed FSX again recently?
Noted for further study... "Cancel" should indeed not write anything. Yeah, this was all with RC 3. I'll try RC 4 and see what I can break there. Answers to questions: When did this behavior start? When were you last able to load an aircraft? This started when I started normal load with ACARS the first time. I have yet to successfully load an aircraft with this version. I have successfully loaded aircraft with earlier versions. Has this occurred on more than one aircraft? Yes. CS 737-200 and iFly 738 Have you installed FSX again recently? No.
|
|
|
Post by mjl1966 on Nov 12, 2014 19:30:57 GMT -5
4. "Main exit opening" message appears in banner. 5. FSX crashes. Have you installed the uiautomationcore fix ? I have that installed already, but it was a good thought.
|
|
|
Post by Travis on Nov 12, 2014 19:37:01 GMT -5
This started when I started normal load with ACARS the first time. I have yet to successfully load an aircraft with this version. I have successfully loaded aircraft with earlier versions. So you had no problems in this area while using 1.5.0... and the problems began with 1.5.1.
Oh dear, this is looking like a showstopper....
Yes. CS 737-200 and iFly 738 Could you try a default aircraft and see how it works there? And for a follow-up, do you use the Gauge or the EXE? When you've crashed more things, please ZIP and email us your entire \FSCaptain\Data\Logs\ folder so we can start to crunch data....
|
|
|
Post by mjl1966 on Nov 12, 2014 20:11:00 GMT -5
This started when I started normal load with ACARS the first time. I have yet to successfully load an aircraft with this version. I have successfully loaded aircraft with earlier versions. So you had no problems in this area while using 1.5.0... and the problems began with 1.5.1.
Oh dear, this is looking like a showstopper....
Yes. CS 737-200 and iFly 738 Could you try a default aircraft and see how it works there? And for a follow-up, do you use the Gauge or the EXE? When you've crashed more things, please ZIP and email us your entire \FSCaptain\Data\Logs\ folder so we can start to crunch data.... OK, I found the problem. Gaugesound.dll was missing. I backed up my stuff, installed an older version, then merged my current version back in. Dutch is now talking about signs and seatbelts and Heidi is greeting customers. No more crash. Two suggestions: 1. Ideally, the prog should do a manifest on its file structure to make sure the stuff it needs is there. If it isn't, it can then exit graciously and explain itself. ("Hey, why did you delete the sound dll file? Seriously?) Or something like that. 2. If that isn't practical, the fixpacks should definitely be doing a check on required files during install. (Maybe even make each fix pack a complete install.) If the fix pack can't find all its files intact, then it can exit graciously and explain itself. ("You broke the files man. I'm not going to play. Bye.") Or something like that.
|
|
|
Post by mjl1966 on Nov 12, 2014 20:47:15 GMT -5
Noted for further study... "Cancel" should indeed not write anything. What's happening here is a desync of the UI and the database. If you enter data into any of the fields, select another tab (take off focus) and then come back (put focus back on), the changes are still there even if they haven't been committed. I have a lot of long of long-winded opinions about how the administrator UI handles data transactions. If you want to hear them, let me know. (I used to write front ends for relational database applications.)
|
|
|
Post by Travis on Nov 12, 2014 23:29:17 GMT -5
OK, I found the problem. Gaugesound.dll was missing. I backed up my stuff, installed an older version, then merged my current version back in. Dutch is now talking about signs and seatbelts and Heidi is greeting customers. No more crash. Two suggestions: 1. Ideally, the prog should do a manifest on its file structure to make sure the stuff it needs is there. If it isn't, it can then exit graciously and explain itself. ("Hey, why did you delete the sound dll file? Seriously?) Or something like that. 2. If that isn't practical, the fixpacks should definitely be doing a check on required files during install. (Maybe even make each fix pack a complete install.) If the fix pack can't find all its files intact, then it can exit graciously and explain itself. ("You broke the files man. I'm not going to play. Bye.") Or something like that. Cool Cool Cool. I've sent the paramedics home, telling them that I didn't need their dadgum defib - thanks. Future Fixpacks will include all DLL/EXE/Important files. Far future Fixpacks may be more intelligent.... Since the Gauge & Admin both run within the simulator - and I am on a mission to reduce the footprint of the in-simulator code - we will have to wait until the 2.0 Administrator to check for all necessary files and screech loudly if not found. (The 2.0 Administrator will be a standalone application to handle cfg file editing & interface to Dispatch. It will not look like a Windows 2000-era application....)
|
|
|
Post by Lucas on Nov 13, 2014 5:55:58 GMT -5
Travis, if you have in mind the last files which I sent you a few days ago via e-mail, hmm, these files are realted with PMDG777
|
|
|
Post by Travis on Nov 13, 2014 12:47:58 GMT -5
Travis, if you have in mind the last files which I sent you a few days ago via e-mail, hmm, these files are realted with PMDG777 You also sent me your \FSCaptain\Aircraft\ folder which has all your config & load map files. Btw, on the 777 issue, you need to return the B77L.cfg file to your \FSCaptain\Aircraft\ folder. I'm attaching my copy, if you do not have yours. B77L.cfg (1.19 KB) Now about the JS41, I have to step away for the remainder of my day, but this evening I will schedule a PAX flight using your configs & load maps and I will report what I see. [minutes later] I've scheduled a PAX flight that should give me 29 souls on board. Very late in my evening I will report on how many of them showed up.
|
|