KA350i Version 1.1.35 Beta (V4 + V5)

[didier]

Can you provide me EXACT steps to reproduce this?

A)
A.1 - FPLN from LEAL to LEMD:

• insert these waypoints ASTRO, SOSAV, MOTIL, NANDO and VILLA
• Verify that legs are present ( )...
• DEP/ARR, choose RWY 28 with ASTR4D (AIRAC cycle 2009)
• EXEC
• No leg have been inserted for SID ASTR4D

A.2 FPLN from LEAL to LEMD:

• Verify that no leg is present...
• DEP/ARR, choose RWY 28 with ASTR4D (AIRAC cycle 2009)
• EXEC
• Legs for ASTR4D have been inserted
• DEP/ARR, choose RWY 10 with ASTR4A
• Legs for ASTR4D have been replaced by those for ASTR4A
• insert these waypoints SOSAV, MOTIL, NANDO and VILLA
• DEP/ARR, choose RWY 28 with MAGA2D
• Legs for ASTR4A have been replaced by those for MAGA2D

A.3 Adding some user waypoints I didn't succeed to have P3D crashing... Forget it.
Instead I think there is perhaps some problem with the naming of the second user waypoint:

• Verify that no leg is present...
• Add LEAL280/5 (ie 5 NM on radial 280 from LEAL, right?), you get a new leg to LEAL1
• Add LEAL1010/5, you get LEAL12 (that should probably be LEAL2)...
• Add LEAL12225/15... you get NOT IN DATABASE
• The problem is identical when name of the user waypoint is "PWn" (3 then 34 ... 10 then 1011)

B) Even without taking off, WXR On then OFF, a pair of random "keystrokes" on PFD/MFD makes P3D to crash. Without WXR on/off... I get tired playing with PFD/MFD buttons but P3D seems to resist

Within a couple of minutes I'll try to fly to Madrid (15th attempt )...
Perfect, landed at LEMD ILS Z 18R! No more WXR for me!

C) PUSH STD
Sorry if it has already been reported but pressing (clicking) Baro has not the expected effect (pressure is decreased instead).

[Slayer]

Can you provide me EXACT steps to reproduce this?

A)
A.1 - FPLN from LEAL to LEMD:

• insert these waypoints ASTRO, SOSAV, MOTIL, NANDO and VILLA
• Verify that legs are present ( )...
• DEP/ARR, choose RWY 28 with ASTR4D (AIRAC cycle 2009)
• EXEC
• No leg have been inserted for SID ASTR4D

A.2 FPLN from LEAL to LEMD:

• Verify that no leg is present...
• DEP/ARR, choose RWY 28 with ASTR4D (AIRAC cycle 2009)
• EXEC
• Legs for ASTR4D have been inserted
• DEP/ARR, choose RWY 10 with ASTR4A
• Legs for ASTR4D have been replaced by those for ASTR4A
• insert these waypoints SOSAV, MOTIL, NANDO and VILLA
• DEP/ARR, choose RWY 28 with MAGA2D
• Legs for ASTR4A have been replaced by those for MAGA2D

A.3 Adding some user waypoints I didn't succeed to have P3D crashing... Forget it.
Instead I think there is perhaps some problem with the naming of the second user waypoint:

• Verify that no leg is present...
• Add LEAL280/5 (ie 5 NM on radial 280 from LEAL, right?), you get a new leg to LEAL1
• Add LEAL1010/5, you get LEAL12 (that should probably be LEAL2)...
• Add LEAL12225/15... you get NOT IN DATABASE
• The problem is identical when name of the user waypoint is "PWn" (3 then 34 ... 10 then 1011)

B) Even without taking off, WXR On then OFF, a pair of random "keystrokes" on PFD/MFD makes P3D to crash. Without WXR on/off... I get tired playing with PFD/MFD buttons but P3D seems to resist

Within a couple of minutes I'll try to fly to Madrid (15th attempt )...
Perfect, landed at LEMD ILS Z 18R! No more WXR for me!

C) PUSH STD
Sorry if it has already been reported but pressing (clicking) Baro has not the expected effect (pressure is decreased instead).

Use middle mouse button for pushing in baro STD, same goes for the rotary selector on the map system.

[didier]

Sorry for that but... Without WXR, just "playing" with NAV/BRG SOURCE VOR1 / VOR2, P3D hangs then close:

Faulting application name: Prepar3D.exe, version: 5.0.31.35253, time stamp: 0x5eebf566
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x06701e03
Exception code: 0xc0000374
Fault offset: 0x00000000000fed79
Faulting process id: 0x4238
Faulting application start time: 0x01d67c3f425ce707
Faulting application path: C:\Avionic\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 27597be2-7cc2-4e61-b6e9-3e03c648d632
Faulting package full name:
Faulting package-relative application ID:

I give up and wait until new versions are released for KA350i... and P3D V5...

[Turbofandude]

I was unable to reproduce any of the leg insertion/crash issues you had, however, I was able to recreate and fix the pilot waypoint entry issues.