Jump to content

[SOLVED] Version 1.5.2 Issues

jeanlune

By jeanlune
in Canadair CRJ-200

 Share

Recommended Posts

jeanlune Newbie

jeanlune

Posted
Posted

Hello Guys, yet another one (seems pretty unlucky those time)...

 

Scenario is the following :

 

X-Plane V 10.11R3 + CRJ 200 V 1.5.2

 

Made à Fresh install on Windows 7 64, Open Scenery + Salamanca and Valencia.

Cold start on ramp 5 at Salamanca, just click on the upper arrow from the FMS at any time and --> Kicked back to desktop.

I ve exactly the same issue from the same machine on Mac Os X 10.8.2...

 

(72 Kb Log is from W7 and 52 Kb is from OsX)

Intel Quad Core 2.83 Oc 3.4 Geforce GTX660 2Gb Vram.

I'm surely missing something since in any case I don't have any crash.txt file.

 

Anyway great Job the CRJ seems awesome (And I only was on the ground... :D)...

 

Latest Nvidia drivers on Both OS. If someone has any idea.

Log.txt

Log.txt

Link to comment
Share on other sites
philipp Newbie

philipp

Posted
Posted

The crash log is inconclusive, but given the fact that your run

-Mac

-32bit

-additional scenery

makes it _very_ likely that it's an out-of-memory.

 

Try reducing texture resolution as well as world detail distance to conserve memory.

X-Plane 10.20 will be out of beta one day, then we can all use 64bit and no longer have these kind of problems.

 

Philipp

Link to comment
Share on other sites
jeanlune Newbie

jeanlune

Posted
  • Author
Posted

Hi Philipp,

 

For the record, I got the same issue with a clean install on Windows 7 that's why I posted both Logs and above all that's why I posted in the Windows and not Mac Section ;)

So this is OS unrelated.

Even made à test with 10.20B (running in 32 Bits).

I Clearly suspect NVidia Card, so I'm gonna make a test with Radeon GPU (5670 from My Kidz).

 

Btw texture settings are high (not very high or Extreme) since My MB only supports PCIE 2.0 and graphic card is 3.0, higher makes Frame rate drop too much (not running under 30 Fps).

 

Thx anyway.

Link to comment
Share on other sites
jeanlune Newbie

jeanlune

Posted
  • Author
Posted

Well, I'm not so stupid to accept any bet on that :rolleyes:.

 

In the mean time this seems to be the faulty Thread :

 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   mac.xpl                            0x298b0278 AIRNAV::CDU::FMS4200PageManager::FKUP() + 52

1   mac.xpl                            0x298b2a5a openGLCDU<PPLcrj14::OverlayGauge>::handleNonDragClick(int, int) + 2520

2   mac.xpl                            0x29925dac PPLcrj14::OverlayGauge::handle2dClickCallback(void*, int, int, int) + 660

3   mac.xpl                            0x29925e3b PPLcrj14::OverlayGauge::handle2dClickCallback(void*, int, int, int, void*) + 45

4   XPLM                               0x16f85333 XPLMDisplayMouseClickHook(int, int, int) + 161

5   com.laminar_research.X-Plane             0x00868b1f XPPMouseClickHook(int, int, int) + 335

6   com.laminar_research.X-Plane             0x00a60a74 xplane_window_delegate::mouse_down(void*, int, int, int) + 260

7   com.laminar_research.X-Plane             0x00ba3bf9 -[WIN_OpenGLView mouseDown:] + 121

8   com.apple.AppKit                       0x91edaa21 -[NSWindow sendEvent:] + 6968

9   com.apple.AppKit                       0x91ed5a0f -[NSApplication sendEvent:] + 4278

10  QtGui                              0x2b933dec -[QNSApplication qt_sendEvent_replacement:] + 76

11  com.laminar_research.X-Plane            0x0038c1a7 WIN_event_loop_once + 343

12  com.laminar_research.X-Plane            0x00ba485c WIN_run_app + 44

13  com.laminar_research.X-Plane            0x0057c6ed main + 1501

14  com.laminar_research.X-Plane            0x003f7239 start + 53

 

Actually installing on my LapTop (F...ing Optimus card with an nVidia Quadro 1000M) SO I'm gonna run the test on Windows From Demo Install.

 

FMS4200PageManager::FKUP Is exactly what I do to provoke Crash...

 

This is only intuition, but I'm pretty sure that fault is located at low Level API (but Which one ?? :P :P ) I keep Testing and will come back to You if've any further valuable info to help Diagnosis.

 

Thank's anyway...

Link to comment
Share on other sites
jeanlune Newbie

jeanlune

Posted
  • Author
Posted

Hi Cameron,

 

First of all I know how it is hard for you to face such a variety of user/Config/mistake and so on, that's my job too.

 

I have to insist a bit, I can't see how it could be an "out of memory" unless you tell there is no way to make CRJ200 1.5.2 run under XP10 32 Bits (which I can barely imagine).

Sometime I can do some weird stuff with my computer but when I got a strong issue to troubleShoot, I come back to basics.

 

Let me explain :

 

- Clean Install from XP10 Demo (Alright the french version seems to log a tons of error about translation, but there's nothing I can do about this is from laminar).

- Running on Windows 7 With latest Drivers/Bios for my HardWare

- Minimal config (HardCopy of screen inside).

 

Tested on Two Different computer.

- Home Computer is GigaByte EP45 + GeForce GTX 660 + Intel Core 2 Quad 8 Gb Ram)

- Pro Laptop DELL Precision 4600M Geforce Quadro 2000 + I7 + 8Gb Ram

 

Both on Windows 7 64 SP1 --> Exactly the same failure with Mac OS Mountain Lion 10.8.2...

 

This Also occurs on Laptop wether I run it either on Quadro or Intel HD3000 Graphics (Which is ridiculous I admit it).

 

This is even crashing if I push the upper arrow on FMS with plan totally shutdown (Cold Dark situation, I push the button without even switching battery on, it's the quickest way ti get back on desktop).

 

So I'm confident in the fact that sooner or later it will finally work, but there I'm a little but frustrated. And I don't even speak of ATG Javelin I also I've a little problem with.

 

So, I'll be glad to downgrade to 1.4.5 since I'd like to fly a bit, but unfortunately, I have no idea of where I could find the 1.4.5 version.

 

Again I'm not a yelling customer, and I really still think this is an awesome bird and a huge project that is hard to stabilize, indeed I need a little help to work it out.

 

(Had to add a txt extension since the uploader seems to forbid anything else).

 

MP4 file is a little video of the config screen enclosed and the crash that occurs everytime.

 

Best regards.

 

JL

20130127_012924.mp4.txt

Log.txt

crash_report_01_27_2013_00_29_50.rpt.txt

post-9740-0-97685700-1359248635_thumb.jp

Link to comment
Share on other sites
Cameron Mentor

Cameron

Posted
Posted

I understand you have doubts, but both Phil and I have been around the block more than a thousand times (literally) with memory issues. X-Plane 10 is a hungry application and leaves little room for add-ons. This is why 64-bit is so important. 1.5.2 incorporates plenty of differences to the extent that your issue has been proven memory related many times.

To obtain 1.4.5 please shoot off a message using the contact form on X-Aviation requesting such. We'll be happy to get you sorted!

Link to comment
Share on other sites
cessna729 Newbie

cessna729

Posted
Posted (edited)

I understand you have doubts, but both Phil and I have been around the block more than a thousand times (literally) with memory issues. X-Plane 10 is a hungry application and leaves little room for add-ons. This is why 64-bit is so important. 1.5.2 incorporates plenty of differences to the extent that your issue has been proven memory related many times.

To obtain 1.4.5 please shoot off a message using the contact form on X-Aviation requesting such. We'll be happy to get you sorted!

Hi Cameron & Philipp, I'd agree 95% of the time with many "user reported problems lately". But with respect to the "UP ARROW" bug that jeanlune discovered in post #1, I'm sorry to disagree with you, as this appears to be a repeatable effect (at KRNT anyway), which IMHO is not fixed by using the CRJ-200 64-bit plug-in on my Windows 7 machine, or by down-grading to ver 1.45, or by using XP9.70 as it happens.

 

I don't think it's a big problem, and the work round is simple, don't press the UP ARROW key on the CDU before you have a active flight plan to step through on the ND in PLN mode (which is the only function of that key that I know of anyway) :)

 

@ Philipp

I ran a test wih XP 10.11 and CRJ-200 Ver 1.4.5-aee94cb and again with XP10.20b11 (64-bit) and CRJ-200 ver 1.5.3-32009f0 (64-bit) and X-Plane 9.70 as well, and got the same results, CTD.

 

The attached winzip files each contain the Log.txt, Cycle Dump.txt and the relevant XP cash dump report files.

Here is a short vid (using FRAPS so it stops on the CTD) :o

As I said, it's no big problem as normally you don't use the UP ARROW key on the CDU for anything untill you have an active  PLN anyway, and once you have an active flight plan pressing the UP ARROW dosn't cause a CTD (on my machine that is). Also if it's any help my Windows 7 (64-bit) machine has a EVGA GTX580 GPU with 1.5GB and Nvidia GeForce 310.70 drivers (in case it's a NVIDIA related problem).

 

Update 1: The UP ARROW key causes a CTD on X-Plane 9.70 as well even starting "Engines running", (that is if there is no active PLN).

 

Update 2: Even using Remote CDU "Up ARROW" key cases the same CTD.

cessna729.

CRJ-2 Ver1.45 UP ARROW CTD.zip

CRJ-2 64bit UP ARROW CTD.zip

Edited by cessna729
  • Upvote 1
Link to comment
Share on other sites
philipp Newbie

philipp

Posted
Posted

Interesting. But unless the OP is pressing the FMC up arrow key in uninitialized state on purpose, it doesn't change anything, right?

 

Nevertheless I just fixed that for the final 64bit update - which will not be out before Laminar declares X-Plane 10.20 final. More info on that here: http://developer.x-plane.com/2013/01/whats-left-in-the-10-20-betas/

Link to comment
Share on other sites
cessna729 Newbie

cessna729

Posted
Posted (edited)

Interesting. But unless the OP is pressing the FMC up arrow key in uninitialized state on purpose, it doesn't change anything, right?

I don't know if the OP was just pressing the FMC up arrow key in uninitialized state on purpose or not. But you are correct in that I could only force the FMC to cause a CTD, "by pressing that key when there was no ACTIVE PLN", i.e. "in an uninitialized state".

Note: I didn't try it during my testing, but guess the "DOWN ARROW" may have had a similar problem?

If users follow the check lists and normal SOP's, they are not likely to have had a problem with the "UP ARROW KEY".

When there was an ACTIVE PLN, the UP ARROW key works correctly as expected (No CTD and all is ok, :)

cessna729.

Edited by cessna729
Link to comment
Share on other sites
jeanlune Newbie

jeanlune

Posted
  • Author
Posted

Hello All,

 

indeed great thank's to all... Sorry I missed all this stuff was on the road for job :unsure:.

 

Uncaught exception seems quite more consistent. And from now we can live with it for while.

Found it with a foolish misclick, will be be careful on next attempt. 

Think we can close this one :D 

 

Good job guys !

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...