Page 1 of 1

KA350i Version 1.1.30 Beta

Posted: Mon Jun 22, 2020 3:15 pm
by doodlebug
Hello all!
We have made some fixes and changes. The builds are currently in testing, but if you would like to try them out, we would welcome the additional feedback.

The change log and links are below:

High Resolution - http://milviz.com/Online_products/Produ ... 6_High.exe
Low Resolution - http://milviz.com/Online_products/Produ ... 16_Low.exe

Changes from 1.1.29
FMS Changes
-Added support for second navigation database [navigationdata2.mdb in P3Dv4\Milviz\FMS-3000]
-Added the ability to enter time manually
-Added nearest airport lookup for the POS INIT airport
-Fixed text on POS INIT 2/2
-Fixed GNSS data appearing when GNSS is disabled
-Added GNSS track/speed display
-Added functionality to NPA RAIM page
-Fixed units on GNSS STATUS
-Added POS DIFF to GNSS STATUS
-Added more data to GNSS STATUS 2/2
-Prevented WAAS/EGNOS from appearing when disabled
-Fixed missing DIRECT TO text on FIX INFO page
-Fixed ABEAM REF text
-Fixed PROG data display/dashes
-Fixed SEC FPLN not swapping with MOD ACT FPLN
-Added custom PILOT ROUTE name support
-Fixed PILOT ROUTE not loading into SEC FPLN
-Added overwrite/delete prompt for PILOT ROUTE
-Updated DISK ROUTE page
-Added RUNWAY LENGTH METERS/FEET to DATA BASE page
-Improved TERM WPT display significantly
-Added ability to enter pilot waypoints with true heading
-Fixed reversed order of marked points
-Added along-track offset pilot waypoint support
-Added pilot waypoint retention between sessions
-Added marked point retention between sessions
-Added disabled navaid retention between sessions
-Fixed broken MAG/TRUE toggle
-Added ability to enter shorthand latitude/longitude waypoints
-Added ability to convert a FIX to a waypoint
-Fixed PILOT WPT selection issue
-Fixed naming of implicit pilot waypoints
-Fixed a crash relating to entry leg wind on an empty flight plan

PL21 Changes
-Fixed alignment of FIX label

Systems Changes
-Added new XMLTools installer

Re: KA350i Version 1.1.30 Beta

Posted: Mon Jun 22, 2020 10:55 pm
by j.waeber
Is the EGPWS-Issue i experience also fixed in this one?

Re: KA350i Version 1.1.30 Beta

Posted: Tue Jun 23, 2020 5:22 am
by henrik.bergvin
Indirect light texture for the main panel is missing in the high res version, this was also an issue in .29:
http://www.milviz.com/forum/viewtopic.p ... 330#p99561

Re: KA350i Version 1.1.30 Beta

Posted: Tue Jun 23, 2020 10:14 pm
by lukasz
P3D5 HF2 released.... waiting for KA350 ;-)

Re: KA350i Version 1.1.30 Beta

Posted: Wed Jun 24, 2020 6:44 am
by bmw969
We are waiting very much !!

Re: KA350i Version 1.1.30 Beta

Posted: Wed Jun 24, 2020 10:56 pm
by spickle
Is anyone else unable to see Master Caution, Master Warning, Prop Sync, GND COMM, or gear lights? Am I just being an idiot here or is this a bug?

Re: KA350i Version 1.1.30 Beta

Posted: Sat Jun 27, 2020 1:04 pm
by henrik.bergvin
-Added the ability to enter time manually
Does this mean you can set the current UTC manually? If so, how do you do that?

Re: KA350i Version 1.1.30 Beta

Posted: Sat Jun 27, 2020 1:06 pm
by henrik.bergvin
spickle wrote:
Wed Jun 24, 2020 10:56 pm
Is anyone else unable to see Master Caution, Master Warning, Prop Sync, GND COMM, or gear lights? Am I just being an idiot here or is this a bug?
I see them, but the G/S INHIB, TERR INHIB, STEEP APPR and FLAP OVRD buttons don't show lights when I press them. I suspect this is RealLight causing it..

Re: KA350i Version 1.1.30 Beta

Posted: Sat Jun 27, 2020 4:28 pm
by richbonneau
Note the double text on the FMS button on lower left of the attached file

Re: KA350i Version 1.1.30 Beta

Posted: Mon Jun 29, 2020 12:47 pm
by bmw969
I have no such problem

Re: KA350i Version 1.1.30 Beta

Posted: Mon Jun 29, 2020 4:42 pm
by bmw969
Any official information about P3Dv5 ???

Re: KA350i Version 1.1.30 Beta

Posted: Tue Jun 30, 2020 3:53 am
by t
henrik.bergvin wrote:
Tue Jun 23, 2020 5:22 am
Indirect light texture for the main panel is missing in the high res version, this was also an issue in .29:
http://www.milviz.com/forum/viewtopic.p ... 330#p99561
I didn't see an explicit acknowledgement of this issue, but since it was also present in .29 I want to +1 this.