Falcon 4 BMS 4.34u2 crashes when loading 3D world (Acces violation @creation of OffScreen texture or RTT object)

[XenoPL]

Falcon 4 BMS 4.34 mod ran under wine-nine crashes during mission load screen.

There are two variants of crash message:

Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 000000000455F3A9 Falcon BMS.exe, ImageBuffer::SetupAsOffScreenPlain()+377 byte(s) Exception handler called in UnhandledExceptionHandler. Write to location 0000000000000003 caused an access violation. Bytes at CS:RIP: C7 04 25 03 00 00 00 03 00 00 00 4C 8D 9C 24 90

or:

Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 0000000004560D6D Falcon BMS.exe, RTTImageBuffer::SetupAsRTT()+333 byte(s) Exception handler called in UnhandledExceptionHandler. Write to location 0000000000000003 caused an access violation. Bytes at CS:RIP: C7 04 25 03 00 00 00 03 00 00 00 C7 47 08 06 00

Console output of the session:
BMS.log

Crash screenshot:

System specs:
Hardware: CPU: Intel Core2Duo E8500 @3.16GHz (stock) , m.b: GA-P35-DSR3, RAM: 8GB 1333MHz DDR3, GFX: RadeonHD 6870 1GB VRAM.
OS: Fedora 31 64bit, kernel 5.5.6, libdrm 2.4.100-1, mesa 19.2.8-1, DE/Windowanager Plasma/kwin_x11 5.17.5,Wine: wine 5.2-1, wine-nine 0.5.

Wine config: clean Windows 7 64-bit prefix, wine-nine enabled via nine GUI app,
gfx tab:

• allow window decorations
• allow window manager manage windows
• enable virtual desktop 1920x1200 (max res of my display)
  Stagging tab:
• enable CSMT
• Enable EAX
  Wine windows are forced to run fullscreen.

Steps to reproduce:

• Launch BMS
• Select Tactical Engagement/training (crash also occures wih other game types, i've tried Dogfight and Instant Action)
• From the list of missions pick TR_BMS_02_Navigation then commit
• Click TakeOff button
• Crash occures when progress bar is somwhere between 60-80%

With wine-nine disabled mission loads just fine.
Funny thing training mission 13 works with wine-nine enabled.
I've askefd a guy from a BMS project for some hints but he couldn't tel much:

Sorry but I don't have much clue here. This is a simple texture handling function that is being called when the code requires to create a "Off screen" rendering. E.g a 3D cockpit RTT target. I don't know why it's failing but seem to me like some obvious API issues that somehow prevent such a off-screen render target to be created. Hard to tell without any more info or reproducing such issue locally (Which obviously cannot be done).

[dhewg]

Could be another case of process runs out of address space.
And it's been a while, any progress on your end?

[axeldavy]

Possibly fixed by iXit/Mesa-3D@84c3b6e

[dhewg]

Is this fixed now when using mesa v21.1.0-rc1 or later?