1 minute ago, turbomax said:

no, from JustFlight? 

Yeah 

10 minutes ago, Ray Proudfoot said:

As Goran has suggested any bugs should be reported via the correct channels. AvSim is for discussion, not bug reporting. Keep discussions civil without sarcasm.

But he’s discussing the bug he found in a beta? 🤷🏻‍♂️ Who’s to say he hasn’t reported it? 

6 minutes ago, Ianrivaldosmith said:

But he’s discussing the bug he found in a beta?

thanks Ianrivaldo, but I gave up on this, as it is not always immediately clear where the bug comes from: new beta version or existing addons that are no longer compatible. I have WorldTraffic 3 but haven't used it in years because it was too cumbersome, more a developer tool than a finished end user product.

Edited November 16, 20232 yr by turbomax

18 minutes ago, turbomax said:

thanks Ianrivaldo, but I gave up on this, as it is not always immediately clear where the bug comes from: new beta version or existing addons that are no longer compatible. I have WorldTraffic 3 but haven't used it in years because it was too cumbersome, more a developer tool than a finished end user product.

Yeah that’s why back in the xp11 days I always used traffic global. Seems ok in xp12 too. No messing. 

35 minutes ago, Ray Proudfoot said:

AvSim is for discussion, not bug reporting

interesting, when the thread starts like this:

Bug fixes:

• XPD-14740 – Crash due to broken navdata not being handled correctly
• XPD-14735 – Dataref Read/Write Ability Gone
• XPD-14736 – 2D panel rendering broken with panel/always_render art control
• XPD-14718 – Missing OBJs of new fire extinguishers
• XPD 14670 – Icing effect doesn’t properly take thermal sources into account
• XPD-14689 – Window icing glows in the dark
• XPD-14692 – Rain on windshield visible in “forward with nothing” view and disabled windshield effects
• XPD-14673 – Hot Start CL650 crashes on startup due to a previously writable X-Plane dataref having been changed to read-only
• XPD-14717 – Aircraft Class in Analytics Needs to be Untranslated
• XPD-14721 – New Gateway/Global airports recut!
• XPD-14729 – Thousands of new log warnings
  • Fixes flood of iCCP: known incorrect sRGB profile in log.
• XPD-14716 – FMOD event velocity is apparently set the same as the vehicle velocity
  • FMOD events in the past did not take rotational velocities into consideration but now they do!
• Fix fuel temperature NaN on airplanes that don’t have wings:
  • This fixes the NaN crash on the NHadrian planes that only use misc wings and no wings 1-4.b
• Fix OpenXR Frustum Junk Data:
  • VR Frustum and Interaxial are no longer junk for the first few frames if the HMD isn’t ready to render just yet

 

40 minutes ago, Ianrivaldosmith said:

But he’s discussing the bug he found in a beta? 🤷🏻‍♂️ Who’s to say he hasn’t reported it? 

Bug in XP or the addon? It's not clear. I was only drawn to this topic because of a report.

11 minutes ago, Ray Proudfoot said:

I was only drawn to this topic because of a report.

a report that can not live with a bug report in a beta thread that begins with a list of fixed bugs. go figure.

20 minutes ago, Ray Proudfoot said:

Bug in XP or the addon? It's not clear. I was only drawn to this topic because of a report.

A report?! For what? My oh my some people have too much time on their sensitive hands!

Just now, Ianrivaldosmith said:

some people have too much time on their sensitive hands!

we know who "some people" is.

1 hour ago, Ray Proudfoot said:

I was only drawn to this topic because of a report

No need to follow up on every report perhaps 😉

Edited November 16, 20232 yr by Rimshot

13 hours ago, turbomax said:

first test:

The alert note is: value is "nan"  🤣 "Infinity or NaN (Not a number)"

I guess this was caused by an AI aircraft according to the log file. I had 15 AI active at the time of the crash, this happened after an otherwise uneventful flight, one hour into the flight:

1:14:17.684 E/ACF: Flight model error for aircraft: #9, which is path=Aircraft/AI/B737CL/Air New Zealand/B733.acf
1:14:17.684 E/SYS: MACIBM_alert: WHOA! HOLD THE PHONE! WE GOT A PROBLEM! I'LL PAUSE THE SIM NOW AND PUT THE CAMERA ON THE OFFENDING AIRPLANE!
1:14:17.684 E/SYS: MACIBM_alert: This happened in file C:/GitLab-Runner/builds/2dtum6M9/0/x-plane/design/source_code/engine/fm/fm_engines/fm_engine_jet_Nspool.cpp, line 334, function do_a_jet.
1:14:17.684 E/SYS: MACIBM_alert: The alert source is: engine_sigma
1:14:17.684 E/SYS: MACIBM_alert: The alert note is: value is nan or inf!
1:14:17.684 E/SYS: MACIBM_alert: C:\GitLab-Runner\builds\2dtum6M9\0\x-plane\design\source_code\engine\veh\definitions\veh_utils.cpp:48

-------------------------------

AI aircraft from Dazzy's AI airliner pack:

AI Airliners Traffic Pack for X-Plane 12 Version 1.0 for Windows, Max, & Linux

Requirements: X-Plane 12.05

https://forums.x-plane.org/index.php?/forums/topic/283071-uploaded-ai-traffic-pack-for-x-plane-12-beta/&

 

This package has nothing to do with JustFlight World Traffic

14 minutes ago, Dirk.M said:

This package has nothing to do with JustFlight World Traffic

Who said it did? 

Edited November 16, 20232 yr by Ianrivaldosmith

Dirk

as mentioned in my post that you quoted, this AI package crashed 12.0.8b2 which it didn't before, that's why I reported my findings, but that is as of today not allowed for some reason. I took Ianrivaldo's post as a suggestion to try something else, but I am hesitant after my previous 2 experiences. 

----------------------------------------------------------------

AI aircraft from Dazzy's AI airliner pack:

AI Airliners Traffic Pack for X-Plane 12 Version 1.0 for Windows, Max, & Linux

Requirements: X-Plane 12.05

https://forums.x-plane.org/index.php?/forums/topic/283071-uploaded-ai-traffic-pack-for-x-plane-12-beta/&

 

Edited November 16, 20232 yr by turbomax

1 hour ago, Ray Proudfoot said:

Bug in XP or the addon? It's not clear.

exactly. that's the very nature of beta testing, or so I thought, find out what plays nicely with each other and what doesn't. but as we learnt, not welcome here.

4 minutes ago, turbomax said:

exactly. that's the very nature of beta testing, or so I thought, find out what plays nicely with each other and what doesn't. but as we learnt, not welcome here.

But maybe this is not the place to report a bug. That is something you need to do with the developers, either LR, or the maintainer of the plugin causing the problem.

You can say : hey look what I found, it looks like bug, and I reported it to … . 

you can’t expect this place to be a place for bug reports, because nobody will follow up. And reactions like: it must be you , can be expected ( but I don’t approve of those, I prefer some helpful advise).