gaab

Just a clue I found that the installer creates an entry in the Program Data\Lockheed Martin\Prepar3D v4 : so, as I had already an entry in Roaming, I got duplicate entries for XmlTools and Prepar3D was not happy... Gérard

Hello, I am ready to follow your advice, but my autogen draw distance is already set to "medium" 😞 Any other parameter I should look at to get rid of this very disturbing phenomenon ? Thanks - Gérard

You must have the lattest WX Advantage Update 8 if you are running P3DV4.5 HF2; see here

I decided some month ago to "black list". I just got the PC12 because there were mods proposed by the community. Thanks for that 🙂 (My fixes have been sent to them).

As written in my first post, I did and I got the usual non-answer... For your information, I fixed all there typos and other error messages. I also fixed an event flooding ! As an example of why I say it is a matter of behavior, you can check by yourself that when they convert a 2D gauge for display in the VC, they just change the "image_filename" to "image_filenameNOP", creating of course a gauge image not found error, when it would be so easy to just comment the image block ! It is just a shame... Gérard

Why some (small or large) developpers provide error free products (even complex one), when other have hundred errors listed. Tools may help, but will never fix errors in place of programmers. This is why there is Quality Insurance fonctions and "behavior".

I really dont see why the behaviour of some developpers would change just because there is a new simulator out.

For your information, coming from a respected member of FsDeveloper and beta tester for several companies WarpD 6 May 2019 According to L-M... each of those errors impacts performance of the sim In the same thread : Notice that any invalid text included in a script will be parsed on every cycle, and then performance will be affected, even loss being insignificant. That' the reason why, as a USER, I take the time to fix "errorcontent" message (more than the 999 errors reported by P3D with the original gauges).

As Carenado insist of uninstalling the aircraft, re-downloading and re-installing, could you be kind enough to confirm that you don't have as well the right version of this gauge. I suspect that it is useless and will be satisfied by just commenting out the gauge call in the panel... Regard Gérard.

Why so withering ? Your status and reputation is not in line with your reaction (BTW I thank you for your updated FDE for this interesting plane) 😞 I expect Carenado to supply the right version of the gauge, like for all other .dll gauge coming with this plane. Or specify that it is useless and must be "commented" in the panel.cfg (which I already did). And concerning the P3D error log, I am using it regularly to fix the numerous typos in the Carenado XML gauge (they are not the only developper having these issues, but they have the record of error messages). You are right, as specified by LM, developper should use the error log, but obviously Carenado don't dare to. Regards Gérard

I recently bought the PC12 and discovered that the "PC12_Cabin_alt" is the FSX version 32b. I am runing Prepar3DV4 which complains : [error.280] error=C-style gauge failed to load: G:\Prepar3D v4\SimObjects\Airplanes\Carenado PC12\panel\PC12_Cabin_alt.dll, Gauge: C340_PRESS. DLL is 32 bit. A 64 bit version is required. I have open a ticket at Carenado support site, but the answer is as usual... and after insisting... Does other Prepar3d user have the same issue and in that case, would open a ticket ... Thanks Gérard

Why run a driver if you want it to do nothing ! Just disable the Alpha Yoke Add On in P3D ! Gérard

What "button" do you specify and where ? Take care that the switch numbering by Honewcomb documentation is not the same as viewed by FSX. For example, if you want to program the switch named Strobe on the yoke, - with the (lattest 1.0.3 ) version of YokeInput you will assign >K:STROBES_ON on button 29 and >K:STROBES_OFFon button 30 If you want to do it with FSX, you will assign twice button 29 with "Strobe lights (on/off)", once for "keypress" and once for "key release" - take care that key position can be desynchronised between the yoke and the VC switch ! Gérard

Should not this topic migrate in the MSxxxx forum 👿

Same, so no vote as it is not included in the choices Very happy with it. Gérard

On REX discord channel, last Thrursday. Just wait just a few days more... Gérard

It is exactly why stream are build for. Too bad it does not work as intended on Avsim (it works well on other sites using the same software...) Gérard

There is a pdf file (german and english) created by the installation program - look in the installation folder. Last version on https://flyhoneycomb.com/drivers/

With included an english version of the "user's guide" (at the and of the still named "manual_de" pdf.) Gérard

On discord, October 8th October 21th So.... I will wait 😉 Gérard

Try the "reload aircraft" command - you will have to assign it to a key in P3D options. Works 90% of the time on my configuration... Gérard

I recently made the move (clean install). Take a look at O&O ShutUp10 to setup more easily all the parameters of W10 (no tweak - only a clear and clever display of all the official parameters) I use also Open-Shell to get back a Start Menu I understand 😊 Gérard.

Rex EF entry is created in the dll.xml when the EF program is launched (reason why you MUST launch it before P3D) and removed when it exits (this is the solution selected by REX to solve the mini-UI error message when running P3D without EF). So this is not an issue, but the normal behavior. Gérard

Hello, I ckecked the other way around with and without the Airport Elevation stub at the highest area number (according to P3D own scenery list). I have : at level 515 - elevation 10ft - airport elevation stub at level 460 - elevation 0ft - region elevation stub at level 348 - elevation 846ft - 1105 Base at level 257 - elevation 0ft - region NZMF at level 190 - elevation 10ft - airport NZMF I made a test with and without (.off) the airport elevation stub with NO impact on display... I confirmed with disabling also level 460 (according old rules the airport should have been rised to 846 ft (not few feets as before)... The three views are exactly the same (and alt-Z shows the SAME altitude). As mentionned by Jabloomf, a few minutes ago, this could bring a huge performance improvement especially with sceneries using add-on.xml entries, but can also bring a mess with mesh inteferences (AEC or equivallent would have to be at the top of the scenery ?). Maybe this could justify a tool to directly patch the airport altitude with the mesh information or to go a step further, P3D would take the altitude directly for the mesh (not sure, but is it not the way XP is working ?...) Interesting ....