[MAC] x-plane crashes on loading CRJ

We have indentified the possible culprits:

4. Broken fonts

I have seen two crash reports in this thread related to broken fonts in OSX.

You can identify them by a crash involving the "HandleOFAScalerMessage" function. If you google for this fault, you will find that this is related to having either duplicate or incorrectly converted fonts installed. To fix this:

1. Open Fontbook

2. Select All (Cmd + A)

3. Select "Validate Fonts" from the file menu.

4. Remove any fonts marked as invalid or duplicate

For more info, please consult this article at Apple Support: http://support.apple.com/kb/ht2509

Philipp

I've validated my fonts (37 warnings) and deleted it. After that I did a clean install of the update (version 1.1) and did a testflight.

During the flight, 25 minutes after takeoff, the CRJ crashed to the desktop.

Rebooted the system and deinstalled all the plugins. After a restart of X-Plane I started a testflight. The plane crashed 5 minutes after the restart.

See below the log- und crashlog-files with and without the plugins:

hi jode. I don't know how to read propertly the logs file, but it seems in yours you have lots of errors in scenary installed. Can you make the test in a default clean demo version of xplane? Even flying over water.

I think the crashes are because memory and scenaries. A good way to test it doing what I said.

But Philipp will know better.

hi jode. I don't know how to read propertly the logs file, but it seems in yours you have lots of errors in scenary installed. Can you make the test in a default clean demo version of xplane? Even flying over water.

I think the crashes are because memory and scenaries. A good way to test it doing what I said.

But Philipp will know better.

I did this yesterday without the custom scenery on the same flight-route as today (EDFH-LEPA). Sorry, there are no logfiles. Today I reinstalled version 1.0

and I did a complete successfull flight along the above mentioned route. After uninstalling version 1.0 and installing version 1.1 I did two testflights with and without the

plugins and deleted wrong fonts. The first flight lasted 25 minutes and then came the crash (with plugins) and the second flight lasted only 5 minutes (without the plugins). The crashes couldn't be due the lack of memory and sceneries because version 1.0 works and other aircrafts work flawlesly.

I uninstalled version 1.2 and I'm no longer interested in testing, because I have not enough sparetime.

having the same problem with ctd.  i've attached the crash log.  weird thing is i was able to have one normal flight yesterday with v 1.1.  even after a restart and removing plugins i still have problems.  also i never messed with the files from v1.0 btw.

second_crash.doc

Team,

I just installed CRJ 1.1 using the installer and followed the directions as mentioned. No problems on install.

The CRJ loads then crashes after about a min. I uninstalled xpushback and removed all duplicate fonts. 

VER 1.0 ran great no problems.  Attached are my crash files as requested.

Cycle_Dump.txt

Log.txt

This is my last (?) crash report:

- Fresh install of X-Plane 9 without any scenery (except the default LOWI scenery) for testing purposes

- Update to version 9.69 with the latest updater

- Registering with GIZMO and shrink-wrap plugin was successfull

- Additional plugins to the default-plugins (GIZMO, shrink-wrap, pilotview)

- Testflight practical over water: EDFH-LEPA (planned route: EDFH DIR GEBDA Y173 PABLA Y163 NATOR UQ209 BALSI UQ211 VATIR UN852 PIVUS UZ237 SISMO UN855  KENAS LEPA) at FL 305

- 35 minutes after take-off over Switzerland the CRJ-200 Version 1.1 crashed (see the log-files)

Hardware: MacBook Pro, Intel Core 2 Duo, 2,8 GHz, L2-Cache 6 MB, RAM 4 GB, BusSpeed 1,07 GHz, used VideoCard: NVIDIA GeForce 9600M GT  VRAM 512 MB

(second VideoCard, not used for X-Plane, is a NVIDIA GeForce 9400M with 256 MB VRAM)

Joystick: Saitek Cyborg Evo Force

Sorry if i mistake. But i think Gizmo is not necesary to run the CRJ. Dont know if with activation is necesary.

But Philipp will try to find a solution for you.

that's an interesting point.  I did notice this gizmo plugin after installing 1.1 which I never noticed before.  are you suggesting we remove it from the plugins folder?  I'll give it a shot and post my results. 

that said though, I noticed yesterday on your site a section all about gizmo, what it is and why you guys use it.  if the CRJ was coded with it or whatever, then wouldn't it crash the plane to delete th plugin?

From what I know... (I am not programmer.. I know a little of C++) Philipp and Anton only used C++ for the programming of the CRJ. What I don't know if for the activation of the plane was used Gizmo. If you didn't put inside, then the installer did it.. and that was made by x-aviation so I think there is a reason because is inside. Don't know.... Cameron has to say something about this maybe.

But I don't have the Gizmo plugin inside my x-plane copy. So maybe is a good test if you try without it. There was a correction for Gizmo in 1.1 but maybe there are more variables that are making CTD with Gizmo inside (who knows.. we cannot control what people has inside their computers. Only can help them to solve their compatibility problems with the CRJ)

Thanks

Just tried removing the gizmo plugins.  Ran for about 30 seconds then CDT.  I don't know what the problem is, kinda sucks because now we can't use this plane at all.  Looks like there are other people who are posting similar results with fresh installs of x-plane and the original version of the plane worked fine with my setup and installed plugins (I only have a few anyhow).  Have you guys learning anything new on your end?

Hi, All,

Gizmo is required and is installed for you. The other plugin installed for you is called Shrink Wrap. These two plugins work together. Gizmo handles the cURL functionality to connect to the server while our other plugin handles the rest of the activation procedure.

Gizmo and Shrink Wrap are not the culprit here. I have done internal tests with customers who have had this crash problem, and to troubleshoot I have had them delete both Shrink Wrap and Gizmo. During these tests, the crashes still occur. There is something else at play here.

that's an interesting point.  I did notice this gizmo plugin after installing 1.1 which I never noticed before.  are you suggesting we remove it from the plugins folder?  I'll give it a shot and post my results. 

that said though, I noticed yesterday on your site a section all about gizmo, what it is and why you guys use it.  if the CRJ was coded with it or whatever, then wouldn't it crash the plane to delete th plugin?

I don't think, that the GIZMO plugin is the reason for the crashes, because on Monday, after registering and the first crash I removed GIZMO and the shrink-wrap plugin. I remeber, that I did a testflight from LOWW to EDDT and was very happy in the first 25 minutes of the flight,  that I had no crash. I thought, this could be, that I removed GIZMO and the shrink-wrap plugin. But during the flight, ca. 30 minutes after take-off, over Czechia, the CRJ-200, version 1.1, crashed to the desktop. After that I tried it with plugins and without plugins, with custom sceneries and without them, today in a separate installation of X-Plane without sceneries and only the default plugins plus GIZMO, shrin-wrap and pilotview, but the plane crashes after 2 to ca. 45 minutes after the start (this is different) . The problem could be the vasFMC plugin. I used GIZMO before the CRJ update, because the payware DASH 8 Q400 needs it and I had no problems with it, also with other planes and plugins, but this was not the GIZMO version, overwritten without asking me from the CRJ upgrade. Why do a payware aircraft need two plugins only for registering and why the installation software don't ask the user, when it overwrites a plugin, in this case GIZMO ?

Why do a payware aircraft need two plugins only for registering and why the installation software don't ask the user, when it overwrites a plugin, in this case GIZMO ?

Mainly because we are the subset of creators of Gizmo at X-Aviation, and we always ensure you have the LATEST version of Gizmo now. Keeping older versions may put you at risk of memory leaks, bugs, etc. As producers of the product, there's really no need.

The other reason being the CRJ will NOT work with older versions of Gizmo.

Why two plugins?

Because it's more efficient that way for many reasons, all in end of which aren't necessary to outline.

Thanks for chiming in!

Because Ver 1.1 crashes on me, I have decided to go back to Ver 1.0 until this gets corrected. Ver 1.0 seems to work fine.  I attempted to uninstall then install Ver 1.0 then upgrade to Ver 1.1 and the unexpected error continues after about 1-3 min. Last night after loading 1.1 I did notice to the right hand side of my screen a new Gizmo Icon that I did not have on Ver 1.0. One of the options is restart Gizmo. So I continued to restart Gizmo after a duration of every minute for 10 min and I did not get the error however after the 10 min I stopped restarting Gizmo and approx a 1 min 27sec later Xplane quit with the unexpected error.

Same for me. XP crashed twice on a flight from LFQQ to LFLB.

Log.txt

Same for me. XP crashed twice on a flight from LFQQ to LFLB.

Please crash log.

I guess this is this one.

error.pdf

That may help. But Philipp has to see it. When he is online he will reply and try to find a solution for this. For now I recomend all Mac users that have this problem change back to 1.0 version.

I have been making this test twice. First time I had a CTD in MAC but I was loading lots of chrome webbrowsers and in one of navigations with youtube video while the plane was running I had that CTD.

Second time it is still running after 2 hours with engines running and not doing anything (as the first time) But this time only after those 2 hours I write this post. Still not CTD.

I may think of several posibilities (with my totally ignorance in programming). It could be a memory leak.. but I don't see how the RAM memory goes down throught time. It stays going up and down but stable.

Maybe CPU temperature because more hot these days with full CPU loading? Nope... In windows same computer doesn't CTD and in MAC right now it is more than 2 hours with a hot Mac already. 77ºC all time stable (but usually CTD because CPU temperature are (in windows) blue screens. Don't know in Mac how they are).

So I may think that only changing lots of programs manipulation of them.. videos.. in parallel made the plane CTD....

I don't have Gizmo and none of the other plugins. But people says that without this still CTD happens.

Maybe the only difference then is that I don't have the CRJ protection version of its plugin.. and that is one of the most important changes in 1.1 from 1.0 version.......

well all of these are open thinkings I have... Lets hope Philipp soon gives us some light in this, and sorry for the problems you have with this CTD. I believe is one of the worst bugs someone can have, and I feel frustrated because of that. 

Third test, with activation the same as I were a costumer. No CTD in 45 minutes.. just leaving the plane in platform with engines running.

I would like to know if there are Mac users that fly the plane long enough and don't have any issue.

Thanks

I open it, then it freezes and crashes a few seconds later.

After reading many of the post's I decided to not give up and keep trying.  I installed a fresh copy of xplane 9, Installed the updates using the xplane updater. Installed CRJ Ver 1.0 - flew a flight from Denver to Phoenix no issue.  I then updated to Ver 1.1 without any install issues. Opened up the plane cold and dark and began moving through the checklist. I did not get far maybe 2 min and it crashed. Thought that might help. I have now restored my system with all addons and stuff back to configuration prior to this test. 

I think enough people have reported the same experiences that it confirms the fact that the culprit is somewhere within the 1.1 update.  At this point, I suppose all we can do is wait for the team to figure out the problem and do something about it.  I guess I'd be lying if I said I wasn't beginning to develop a bitter taste in my mouth considering the premium we paid for the CRJ, but I'm just trying to be patient and give them a little time.

Third test, with activation the same as I were a costumer. No CTD in 45 minutes.. just leaving the plane in platform with engines running.

I would like to know if there are Mac users that fly the plane long enough and don't have any issue.

Thanks

I flew it for 45 minutes with no issues.  I'm on an iMac mid 2010.  I deactivated xpushback and that's it.

Thanks

OK I think I might have stumbled on to a fix and I hope this works for all of you.  Here is what I did and now the 1.1 Version is working for me.  Just had it up for 17min and took a flight around the pattern.  No Problems:

1.  Made sure I had admin rights to this computer (System Preferences - Users)

2.  Installed Ver 1.0

3.  Tested it - no problems

4.  Removed Ver 1.0 using the "Uninstall CRJ-200 program located within x-plane main folder

5.  Used the MAC finder to search for "VASCORE"

6.  Found 5 Vascore folders and deleted them

7.  Unziped the Ver 1.1 update that I downloaded as per the email (I say this because before I was just running the installer (Update 1.1) that I previously unzipped.  Thought I would start fresh just in case.

8.  Installed the 1.1 Version using the installer file included in the update.

9.  Install completed no problems

10.  Restarted my system

11.  Started X-plane & loaded the CRJ 1.1 Engines Running

12.  Noticed that the Avionics Displays were blank (should be on for engines running)

13.  restarted Xplane and loaded CRJ

14.  No issues or crashes for 17 min and flew the pattern at KPHL

WOW that makes me very happy to report.  As a note I did have admin rights but just wanted to check.

I think it was the old VASCORE Folders and stuff.

Hope this helps It sure did for me and I have been spending alot of time trying to try different install methods.

Rod  

One more thing to my previous email.

I also removed xpushback and autogate plugin.

Rod