• There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Unusual g2d.dll errors

WarHorse47

SOH-CM-2024
About a week ago I encountered a problem with my JustFlight PR9 Canberra. Whenever I attempt to load a flight I encounter a CTD. The aircraft loads to 100%, then I get an FSX error message and restart. Each time this happens the Error Log points to the g2d.dll module.

Now, as far as I can tell there have been no major changes to my system (Win8 or FSX). My default flight is the same and works on all other aircraft and helos. When I first got the Canberra I had no problems. Since then the only changes/additions to my FSX include the latest FSUIPC, two addon airports by Team SDB, and a few more addon aircraft.

The problem is limited to the Canberra. I have uninstalled and reinstalled at least 4 times, and did get in a couple flights. Yet this evening after not touching it for a couple days, I once again cannot get the aircraft to load. I even tried resetting the default flight to the Friday Harbor default flight, but the Canberra still will not load.

I've filed a ticket with JF Tech Support and exchanged e-mails, but they are baffled. I've looked for answers on the web and am not making much progress. Others have reported similar errors but more globally, meaning not related to a specific aircraft.

So, I'm totally open for suggestions or guidance at this point.

Thanks in advance.
 
Warhorse.
I had this problem with the MAAM B25 for FSX. The cause of mine was that Direct X 10 was activated, and was causing problems for it.
If you use Direct X 10 try turning it off and see if you still get the Error msg.
Aside from that I would have no ideas.
Craig.
 
I do not use DX10, and yes I keep my FSUIPC updated to the most current version.

It has been awhile since my original post. Since the error somewhat pointed to a gauge related issue, I examined the CanberraGPS.cab file and found nothing unusual. As a test I extracted the contents to a panel subfolder, and haven't had a problem since. Strange. Maybe my system was just being temperamental that day.
 
I do not use DX10, and yes I keep my FSUIPC updated to the most current version.

It has been awhile since my original post. Since the error somewhat pointed to a gauge related issue, I examined the CanberraGPS.cab file and found nothing unusual. As a test I extracted the contents to a panel subfolder, and haven't had a problem since. Strange. Maybe my system was just being temperamental that day.

Glad you got it worked out their Warhorse.
 
Back
Top