KA350i Version 1.1.36 Beta (V4 + V5)

[alex.fluglotse]

Hey,

thx for your help, unfortunately I tried that already. I'm still receiving the Error about the XML Tools, trying to installing the king.

[alex.fluglotse]

I tried out a the old 1.1.34 Version, unfortunately the problem persists. Is there a way to download and install the xmltools for P3DV5 manually? I only found the V4 version.

[alessandro.devoto.fly]

Top pic latest update, bottom earlier version with nice and bright screens. Also confirming weather radar immediately causes ctd.

[alessandro.devoto.fly]

And now it's almost not usable from how dark it is.

[andreasmb]

Hello,

I installed this Beta just now today with all options ticked during install process. Also during install process there were downloads of latest beta versions of reallight and trueglass.

In MVAMS selected current conditions under options, left the rest as is, saved defaults.

Started P3DV5 with my standard plane fully up and engines running, ready to start, incl all position lamps etc.
Then selected KA350i and loaded it, and all was good, i.e. engines running etc etc, outer looks smashing, the bird was well flyable, all good, except that all avionics inside are looking as per enclosed, i.e. not correct.

I then exchanged the truelight.dll offered as download here, to see if that changes avionics look, but no, it stays the same.

Any Idea what I can do, except wait for the final V5 product?

Thanks,

[ccmh15]

So, after a few weeks "off-sim" I'm finally back and I just installed version 1.1.36 from the link in the first post into P3D v5.

TL;DR:
Unusable, CTD when the weather radar is activated!

Long story:
Basically, it works really well - until the WXR is activated, then the sim is crashing to desktop every time, without any error message. Windows event log lists "api.dll" as responsible module (that's a new one for me)

I tried to install the "New WX supporting P3D v5" from here http://www.milviz.com/forum/viewtopic.php?f=105&t=12439

The installer available in this thread doesn't change anything in the King Air folders. When unpacked using 7zip, it can be seen that it contains installation target folders for quite a few MilViz products, but not the King Air.

The DLL that's included in this "new WX" installer, is called "MV_WX.dll":
Product Version 1.40.45 from 19 AUG 2002, file size 3.58 MB.

The relevant DLL that is found in the King Air's "panel" folder, is called "MV_WXM.dll" (note the difference in the file name!)
Product Version 1.44.1 from 21 APR 2020, file size 3.04 MB

So - the WXR DLL distributed with the King Air version 1.1.36 has a higher version number, but is four months older.

Replacing the DLL in the King Air panel folder with the one found in the "new WX" installer, doesn't work (sim crashes upon aircraft load)

Summary: to me, version 1.1.36 is unusable.
Whenever the WXR is activated, the sim crashes. In the version I used before, the WXR just didn't show anything, but at least the sim didn't crash...

Anyways, something positive at the end - a big THANKS for the huge improvements made in the CHART area, love the new features!
Just the info text line (with ground speed and outside temperature) is still unusable when a chart is displayed... if you fix that as well, I will finally shut up about this topic..

Cheers,
Chris

[Slayer]

That WXR is for other aircraft such as the Otter and Beaver so it has no effect on the KA. The KA uses a custom version of that...similar but not the same. There are 3 versions of the WXR out there, the stand alone that can be installed to any aircraft as a 2d gauge, the locked versions that are included with products like the Beaver and Otter and can only be used on the aircraft purchased, and the version for the KA. All have different version numbers or dif. file sizes etc. I'll ask Collin to take a look but to my knowledge the WXR is the same as was included in previous betas.

[Turbofandude]

Hey there,

after some research i found out, that the XMLTools are not installed properly. Once i try installing them there comes the following error up:

[ERROR] Prepar3D v5 installation failed: System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at XMLToolsInstaller.MainWindow.InstallTo(SimulatorVersion version, String path)

Not sure what's the reason for that.

Greetings

Alex

This sounds like your dll.xml is invalid/improperly written. Can you post it here?

[ccmh15]

That WXR is for other aircraft such as the Otter and Beaver so it has no effect on the KA. The KA uses a custom version of that...similar but not the same. There are 3 versions of the WXR out there, the stand alone that can be installed to any aircraft as a 2d gauge, the locked versions that are included with products like the Beaver and Otter and can only be used on the aircraft purchased, and the version for the KA. All have different version numbers or dif. file sizes etc. I'll ask Collin to take a look but to my knowledge the WXR is the same as was included in previous betas.

Thank you for the response. It's a bit misleading, that the pinned announcement "New WX supporting P3D v5" is visible directly in the K.A.350 Support Forum, although it's not applicable.

And yes, I compared the DLL to the ones in my backups - it appears to be the same. However, the problem with CTD appeared only after installing 1.1.36, before that, the WXR just didn't show any echos.

Cheers,
Chris

[andreasmb]

Further to my message three further up from this one like to additionally report:

As mentioned above with 1.1.36 Beta in my V5 the glass of the instruments on the panel is very milky and the avionics behind shimmering very faintly through but unreadable. See 1st picture below.

I installed the full package, highres, all modules incl trueglass and reallight. My setting in p3dv5 are as per further pictures, simulator runs smooth, with KA350 6,2 GB at the max, steady 30 FPS all over as set by me via NCP outside the sim.

When I set HDR off in P3D then the two big panels in front of the pilot show well and okay. but the others (copilot aswell as behind throttles and left from pilot remain milky. Thats stunning for me. see last picture.

The glass of the center above avionics aside the voltmeter bus select knob are fine by the way, wether HDR is of or HDR is on.

[Turbofandude]

I believe the "milky" displays is either a bad install or a shader issue. I do not have that here, though they are quite dark with HDR off.

[andreasmb]

Hello Collin,

can you confirm that the Gauges under [VC2] section in the panel.cfg which was installed by 1.1.36 Beta into my V5 as per end of this message inserted sections ( tried to enclose the panel.cfg as a file, but could not) are those gauges which remain milky in my cockpit?

Those milky ones in my cockpit right now °are
the co-pilots right PFD,
the behind the thottle lever 3 round avionics,
the chronometer on pilots control stick
the chronometer on co-pilots control stick
and the two engine fuel gauges left side of the pilots seat

BTW: Raul from FSreborn asked me to give best regards.

Collin, thanks for your check and advise and best regards

quote extract from panel.cfg
[Vcockpit01]
Background_color = 0,0,0
size_mm = 2048,2048
visible = 1
pixel_size = 2048,2048
texture = $B350i_VC1
gauge00 = KingAir350i64!KingAirSystems, 0,0,1,1
gauge01 = MV3DSound!MV3DS, 0,0,1,1,SimObjects\\Airplanes\\MV_King_Air_350i\\sound\\B350i#190
gauge02 = ProLine21!pfd_left, 0,2,1022,1254,lpfd
gauge03 = ProLine21!mfd, 1024,2,1022,1254,mfd
gauge04 = B350i!CCP_PopupControl, 1590,1042,390,204
gauge05 = AMSInterop!AMSInterop,0,0,1,1
gauge06 = RealLight!Core,0,0,1,1
gauge07 = TrueGlass!Core,0,0,1,1
gauge08 = RTU!rtu,1026,1268,774,776,rtu
gauge09 = Proline21!driver,0,0,1,1
gauge10 = ESIS!esis,80,1270,768,772,esis

texture00 = lpfd,0,2,1022,1254
texture01 = mfd,1024,2,1022,1254
texture02 = esis,80,1270,768,772
texture03 = rtu,1026,1268,774,776

[Vcockpit02]
Background_color = 0,0,0
size_mm = 2048,2048
visible = 1
pixel_size = 2048,2048
texture = $B350i_VC2

gauge00 = B350i!Clock2, 1136,1304,608,260
gauge01 = B350i!Clock, 74,1316,608,260
gauge02 = Proline21!pfd_right,0,2,1022,1254,rpfd
gauge03 = FMS-3000!fms,1164,102,744,582,fms
gauge04 = B350i!FreeTemp, 0,1682,626,220
gauge05 = B350i!Registration, 885,1650,996,368
gauge06 = B350i!CabinMonitors, 1150,746,752,432

texture00 = rpfd,0,2,1022,1254
texture01 = fms,1164,102,744,582
unquote - end of extract

[Turbofandude]

It does indeed seem like the VCockpit2 entry that's "milky", as you put it. That's VERY strange indeed. Has it always been that way or did something change/cause it?

[Slayer]

I suspect he's running out of VRAM. Have you tried lowering your textures and or AA yet?

[andreasmb]

Yes, it continues to be same status with any reduced AA setting as well as low textures like 1024.

New observation:
when I change the texture setting to whatever the new changed to texture setting becomes (1024, 2048 or 4096) then after having selected it and when hitting ok to initiate the new texture setting then all textures outside and in the cockpit built ip for about 2-3 seconds and the cockpit shows for the built up time of those new setting for some seconds (maybe 1-2 seconds ) all avionics Clear, but at the end as last step texture built up the VC2 ones then get their milky glass in front.

Also tried with reallightnand or trueglass disbled. all the same, producing this result o partly milky.

I run the Aerosoft CRJ new airplane for V5 incl trueglass, and no problem there.

I never ever had or have no OOMs whatsoever, or CTD, running with the KA350i 6.2 gB out of 10.4 ( windows 2004 version). I sent you my settings, which I believe are quite high, same as the hardware is highest end, mobo for that matter being msi z490 ACE, also not the low end one.


The fact that the VC1 avionics show fine should make it possible somehow for you and me to solve this, I hope.

Appreciate your help and your further guidance, as like this this smashing great product is really a sorrow appearance.

Do you recommend me to de-install 1.1.36 now and try 1.1.37?

I really very much appreciate your help, same as I need it much.