Hi Guys

Ive encountered this on initial install and reinstall, each time i try to type in the ICAO airport code into the gps it appears to be doubling up on the letters for example if I try and type in YPDN i get YYPPD

This happens with both the 400 and 430, however  If I use the dial and do it the slow way there is no problem

anyone else experiencing this?

Hi Matt,

This is unfortunately a result of having the GPS display in both the VC and the 2D popup, and keeping them in sync. We're looking into a way to remedy this.

1 hour ago, henningvr said:

Hi Matt,

This is unfortunately a result of having the GPS display in both the VC and the 2D popup, and keeping them in sync. We're looking into a way to remedy this.

Not sure if this is related in any way but I had a CTD when zooming in on the 2D 340 unit. If it happens again I'll send a ticket. I'll try later and replicate the error and let you know. Hopefully it's just a one time event.

This is the windows event report:

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: symmap.dll, version: 4.0.28.21686, time stamp: 0x594a71d6
Exception code: 0xc0000005
Fault offset: 0x0000000000007bbd
Faulting process id: 0x1b0c
Faulting application start time: 0x01d302bce3678c8f
Faulting application path: D:\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Prepar3D v4\symmap.dll
Report Id: 798aea1c-1b18-4b6a-9f7f-1f7f215ca7dd
Faulting package full name:
Faulting package-relative application ID:

9 hours ago, henningvr said:

Hi Matt,

This is unfortunately a result of having the GPS display in both the VC and the 2D popup, and keeping them in sync. We're looking into a way to remedy this.

Thanks for the reply

 

I have worked around this by opening the 2D to get the cursor up and then I will deselect the 2D, type whatever I am wanting to type, and then reselect the 2D and it is perfect.  

On ‎2017‎-‎07‎-‎22 at 10:58 AM, bills511 said:

Not sure if this is related in any way but I had a CTD when zooming in on the 2D 340 unit. If it happens again I'll send a ticket. I'll try later and replicate the error and let you know. Hopefully it's just a one time event.

This is the windows event report:

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: symmap.dll, version: 4.0.28.21686, time stamp: 0x594a71d6
Exception code: 0xc0000005
Fault offset: 0x0000000000007bbd
Faulting process id: 0x1b0c
Faulting application start time: 0x01d302bce3678c8f
Faulting application path: D:\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Prepar3D v4\symmap.dll
Report Id: 798aea1c-1b18-4b6a-9f7f-1f7f215ca7dd
Faulting package full name:
Faulting package-relative application ID:

I just got hit with the same problem as you. Did you open a ticket?

1 hour ago, evaamo said:

Did you open a ticket?

Not yet. I tried to duplicate the error but it didn't happen.

2 hours ago, bills511 said:

Not yet. I tried to duplicate the error but it didn't happen.

Same here... I've been trying to replicate it as well not no luck... yet.

Thanks!

-E

5 hours ago, bills511 said:

Not yet. I tried to duplicate the error but it didn't happen.

 

2 hours ago, evaamo said:

Same here... I've been trying to replicate it as well not no luck... yet.

Thanks!

-E

I'm guessing since you can't repeat it, the stars probably aligned that one time causing the crash. If it happens again, open a ticket, but right now without any repeatability, there's not much more they can go off.

6 hours ago, PMDG777 said:

 

I'm guessing since you can't repeat it, the stars probably aligned that one time causing the crash. If it happens again, open a ticket, but right now without any repeatability, there's not much more they can go off.

Just completed a 1.9 hr flight from KIND to KOSH. No errors.

Just my ears ringing from those awesome sounding radials.