Hi Bob,

If you find a bug, please use the bug report form.
If you need tech support, contact tech support.

None of this should be in the blog comments.

Under radios -> GPS FMS -> you will find: Garmin_430_screen.png and Garmin_530_screen.png as well as Garmin_430.png. The two _screen options are new.

I am loaded with Windows 7 64 Bit 10.30b2.
PlaneMaker 10.30b2.
MY above comments are exactly the same.
No new GPS appears in the FMS/GPS Listing.
The data files are located in the Resources folder for the new gps and appear OK on display.

Hi Bob,

First, please update to beta 2. There was a bug in the error checking for GPS configurations in beta 1.

Second, this yes, it is definitely possible to put a G430 into the 2-d panel; the default Cessna ships this way!

cheers
Ben

Philipp..I am using the new Plane-Maker which is included in the release 10.30b1. It is the Windows Release. I can do the steps described by the 822414 instructions. up to the point of specifying the new revised GPS in the drop down#1 window’s check boxes.

Two problems.. First, my aircraft only shows a 2-d window in its construction. Selecting 3-d gives a full blank.
Second, no new GPS is shown as selectable in the FMS/GPS
drop down window in the instrument listing. The selection of the GPS in the 2-d window works… but that ends the described procedure that can occur, since no new GPS listing for the new GPS is available. The Folder GNS430 in the Resources Folder in the 10.30B1 Windows release does contain the files that the Plane Maker should access for the substitution.

Question: can the GNS430 be put into a 2-d panel cockpit, and does plane maker have the present capability to do this? Or does only a 3-d cockpit have the ability to receive it?

No kidding, Ben, thanks for the honest reply! So I must have seen the best and the worst of 3D shadows, and my recent experience was when the sun angle was just right. Seems to me that we discussed increasing the shadow map size sometime in the past. Might this be an opportunity for a tuning option, with a number of progressively larger maps to choose from. With an increase in pixel resolution on the map, the aliasing should, in theory, become less noticeable. It may need some anti-aliasing love too…when you get around to optimizing it. It’s a neat, cheap effect though, and really amps the realism inside the cockpit when you get an accurate shadow of the wing or something. Helps external views in videos too, if your system can’t handle HDR.

ok i will do!

this behavior comes from previos versions, so i thought it was an expected behavior being difficult to address. I just wanted to understand the insides and if any transition tweaks in the pipe for 10.30

I hate to state the obvious, but if there is a behavior that you do not like, and it has not changed, it should not be shocking that there is no mention in the change log. The change log lists only things that we actually changed (or things we think we actually changed).

Anyway, I think you know what I am going to say…please file a bug!

Yes, but as a customer, contact tech support (info@x-plane.com) if you want to talk to an actual human about an actual problem! The bug reporter and auto crash reporter are _not_ ways to contact tech support (nor is this blog).

I mean, some times you are flying a large jet at high altitudes 37 knots front wind, then when the weather engine updates METAR it may change in a fraction of time to 57 knots tail wind, as consequence you go overspeed in a second, the AP has no time for reacting and your long hours of flight end up due to structural damage.
You may be also flying a GA where those sudden weather updates gets your small light aircraft very critical trimmed crazy.
It will aso be much more nicer from visuals perspective, smoothness transitions from clear skies to cloudy or whatever transition the weather is doing.
hopefully you can share us a bit of the insides, i can imagine this is not in purpose! anything on your -to do- list about this? thanks a lot 10.30 is great to me