Jump to content

Recommended Posts

Posted

I'm experiencing a consistent crash when loading the RSG G500 1.3.0 plugin in the Beechcraft Baron 58 EFM under X-Plane 12. I purchased the G500 through X-Aviation and it works correctly in the included Cessna 172SP G500 aircraft, but crashes every time when installed into the Baron 58 EFM.

System:
- iMac Pro, Intel x86_64
- macOS (Metal/OpenGL bridge)
- X-Plane 12.04+
- OpenGL 2.1 ATI-7.0.24, AMD Radeon Pro Vega 56

Crash details:
The plugin initializes, registers all commands, loads all nav data, airspace, airways, and cities successfully, then crashes during the deferred initialization phase at the following location:
 

    g500.cpp:229 — Init Paged Parser


The last successful log lines before the crash are:
 

    G500[g500.cpp:152]: Deferred Init
    G500[g500.cpp:229]: Init Paged Parser
    <crash>


In the working C172, the sequence continues past Init Paged Parser to:
 

    G500[g500.cpp:232]: Init airportList
    G500[g500.cpp:235]: Init fplDrawer
    G500[g500.cpp:238]: Init airportDrawer
    G500[g500.cpp:241]: Init Traffic
    G500[g500.cpp:246]: Deferred Init Complete


Additional observations:
- The crash occurs regardless of g500.cfg contents (zeros, C172 values, custom values)
- The crash occurs with all other aircraft plugins disabled (xlua, rdr2000, OpenGPWS all tested)
- A fresh copy of the plugin folder with cache cleared produces the same crash
- The plugin binary is identical between the working C172 install and the crashing Baron install (same file size, same build date: Nov 1 2024)
- The Baron cockpit OBJ uses GLOBAL_cockpit_lit / GLOBAL_luminance 2500; the C172 uses BLEND_GLASS — this may be relevant to how Init Paged Parser locates the panel texture

My goal is to embed the G500 in the Baron's 3D panel by modifying the cockpit OBJ, similar to how it is implemented in the C172. I am happy to provide full Log.txt files if helpful.

Thank you for your assistance.
 

Posted

1.3.1 fixed the crash completely, the plugin fully initializes and the popup works with real instruments. I'm now hoping you can clarify how panel rendering is supposed to work.

What I'm Trying to Do

I want the G500 screens to render on the 3D virtual cockpit panel texture, not just in the popup window. The Baron has a 2048x2048 panel texture (Baron_58_cockpit.png).

What I've Tried

g500.cfg render coordinates — I've set these based on scaling from the XP11 Baron donor (which used a 4096x4096 texture) down to XP12's 2048x2048:

render_pfd_x = 25
render_pfd_y = 660
render_pfd_w = 256
render_pfd_h = 384
render_mfd_x = 300
render_mfd_y = 660
render_mfd_w = 256
render_mfd_h = 384

ATTR_cockpit geometry — I added screen-shaped quads to the cockpit OBJ at the correct 3D positions (derived from the XP11 donor clickspot geometry at Z=2.538971), with UV coordinates mapped to the render regions above, wrapped in ATTR_cockpit. No OBJ errors in the log, but the screens don't appear — just the original 6-pack gauges.

devices_screen.obj — The Baron has a separate devices screen OBJ using ATTR_cockpit_device. It had an invalid parameter that caused XP12 to log "device directive that is not any of X-Plane's glass cockpit devices." I fixed the parameter — warning is gone — but screens still not rendering.

My Core Question

Does the RSG G500 actually support panel texture rendering in XP12, or is it popup-only?

Specifically:

  1. Do the render_pfd_x/y and render_mfd_x/y values in g500.cfg control panel texture rendering, or do they control something else (popup position/size)?
  2. If panel texture rendering is supported, what does the cockpit OBJ setup need to look like?
  3. Is there a specific ATTR_cockpit_device device name the RSG G500 registers that should be used in the OBJ?
  4. Is there a cfg setting to enable panel rendering mode vs popup-only mode?

System Info

  • iMac Pro, Intel x86_64, macOS
  • X-Plane 12.04+
  • RSG G500 v1.3.1 (Apr 16 2026)
  • Baron 58 EFM 520 (XPlane2Blender 4.3.4, Blender 4.2.0)
  • OpenGL via Metal bridge (AMD Radeon Pro Vega 56)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

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