D3D error (Originally posted by Cocoabean)

[TG-55Panthercules]

This thread was copied from the old RoF forums:

 

Originally posted by Cocoabean:

 

I am able to play the game for a few minutes before my game freezes but I can still hear the game audio. When I tab out there is no error until I try to tab back in to Rise of Flight. That's when I get that error. I have a monitor with a resolution of 1920x1080 so I don't see why any resolution I choose in game that is lower than that would be the reason for the crash. I just need help knowing what the error means.

 

 

 

 

Edited July 1, 2023 by TG-55Panthercules

[baldeagle611]

I'm getting something similar: I re-installed RoF after a long absence. Firstly it takes a long time to start. Then when I try selecting a quick mission to test it, it tells me I don't have the plane (I thought I had purchased nearly all of them), then it freezes up with the error below.

 

[TG-55Panthercules]

If you haven't done so already (and maybe even if you have), be sure to try doing an update to the game before you try to play it.  (Also be sure you have both the 2005 and 2008 versions of the MS distributable).  That seems to have done the trick for most folks suffering this sort of error upon startup.  

 

Also, what version of the game did you install after all this time?  If it was some sort of older (especially disk-based) copy, that's almost certainly part of the problem.  Best bet is to D/L and install the latest free-2-play copy from the RoF store/website (or from my alternate links posted on the Useful Materials page on this subforum) and then update from there.

 

If all else fails, you can try submitting a ticket to the support team.

 

Good luck!  Let us know how it works out.

 

Edited July 31, 2023 by TG-55Panthercules

[testid]

Re-engaging with my sim rig.

Still on Win10. Initial attempt to launch RoF using ROF.exe succeeded but launched to 2 screens instead of to all 3 (I fly triple-wide). Login worked. Quit running game to troubleshoot display settings.

I looked at my startup.cfg and it matched my backed-up version. I relaunched using ROF.exe again and instead of running, a Direct3D error came up:

 

"D3D_ERROR
Cannot create Direct3dDevice

D3DERR_INVALIDCALL"

I followed these instructions to reinstall the D3D stuff from the ROF installer bundle:

https://steamcommunity.com/app/244050/discussions/0/4415298919341493993/?l=czech#c6895657216186702454

Reboot, relaunch, nope. Tried the Updater, rof_updater.exe, no updat available (duh), used "Start game" button: D3D error.

Reboot, try Updater method again but this time click "Recovery". Updater examines install for checksum issues, none found, click "Start Game". Game launches successfully!

A bit more fiddling. Changing the resolution definition lines in startup.cfg to 

    full_height = 1080
    full_width = 5760

    fullscreen = 0

 

and

 

    win_height = 1080
    win_width = 5760
 

with 

    desktop_center = 1

Produces a launched game but with only output to the left and center screens. The leftmost screen is treated as the location of most of the UI elements with the settings and quit icons on the center screen at the rightmost lower edge.

Changing the desktop line to

 

    desktop_center = 0

 

Produces a successfully launched game with all three screens active as desired, primary UI elements centered in the middle screen.

Anyway, this worked for me. I'm aiming to refiddle my sim rig for RoF, FC, and the recent MSFS to all run with similar control settings and a simplified set of USB devices. Last time I took a whack at this I ground-looped on a bizarre control mapping issue in which settings for controls in MSFS and RoF would deny the other program the inputs and occasionally invert them (as in the axes on the stick), which makes no sense whatsoever and which I did not bear down on to resolve, so my impression of the issue may certainly be incorrect. 

UPDATE

After launch and heading to Options > Video > Screen and checking the "Full screen" option, invoking a game restart, the D3D error recurred. on changing the startup.cfg option "fullscreen = 1" to "fullscreen = 0", the game launched successfully. 


 

Edited October 10, 2024 by testid