Consolidated list of issues in 1.5.0

[Dutch Owen]

Captains,

These are the issues reported in 1.5.0 so far. If I have missed something you reported, please remind me and I'll add it to the list. As these reports and verified (reproduced here) and fixed I'll try and keep this list updated.

• Crash to desktop when clicking on "Weather Options" button. [Verified, fixed.]
• On subsequent legs of a multi-leg flight the fuel quantity is always zero. [Verified, fixed.]
• Fuel Quantity is wrong on VA export.
• Intermediate leg selection results in flight data for a previous leg. [Verified.]
• Winds shown on "Winds Aloft" dialog do not match winds from AS data file.
• Gates not being assigned - "TBA" instead. [Hopefully addressed - Trav.]
• Engine flameout from icing even with engine anti-ice on. [Hopefully addressed - Trav.]
• On some installations no music and/or no audio is heard.
• Proceed button INOP after refueling stop. [Verified, fixed.]
• Incorrect identification of sim version (FS9 and not FSX). [Verified and investigating - Trav.]
• Autoload failing under certain circumstances.
• Position reporting option not being updated properly in Admin. [Verified, fixed.]
• Invoking the "why didn't my aircraft get listed" dialog causes a crash on some systems.
• Getting 'Station not set' from Opus on External FCDU with Wx configured correctly.
• Minor formatting errors on the Commitment page.
• Uninstalling the gauge from an aircraft deleted the whole aircraft folder.

[Svilen Vassilev]

For what it's worth, based on personal observations on 10+ flights with version 1.50:

* Fuel Quantity on VA export: no issues noticed, numbers match (both my FSC and VA scripts are configured to use kg). For those experiencing issues: could it be that your VA is expecting lbs and you're sending kilos or the other way around?
* Music / Audio: no major issues. On one flight, the deicing spray sound persisted after the deicing was finished and throughout the entire flight.
* Engine flameouts: no issues noticed when flying in icing conditions with QW146, Aerosoft Twotter, PMDG MD11, PMDG 737NGX (all with xml interfaces).

Observations on the Majestic Dash-8 (with xml interface installed):

All signals and data implemented in the interface are correctly transmitted to FSC.

However:

The fake flameout issue persists (even though anti-icing switched on and recognized by the interface)
Min Gs for each flight are always 1G. Max Gs for each flight are always 10G. The plane jumps from 1 to 10 Gs every few seconds or so, I guess because of the externally controlled FDE. This makes Travis VERY displeased and the stewardess has to apologize to pax after each flight

[Travis]

Svilen,

Can you open the Q400 interface file and check the version? What you've posted makes me think you're using version 0.2.

[Svilen Vassilev]

Hey, Travis!

Oddly, it is v. 0.3 of the interface, I opened the file, and apart from the version number I can clearly see the code that is designed to handle the Gs and engine overrides. In the same section of the xml there's also the landing gear handling (works properly) and vertical speed (works properly). Also all other systems and switches referenced in the XML are working and communicating to FSC normally. It's just the bogus flameout and the G forces that don't get picked up.

But don't bother about it if noone else is reporting, confirming these issues, I'll try a clean reinstall of the Dash when I have a bit more time and will try to wrap my head around the xml logic and tweak it to see if I can get a match. It's an awesome addon but obviously very uncoventional design (heck, one can't even read/write the radio frequencies via FSUIPC or simconnect), and the upcoming PRO version will probably change yet again the way things work and are communicated externally.

P.S. Also sorry for flooding the 1.5.0 thread with those issues, they are certainly not related to the new FSC version and are not part of the FSC core anyway, perhaps you can move the posts to the Dash-8 interface topic if the forum software allows.

[Travis]

Svilen,

I've updated my Q4 to the 1.00801 (Hotfix 1) version.

Prior to that, I've ran the internal interface (non-xml) version and have not had a problem.

(That is, unless I'm running my new 1.008 LUA meta-interface code. Ahem)

I will be revising that interface and should anyone reply to my "Hello?" post in the Developer's forum, I would be happy to post more goodness there.   Ahem.

Sorry for all the "Ahem-ness."

[okupton]

Here's a new one. Not sure how this happened, but I updated FScaptain from the 1.5.0 Beta to the full 1.5.0 version, and now the FCDU within the sim is telling me that it's the FS9 version, when Im running FSX. Externally, if I run the FCDU.exe file in the fscaptain folder, it is showing as the FSX version. Reinstalled version 1.5.0 complete install instead of the fixpack like I did before, and the problem continues.

[awralls]

Dutch, any feel for the ETA for 1.5.1? The issue over 0 fuel and eta for subsequent legs is hurting my airline at present. No hassle, it would just be useful to have an idea.

Thanks

Andy

[Svilen Vassilev]

Dec 27, 2013 14:27:29 GMT -5 Travis said:

Svilen,

I've updated my Q4 to the 1.00801 (Hotfix 1) version.

Prior to that, I've ran the internal interface (non-xml) version and have not had a problem.

(That is, unless I'm running my new 1.008 LUA meta-interface code. Ahem)

I will be revising that interface and should anyone reply to my "Hello?" post in the Developer's forum, I would be happy to post more goodness there.   Ahem.

Sorry for all the "Ahem-ness."

Thanks for the tips, Travis!

[Travis]

Andy,

I'm not expecting an update before the 1st of the year. Dutch put in a lot of weeks working on the 1.5.0 version and with us taking some "family time" for the past week, I really hope he's taking it easy for a few more days.

[awralls]

Quite understand; thanks for the update.

Andy

[jenstt]

Is it normal that in P3D v2 I keep getting a message that the dll can't be accessed and if I've installed fscaptain? I also have a feeling that al my airline and music adjustments in the administrator aren't 'seen' in P3D (no music, assigned parking,louder volume even though it's set in the fs administrator).

On a sidenote, icing and runway conditions are based upon the outside FS reported temperature? Because as you may or may not know P3D v2 has some issues for the moment causing to set a reaaaally high outside temperature in the sim when being controlled by fsrealwx. I suppose that's why I almost never get icing.

[Dutch Owen]

It looks like your FSCaptain.dll isn't getting loaded into P3D (this is why the music doesn't play, etc) Please post us the contents of the DLL.XML file in your [ApplicationDataFolder]\Lockheed Martin\Prepar3d V2 folder.

Dutch

[jenstt]

Dec 29, 2013 14:38:51 GMT -5 Dutch Owen said:

It looks like your FSCaptain.dll isn't getting loaded into P3D (this is why the music doesn't play, etc) Please post us the contents of the DLL.XML file in your [ApplicationDataFolder]\Lockheed Martin\Prepar3d V2 folder.

Dutch

Now it plays but not sure about the volumes and still no gate assigned (I think, always says that I should park somewhere on the ramp, no matter where).Could you please clarify the icing issue too?

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>Addon Manager</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>bglmanx.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSCaptain</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>FSCaptain\bin\FSCaptain.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

</SimBase.Document>

[Travis]

Jenstt,

What are you using for your P3D weather source? If you are using an external engine (other than Opus) then there is a bug within P3D 2.0 which is somehow generating very high temperatures to which that FSCaptain must abide.

[jenstt]

I'm using fsrealwx but when on the ground at my home airport (EBBR or EBCI) I get the correct clouds and winds but my aircraft indicates an OAT of 72 celcius which isn't correct at all as the temps are around 5 degrees here.. But when I look in fsrealw I see correct values indicated in the METAR (and thus also in Fscaptain). Only problem are the temps in the simulator which, I think, are causing me not to have any icing effects ever at all..