[ Closed ] v1.1b3 distributive (Windows 7/8, MAC OS) (Page 1 of 2)

CTD before taxi

Please disable the captcha key I have to solve the puzzle for every file I upload  it's a ridiculous waste of time! Thanks!

The Co-pilot CHRONO button is just a dark black hole, the pilot side is fine
Mac OS beta 3

good day,
I just down loaded B3 , and now I don't have the keys to start <?>
the aircraft I only have it installed on one computer and I do have back-up disk
what to do? I was asked to enter the key two times ? why ?
I was able to re-install B1 from back-up so all is not lost.
and it was working well.
thank-you for a re-set if the key. [I do believe I have used three up to this point]
captbullett

good day,
a log.txt would help to solve the issue.
captbullett

First try first crash.

MacOS 10.10.3, XP 10.35r1

Preflight -> Push back -> lining up -> Accelerated on RWY -> CTD

All betas are not stable, not flyable for me right now.

Version for me with nearly no CTD was/ is V1R2.

good day,
if you want some help read the txt i attached:

http://jardesign.org/forum/misc.php?act … str=49t995
captbullett

So trying to do a second test flight with 1.1b3 but now with all sound plug-ins (3D sound 2D sound 1D sound plug in) disabled. Same result CTD when accelerating on RWY. So to my mind the failure which results in the CTDs is in the main plug-in or SASL plug in.
Accidentally I closed the Mac Crash report and couldn't recover it. So only XP log and bb log attached.

As I see, all typical MAC log have crashed tread like this

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   mac.xpl                           0x00000000a10c733f 0xa107d000 + 303935
1   mac.xpl                           0x00000000a10c40c3 0xa107d000 + 291011
2   mac.xpl                           0x00000000a10d08e6 0xa107d000 + 342246
3   mac.xpl                           0x00000000a1095384 0xa107d000 + 99204
4   mac.xpl                           0x00000000a10a2d7e 0xa107d000 + 155006
5   mac.xpl                           0x00000000a1080ded 0xa107d000 + 15853
6   XPLM                              0x0000000013751291 XPLMDispatchDrawingHook(int, int, int) + 121
7   XPLM                              0x00000000137515bc XPLMDisplayDoDrawingHook(int, int) + 740
8   com.laminar_research.X-Plane      0x0000000100927492 XPPDoDrawingHook(int) + 114
9   com.laminar_research.X-Plane      0x00000001007916bd APP_update_panel(panel_draw_type, int) + 1069
10  com.laminar_research.X-Plane      0x000000010092dad3 grab_one_panel_texture(OGL_framebuffer*, int, int, int, int, int, panel_draw_type, int, int) + 1395
11  com.laminar_research.X-Plane      0x000000010092e476 grab_panel_textures(int, int, int) + 2198
12  com.laminar_research.X-Plane      0x000000010060f44f WORLD_scene_per_frame() + 3071
13  com.laminar_research.X-Plane      0x0000000100b22f95 APP_update() + 3061
14  com.laminar_research.X-Plane      0x0000000100b256d2 MACIBM_post_event_proc() + 226
15  com.laminar_research.X-Plane      0x0000000100c793cb WIN_run_app + 43
16  com.laminar_research.X-Plane      0x000000010061d053 main + 1075
17  com.laminar_research.X-Plane      0x00000001004918c0 start + 52

So, "0" is a crashed module with crashed functions.
0   mac.xpl                           0x00000000a10c733f 0xa107d000 + 303935

It is SASL base plugin mac.xpl with different functions address. As the man who build this mac.xpl set debut options disable and as result we can't read name of this (crashed) functions, just its address, what can give nothing. So, I talked with Ramzess and he promise give build and give for tests mac.xpl with debug functions on. If will be, we will understand what function(s) called from lua give mac crashes. Thats a plan, but need wait MAC OS SASL build with debug info option.

Here's my clean XP installation 1v1b3 CTD

Mac OS X 10.9.5
XP 10.35r1 without no nothing (not even terrain scenery...)

Mac didn't give me no crash log this time

I was just climbing out of LSZH, was a bit to slow, hit the AP button, ctd

Good day,
I downloaded version b3 and when I wen to enter the key I was asked to enter it two times , the aircraft would not load and I wait for your instructions ?
no more keys and did not use all of them as i did not need them i have one computer installed with your aircraft
thank-you
captbullett

Good day,
issue resolved, I was using the A320neo key instead of the A330 Key
My Bad …
thank-you for the help
captbullett

I don't know exact future. It is not depend from me, but until a lot of SASL-based aircraft have this problems, we will hope to resolve it.