Cameron Posted June 9, 2011 Report Posted June 9, 2011 This topic is for those experiencing problems on the Mac with version 1.1.1 or above of the CRJ.Please do NOT post in this topic unless you have read and followed the procedure in the following topic: http://forums.x-pilot.com/index.php?topic=2486.0If you have followed the procedures as listed in the topic that brought you here, please attach your log.txt and crash.txt located in your main X-Plane directory. Give a brief explanation of what happened as well.Thank you! Quote
Disregard Posted June 12, 2011 Report Posted June 12, 2011 Hi!, I bought the A/C yesterday but as I choose it and try to open it the X-Plane crashes.Already tried to troubleshooted as you explain with the Demo version, but still, I choose the CRJ, it open for a few seconds then gets stocks and then after a few seconds everything closes with the following report that I ll attach.Can you help me?Thanks!Log.txtCrash_report_.doc Quote
philipp Posted June 12, 2011 Report Posted June 12, 2011 Is there a reason you are still running 10.6.0 when the current version 10.6.7 (10.6.8 in a few days)?I suggest updating your Mac OSX first, as there could be virtually any number of errors, perhaps even still related to the font stuff that gaves us so much trouble.Philipp Quote
xfan Posted June 17, 2011 Report Posted June 17, 2011 Here are my crash experiences plus other problems:My config is :MAC OS 10.6.7Processor : 3.33 GHz 6-core Intel Xeon, RAM 8Gp 1333 MHz DDR3X-Plane version is 9.70I got two kinds of crashes : 1- Desktop crash when loading X-Plane with CRJ200 as target aircraft in preferences, in that case, end of log.text is the following :Loading airplane number 0 with Aircraft/X-Aviation/CRJ-200 v1.1.1)/CRJ200.acf.Gizmo: C-Core:AircraftChanged()Gizmo: Calling OnBeforeReboot()Gizmo: Aircraft name: (CRJ200.acf)Gizmo: Aircraft path: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Gizmo: X-Plane Relative Folder Path: (Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Gizmo: X-Plane Relative File Path: (Aircraft/X-Aviation/CRJ-200 v1.1.1)/CRJ200.acf)Gizmo: Entered gizmo_Restart(..)Gizmo: Cleaning up.. Reset timers.. Reset menus.. Reset GUI Widgets.. Reset GUI Windows.. Reset OBJ8 handles..Gizmo: Releasing loaded objects in array, count: 0 Reset datarefs.. Reset Bullet Physics.. Reset OpenAL..Gizmo: Cleaning up OpenAL: Closing context and device. Reset Particle Engines.. Reset Lua.. Releasing all X-Plane overrides.Gizmo: Cleanup Finished.Gizmo: Starting up..Gizmo: OpenAL: Using shared OpenAL context.. Init: Bullet 2.77 - http://www.bulletphysics.org/Gizmo: Loading NAV constants..Gizmo: Init IO Jail..Gizmo: logging.debug: (Disabled: os.execute, os.tmpname, os.exit, io.popen)Gizmo: logging.debug: (Sandboxed: io.open, os.remove, os.rename)Gizmo: Loading Firmware..Gizmo: LoadScript from File (firmware_init.lua)Gizmo: logging.debug: (print function patched.)Gizmo: logging.debug: (Firmware v11.4.25.1049)Gizmo: logging.debug: (Secured IO: io.open: /Volumes/X-Plane/X-Plane 9.40/Resources/plugins/Gizmo.plugin/firmware/repo_manifest.lua / r)Gizmo: logging.debug: (Secured IO: Approved safe filename for io.open: (Resources/plugins/Gizmo.plugin/firmware/repo_manifest.lua)) 32bit GL upload. RGBA src. 32bit GL upload. RGBA src. 32bit GL upload. RGBA src. 32bit GL upload. RGBA src.Gizmo: MD5: /Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/CRJ200.acf: c580a3908fb585d8d7383d2b9924b65f Releasing all X-Plane overrides.Gizmo: Loading init...Gizmo: LoadScript from File (init.lua)Gizmo: Event Map cleared.Gizmo: logging.debug: (CRJ200.acf)Gizmo: logging.debug: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Gizmo: logging.debug: (boot)Gizmo: Completed gizmo_Restart(..)shrink-wrap: Aircraft path: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Fetching plugins for X-Plane:X-Plane 9.40:Aircraft:X-Aviation:CRJ-200 v1.1.1):pluginsLoaded: X-Plane:X-Plane 9.40:Aircraft:X-Aviation:CRJ-200 v1.1.1):plugins:CRJAvionics:mac.xpl.WARNING: object Aircraft/X-Aviation/CRJ-200 v1.1.1)/objects/Cockpit_PanelCentral.obj has normals of the wrong length.WARNING: object Aircraft/X-Aviation/CRJ-200 v1.1.1)/objects/Cockpit_PanelSuperior.obj has normals of the wrong length.WARNING: object Aircraft/X-Aviation/CRJ-200 v1.1.1)/objects/Cabin.obj has normals of the wrong length.WARNING: padding is not integral! (in sign '{@Y,^u}W2{@L}W2{@Y,^r}W3{@@,@L}W2{@Y,^l}GATES_V' from airport LFPO)WARNING: padding is not integral! (in sign '{@Y,^u}SOUTH{@L}W1{@Y,^r}RAMP_N{@@,@Y,^lu}W44{@L}W41{@Y,^ru}W1' from airport LFPO)Preload time: 819625.Total load time: 38Gizmo: logging.debug: (Gizmo Shell 11.4.25)[CRJ] Loading navdata.[CRJ] 10650 airports were loaded.[CRJ] 7834 ndb were loaded.[CRJ] 4295 vor were loaded.[CRJ] 6104 ils were loaded.[CRJ] 203963 intersections were loaded.[CRJ] 8409 airways were loaded.2- FreezeThis happenes when from within X-Plane, loaded with another aircraft, I attempt to load the CRJ200. Sometimes, loading succeeds and the freeze happens when reloading CRJ200 once again. The only way out of the freeze is a reboot of the computer.Normally, during CRJ200 Loading, there is a phase where the "GIZMO" name appears in a yellow rectangle at the bottom right of the screen and then fades out. The freeze occurs just before the fading. The end of log.text is the following :Loaded: X-Plane:X-Plane 9.40:Aircraft:Perso Helico:BK-117:plugins:BK117:mac.xpl.WARNING: object Aircraft/Perso Helico/BK-117/BK-117_cockpit.obj has normals of the wrong length.WARNING: object Aircraft/Perso Helico/BK-117/BK-117_cockpit.obj has normals of the wrong length.Preload time: 1752.Gizmo: logging.debug: (Gizmo Shell 11.4.25)Loading airplane number 0 with Aircraft/X-Aviation/CRJ-200 v1.1.1)/CRJ200.acf.Gizmo: C-Core:AircraftChanged()Gizmo: Calling OnBeforeReboot()Gizmo: Aircraft name: (CRJ200.acf)Gizmo: Aircraft path: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Gizmo: X-Plane Relative Folder Path: (Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Gizmo: X-Plane Relative File Path: (Aircraft/X-Aviation/CRJ-200 v1.1.1)/CRJ200.acf)Gizmo: Entered gizmo_Restart(..)Gizmo: Cleaning up.. Reset timers.. Reset menus.. Reset GUI Widgets.. Reset GUI Windows.. Reset OBJ8 handles..Gizmo: Releasing loaded objects in array, count: 0 Reset datarefs.. Reset Bullet Physics.. Reset OpenAL.. Reset Particle Engines.. Reset Lua.. Releasing all X-Plane overrides.Gizmo: Cleanup Finished.Gizmo: Starting up..Gizmo: OpenAL: Using shared OpenAL context.. Init: Bullet 2.77 - http://www.bulletphysics.org/Gizmo: Loading NAV constants..Gizmo: Init IO Jail..Gizmo: logging.debug: (Disabled: os.execute, os.tmpname, os.exit, io.popen)Gizmo: logging.debug: (Sandboxed: io.open, os.remove, os.rename)Gizmo: Loading Firmware..Gizmo: LoadScript from File (firmware_init.lua)Gizmo: logging.debug: (print function patched.)Gizmo: logging.debug: (Firmware v11.4.25.1049)Gizmo: logging.debug: (Secured IO: io.open: /Volumes/X-Plane/X-Plane 9.40/Resources/plugins/Gizmo.plugin/firmware/repo_manifest.lua / r)Gizmo: logging.debug: (Secured IO: Approved safe filename for io.open: (Resources/plugins/Gizmo.plugin/firmware/repo_manifest.lua)) 32bit GL upload. RGBA src. 32bit GL upload. RGBA src. 32bit GL upload. RGBA src. 32bit GL upload. RGBA src.Gizmo: MD5: /Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/CRJ200.acf: c580a3908fb585d8d7383d2b9924b65f Releasing all X-Plane overrides.Gizmo: Loading init...Gizmo: LoadScript from File (init.lua)Gizmo: Event Map cleared.Gizmo: logging.debug: (CRJ200.acf)Gizmo: logging.debug: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Gizmo: logging.debug: (boot)Gizmo: Completed gizmo_Restart(..)shrink-wrap: Aircraft path: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/)Fetching plugins for X-Plane:X-Plane 9.40:Aircraft:X-Aviation:CRJ-200 v1.1.1):pluginsLoaded: X-Plane:X-Plane 9.40:Aircraft:X-Aviation:CRJ-200 v1.1.1):plugins:CRJAvionics:mac.xpl.WARNING: object Aircraft/X-Aviation/CRJ-200 v1.1.1)/objects/Cockpit_PanelCentral.obj has normals of the wrong length.WARNING: object Aircraft/X-Aviation/CRJ-200 v1.1.1)/objects/Cockpit_PanelSuperior.obj has normals of the wrong length.WARNING: object Aircraft/X-Aviation/CRJ-200 v1.1.1)/objects/Cabin.obj has normals of the wrong length.Preload time: 1993.Gizmo: logging.debug: (IPC kickoff)shrink-wrap: License file: (/Volumes/X-Plane/X-Plane 9.40/Aircraft/X-Aviation/CRJ-200 v1.1.1)/license_key.txt)shrink-wrap: License Verified. Sending Systems.Gizmo: Plugin Message: com.x-aviation.shrink-wrap is sending us a text chunk of Lua script.Gizmo: LoadScript from Buffer (com.x-aviation.shrink-wrap/text/xpl-ipc)Gizmo: Event Map cleared.Gizmo: logging.debug: (Gizmo Shell 11.4.25)[CRJ] Loading navdata.[CRJ] 10650 airports were loaded.[CRJ] 7834 ndb were loaded.[CRJ] 4295 vor were loaded.[CRJ] 6104 ils were loaded.[CRJ] 203963 intersections were loaded.[CRJ] 8409 airways were loaded.Of course, I went through all the tedious procedure described in your 2486 topic.In the demo mode with minimal plugin config, no crash.I then reactivated my original X-Plane version with minimal plugin config, no crash.I reintroduced my original plugins, one by one, the surprise was that after reinstalling everything as before, neither the crash nor the freeze reappeared.So I am back from where I started and I am unable to reproduce the problem. I am afraid that it still there somewhere and will eventually come back.I have 2 other issues, the first might well be related with the crash bug :- Lack of fluidity issue :With reasonable objects rendering settings, I have good frame rate and good fluidity with all my aircraft, including the most demanding with the exception of the CRJ200. With CRJ200, the frame rate is extremely unstable, always jumping between 15 and 60. Furthermore, even when it reads 60, all movements are slow and jerky, to the point that the aircraft is almost impossible to fly. Reducing more and more the rendering settings makes very little change.Fluidity is better with demo version so I still have some investigation to make about plugin compatibility.- FMS issue :During input of a flight plan, when an ambiguous waypoint is entered, the FMS asks for precision. This choice is taken into account in the flight plan. This is OK. Unfortunately, when the route is saved, the full identity of the waypoint is not memorized and the ambiguity remains in the stored route. This is bad enough but the worst is still to come :When a saved route is loaded, the FMS asks once more to select between the possible waypoints with the same name, IT does take into account the selected one but, all the subsequent waypoints in the flight plan are deleted and must be manually reentered one by one!The overall conclusion is that in the present state, I find the aircraft useless. Considering it's outstanding graphic qualities, it is a great pity. I know you are working hard on it and I am sure that you will succeed.All the best to you all. Quote
philipp Posted June 17, 2011 Report Posted June 17, 2011 Hi xfan,First, the Log.txt alone is rather useless. When X-Plane has a crash to desktop, there is a crash_log.txt generated that you should post alongside with the Log.txt. Only when I see both of them I have a chance to narrow down the root cause.However in your case I have a very good idea of what is going on. You must remember that there are two kinds of plugins: global plugins and per-aircraft plugins. You already ruled out the global plugins given the procedure you described, this is fine. Then there are plugins tied to specific aircraft, that get only loaded when this aircraft was loaded once in your sim session. And here I see a possible culprit: You use the ND Art BK117, which in turn uses the Dreamfoil sound engine. The Dreamfoil engine is known to be incompatible with the CRJ. This issue is already under investigation with the developer of Dreamfoil, so you can expect a fix in the next update. For now you can fix this only by not loading CRJ and Dreamfoil in the same sim session.About your unstable framerate, as you said that it is better in the demo version it might be related to some of the other aircraft loaded. Also, overall fluidity is greatly improved by limiting your frame rate. 60fps is completely useless. I found that using X-Plane's option to limit to 30 (half the rate of a 60Hz monitor) gives the most smooth experience, as the frame rate stays at 30 then. For comparison, I run my Mac tests on a 2.4GHz dual core with smooth 25-30fps, so you should be able to fly on a 3.3Ghz six-core without any problems. It is a known issue however, that the refresh rate is worse when the LEGS page of the FMS is displayed in contrast to e.g. the FPLAN page. While this has been improved in the 1.1 update, it is still noticeable, if only barely for me. Could you test if what you call "jerky" depends on the LEGS page being displayed on the FMS?Last, your flightplan issue. This has been discussed before. The FMS stores and loads ICAO routes. This is nothing more than a text. If the text contains an ambiguous waypoint, even when tied to an airway, how would the FMS be supposed to select "the right one"? Yes, it might just select the "geographically nearest" one or "most likely" one, but this is dangerous, and by all means forbidden. I would like to remind you of the American Airlines 965 accident, where they flew a perfectly working 757 into a mountain by just selecting the "nearest" waypoint when resolving an ambiguity. Ouch. Now I hope you understand why we can't automatize the WPT SEL page when loading an ICAO route.What we could do instead is emulate the function where you get your fligthplan as a company route, that is stored on some kind of floppy disk that is read into the FMS like it is done for an AIRAC database update. As far as I know, these routes are stored in an unambiguous format where these problems cannot occur. I would have to check my manuals to see how to implement this correctly, though. This is certainly a feature I want for future CRJ updates, I just have to figure out some clever way of simulating you inserting a floppy disk with the company routes Regards,Philipp Quote
xfan Posted June 17, 2011 Report Posted June 17, 2011 Hi Philipp,Thanks for that quick answer, I just managed to trace down the origin of the lack of fluidity. It is caused by a Python script named "FSWidgetsGMap", it is an add-on which is supposed to show the flight path on a google map. I have never used it but it was in my PythonScripts folder and it seems to interfere in some way with The CRJ200, the result being an erratic frame rate. What looks like a freeze is in fact a very low frame rate, less than 1 fps. What makes the problem tricky is that the amount of speed loss seems to depend on some values contained in a file automatically created by the script in the plugin folder, the name of that file is "FSWidgetsGMap" these values are not always the same and look like geographic coordinates. The FSWidgetsGMap script has no effect on other aircrafts.Anyway, after deleting the script, the CRJ200 behaves normally with or without the "legs" page display.I strongly suspect that in my case, the desktop crash I experienced when opening X-Plane with the CRJ200 as selected aircraft, had the same cause.As far as the FMS issue is concerned, I am not sure that you have fully read my message. I quite understand that storing only the ICAO route doesn't give any information to the FMS regarding the right waypoint selection in case of ambiguity, but, as you say, it might not be impossible to store that information as well, after all, the standard X-Plane FMS does it. But my main issue is different: Accepting the fact that after loading a stored route, one has to answer to the WPT SEL page, I don't understand why all the other waypoints of the route are lost and have to be reentered manually, just as if they had never existed in the stored text. What happens is that after filling the WPT SEL page, when you go back to the legs page, it shows only a direct route from the just selected waypoint to the arriving airport, all the intermediate waypoints have simply ceased to exist.I am french and English is not my mother language, so I apologize if I didn't make myself clear in the first place.CheersMichel Quote
davidngr Posted June 19, 2011 Report Posted June 19, 2011 Failed to follow the instructions listed for the criteria to post in this topic. Please re-read: http://forums.x-pilot.com/index.php?topic=2486.0Cameroncrash.docLog.txt Quote
Cameron Posted June 19, 2011 Author Report Posted June 19, 2011 David,Your topic has been edited. Please follow the criteria as outlined in the linked topic. Quote
xfan Posted June 21, 2011 Report Posted June 21, 2011 Hi Philipp,Here is a report of another compatibility problem.This time it is with a specific aircraft plugin, the B17G available here:http://forums.x-plane.org/index.php?app=downloads&showfile=13235After loading and flying this aircraft, loading the CRJ200 results in an X-Plane freeze.I checked that the freeze happens also in the 2486 topic's conditions.I also found that selecting visible items in the FMS Display Menu is extremely expensive in frame rate. Only one item is enough to lower frame rate from 30 down to less than 20. Is it normal?Hope it helps.CheersMichel Quote
Japo32 Posted June 21, 2011 Report Posted June 21, 2011 what do you mean in visible ittems? Well it is normal have from cold and dark situation to switch on battery a drop up to 50% of frames. That is normal for now. Quote
xfan Posted June 21, 2011 Report Posted June 21, 2011 The FMS display menu shows a list of items : Navaids, Intersections, Airports, NDBS situationWhen selected, these items are made visible on the moving map which is displayed in the MFD with the flightplan.The frame rate drop I mention has nothing to do with battery switch on. It concerns "in flight" situation, with or without some of these items displayed in the MFD. Quote
Japo32 Posted June 21, 2011 Report Posted June 21, 2011 Yes that is normal. If you put lots of fixes with a high range map (lots of them visible) then you will lose fps. Of course with a not good computer is good you don't show fixes with zoom out. Quote
Kieran Posted October 9, 2011 Report Posted October 9, 2011 I bought the CRJ yesterday, and have been flying it with the help of the video tutorials. So far I have twice flown the aircraft successfully to the final approach, only to have X-Plane crash to the desktop.Attached is the System specs and my log.txt. I can't seem to find my crash.txt.CheersKieranLog.txt Quote
philipp Posted October 9, 2011 Report Posted October 9, 2011 The log file alone does not show any hint as to why it would crash.When X-Plane crashes, it should generate a crash report you find under Application/Utilities/Console then click "user Diagnostic Report" and look for the most recent entry with "X-Plane" in it. Paste the contents here and we'll have a look.Philipp Quote
Kieran Posted October 9, 2011 Report Posted October 9, 2011 (edited) I have just successfully done the tutorial flight, but with out the tutorial, so I did it in a much shorter time period (the two failed attempts included a lot of pausing).However this is the last entry for X-Plane from the previous attempt.9/10/11 1:12:42 PM [0x0-0x1dd1dd].com.laminar_research.X-Plane[2412] Kicking off async tex load.Thanks for your time Philipp,Kieran Edited October 9, 2011 by Kieran Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.