D3D Error on Starting Mission Editor

[JimTM]

Brief description:

   

   I get the following Direct 3-D error whenever I start the BoS Mission Editor:

 

   m_pd3dDevice->Reset(&m_d3dpp)

   E_INVALIDARG

 

  The message disappears quickly. The editor does not respond and I have to cancel it.

 

Detailed description, conditions:

 

- BoS and BoS Viewer work normally

- Ran DXSETUP

- BoS updated 2015-04-28 (hotfix)

- Applied latest Windows updates to 2015-04-29

- Updated to latest ASUS GPU driver 9.18.13.4752

- Problem occurred before and after the updates listed above

 

Additional assets (videos, screenshots, logs):

 

- Uploaded RoadsLog.txt

- Could not upload .log files (e.g., packman.log)

 

Your PC config data (OS, drivers, specific software):

 

- Windows 7 Home Premium 64-Bit 6.1.7601 SP1

- CPU: Intel Core i7-3770K 3.50GHz

- Memory: 8GB

- GPU: ASUS GTX680-DC2T-2GD5

            Driver: ASUS 9.18.13.4752 (2015-02-05)

 

RoadsLog.txt

Edited April 29, 2015 by JimTM

[BradMick]

There is definitely something wrong with the D3D Implementation. Straight out of Frank Luna's book (interestingly enough seems to be everyone's foundations on DirectX) the m_pD3Dpp is an instance of of the D3DPRESENT_PARAMETERS. It's a structure that defines the IDirect3DDevice9 object the program is creating. So it includes things like, BackBufferWidth/Height/Format/Count...and a bunch of other fun stuff...so something is definitely broke. It's been happening to me in the actual main flying portion of the sim since the last updates as well. There is something not working right in the actual Code that a simple 'reset the config' isn't going to fix.

[SYN_Haashashin]

Hi Jim,

I got the same problem yesterday, will try later today and report it directly to the devs if possible.

Cheers

 

Edit: Yep, I still have it and cant open the editor at all

[JimTM]

Thanks Haash and Brad.

[LAL_Wolf]

Hi Jim,

 

I got the same problem yesterday, will try later today and report it directly to the devs if possible.

 

Cheers

 

Edit: Yep, I still have it and cant open the editor at all

The same... 

[Jupp]

~S~ Fellows,

 

Just stumbling in here. Have you to tried reloading the Sim (h8 to call it game) with a different resolution option in the Launcher?

 

This cleared an earlier issue of the D3D variety when I was changing my desktop resolutions in and out looking for the sweet spot.

 

I have been using the ME of late without this problem. But I so feel your pains as a daily user of the ME. My #1 BoS pastime of all.

 

Good Hunting!,

 

-Jupp-  

Edited May 1, 2015 by Jupp

[taleks]

Is last used mission loading at start when this error occurs?

Or it occurs even if no such setting was set in editor (Tools -> Open last used mission on start)?

[Urra]

Is last used mission loading at start when this error occurs?

Or it occurs even if no such setting was set in editor (Tools -> Open last used mission on start)?

For me this crash on start occurs even though I do not have it set for open last saved mission on start. Mine crashes completely on start using native resolution. Edited May 6, 2015 by roaming_gnome

[JimTM]

Is last used mission loading at start when this error occurs?

Or it occurs even if no such setting was set in editor (Tools -> Open last used mission on start)?

 

Error occurs without "Open last used mission on start".

 

Also, I tried Jupp's suggestion above re. resetting the BoS resolution but that didn't clear the error with the editor. Thanks anyway Jupp.

 

Thanks.

Edited May 6, 2015 by JimTM

[taleks]

Ok, thanks for report.

 

Next editor version should handle startup sequence in a bit different way.

As we can't reproduce this error, then its a bit of wild guess, but if reported error is related to unordered access to render module, then it will fix this issue.

[JimTM]

Thanks taleks. Please PM me if you need any other logs, etc.

 

Jim

[Urra]

For me it also lists other info after the e_invalidarg notice. It's show in order, "cannot create m_prtscreennormal color surface, "cannot create m_prtscreendepth color surface", cannot create m_psurfscreendepth surface".

[I/JG27_Zimmi]

Same problem here, and I somehow can't get it working again. Is the only way to reinstall the game?

[JimTM]

Same problem here, and I somehow can't get it working again. Is the only way to reinstall the game?

 

I don't know. I'll have to try a reinstall as I'm not sure when the next editor version will come out with the possible fix that taleks mentioned above.

 

Jim

Edited May 16, 2015 by JimTM

[I/JG27_Zimmi]

At least, replacing the files int the editor folder does not work

[I/JG27_Zimmi]

Even a reinstallation of the game, including a complete graphic driver reinstallation, did not fix the problem.

 

Maybe some more additional info: After the

 

  m_pd3dDevice->Reset(&m_d3dpp)

  E_INVALIDARG

 

error message I also get:

 

can not create m_prtScreenNormal color surface

can not create m_prtScreenDepth color surface

can not create m_psurfScreenDepth depth surface

[Urra]

Even a reinstallation of the game, including a complete graphic driver reinstallation, did not fix the problem.

 

Maybe some more additional info: After the

 

m_pd3dDevice->Reset(&m_d3dpp)

E_INVALIDARG

 

error message I also get:

 

can not create m_prtScreenNormal color surface

can not create m_prtScreenDepth color surface

can not create m_psurfScreenDepth depth surface

Same, I've had no luck on multiple machines...

[I/JG27_Zimmi]

I was wondering whether there is a chance to solve this issue, probably with the next version of the editor.

Thanks in advance.

[I/JG27_Zimmi]

Any news on this topic?

[Sneaksie]

It turns out these errors may be caused by incorrect data stored by the Editor in Windows Registry. You can run this batch file to delete the editor registry branch - unzip it somewhere and double-click. You can also delete the folder HKEY_CURRENT_USER\Software\1SGS in the registry manually (don't accidentally delete its parent  HKEY_CURRENT_USER\Software though).

ResetEditorSettings.zip

[JimTM]

The ResetEditorSettings file solved the problem. My BoS Editor starts up fine now. Thanks very much Sneaksie!

[Jupp]

~S~ Everyone,

 

"This bodes well for the Allies". And, o.k., the Axis as well, too!

 

Always glad to hear when anything broken is fixed. Especially this.

 

Keep 'em flying,

 

S! -Jupp  

[LAL_Wolf]

Good Thanks.

[JimTM]

roaming_gnome,

 

FYI, I tried the GUI map button with Coconut's logic test mission and it worked OK. I haven't tried any other missions yet though.

[I/JG27_Zimmi]

Thanks you very much for the fix. It's working now again.

[coconut]

 

 

However, once I load the mission and button noted by red arrow it crashes again immediately

 

Is the crash specific to this mission? Have you changed your terrain.ini? I seem to remember going too high with some settings (the number LODs, IIRC) there could cause the editor to crash.

[Urra]

Is the crash specific to this mission? Have you changed your terrain.ini? I seem to remember going too high with some settings (the number LODs, IIRC) there could cause the editor to crash.

You are right, that must be it. I gotta switch it back for it to work. Thank you.

[CCG_bexhausted]

Hello guys !

I had the same problem as everybody reports here. 

I followed Sneaksie's instructions and my mission Editor runs again.

But ...

I 'am writing a manual in french for the editor and you can see here a page of my manual showing Svetly yar. I am at the early beginning .The runway, taxiway and so on are clearly visible.

 

Before crash : Svetly yar airfield

 

 

But after crash when i loaded Stalingrad map i see that : 

 

 

Runway and taxiway vanished. Not easy to set a plane !

So i think that my database is damaged. 

 

Please how can i restore it ? If it is possible !

 

Thanks.

Bex 

 

 

[CCG_bexhausted]

Another issue with my trouble : i can load only Lapino map. On this map the runways are there. If i want to load Stalingrad or Vluki or Novosilniki the Gui map is the one  i choosed but the 3D view is always Lapino map . Strange  ?

Edited August 1, 2015 by bexhausted

[LoupVert]

Facing the same than OP here. I don't remember doing anything unusual before it happened.

 

 

ResetEditorSettings fix doesn't work, neither Steam's local file check.

 

Please help, I just can't breathe correctly without ME on.

 

PS: forgot to mention the game and stviewer still works flawlessly.

Edited September 8, 2015 by -LaFrench-LoupVert

[LFDM-Carleo]

coucou loupvert

 

il faut que tu supprimes la cle de registre suivante  Hkey_Current_User/Software/1CGS

il y a une coquille dans leur script du ResetEditorsetting

 

J'avais ouvert un post similaire il y a une semaine

http://forum.il2sturmovik.com/topic/18055-editor-mission-out-order/

Edited September 8, 2015 by Carleo

[LoupVert]

Good call Carleo, thanks a lot mate!

So the ResetEditorsetting command must be edited to : reg delete "HKCU\Software\1CGS" /f (instead of 1SGS)

 

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

 

Bien vu Carleo, merci beaucoup!
 

[Blitzen]

The reset just says Run & then opens and closes a screen faster than i can see what it is...what happened?Editor still is saying 3D3 error...help!

[JimTM]

Hi Blitzen,

 

Did you make the change given in the post above?

 

Jim

[Blitzen]

Hi Blitzen,

 

Did you make the change given in the post above?

 

Jim

Which Post...tried the reset,but I'm all thumbs with the other manual fix.Also tried Verifying files in the Steam utility- no joy.

[JimTM]

The post by LaFrench-LoupVert right above yours.

 

1. Start NotePad, click Open, and navigate to where you stored ResetEditorSettings.cmd.

2. Beside the "File name" box, select "All Files" in the drop down list.

3. Select ResetEditorSettings.cmd and click the Open button.

4. Change "1SGS" to "1CGS" and save the file.

5. Double-click the ResetEditorSettings.cmd file to reset the registry entry.

Edited November 26, 2015 by JimTM

[Blitzen]

The post by LaFrench-LoupVert right above yours.

 

1. Start NotePad, click Open, and navigate to where you stored ResetEditorSettings.cmd.

2. Beside the "File name" box, select "All Files" in the drop down list.

3. Select ResetEditorSettings.cmd and click the Open button.

4. Change "1SGS" to "1CGS" and save the file.

5. Double-click the ResetEditorSettings.cmd file to reset the registry entry.

This will probably do it-thanks! I think the 'Verify" command got the Mission Editor in the "downloaded" older version working , but no effect on the Steam one.This new solution just might!

[-NW-FourSpeed]

Facing the same than OP here. I don't remember doing anything unusual before it happened.

 

 

ResetEditorSettings fix doesn't work, neither Steam's local file check.

 

Please help, I just can't breathe correctly without ME on.

 

PS: forgot to mention the game and stviewer still works flawlessly.

 

Same issue here... Yesterday, it was hunky-dory, today the ME is a paperweight...

 

I'll try the Regedit fix in a bit to see if that resolves it...

 

 

Regards,

4 

[-NW-FourSpeed]

Hmmm... can't edit my prior post anymore...  

 

The ResetEditorSettings fix didn't fully resolve the issue (it did prune the  "1SGS" registry branch).  

In my case, I also had to prune the "1CGS" branch as well  (I simply renamed it).

 

At that point, the Mission Editor did start up successfully.

 

 

Regards,

4 

 

 

PS> If it's of interest, my Editor & Test Server is on an (older) XP box - perhaps that has some bearing on which registry keys are created etc... In any case, it's resolved for now (Thanks!), and hopefully, the devs are aware enough now of the actual causes to fix it in a future patch...

[6BLBird-Dog]

Hi,Great these forum pages ,just edited the registry and solved the same problem . Many Thanks