Posted 30 May 2016 - 07:13 PM
I'm running BFME2 on a virtual drive, when booting up WorldBuilder I'm getting this error:
This thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Access address 0x00000014 was written to.
================================================================================
EXCEPTION_ACCESS_VIOLATION:
Spoiler
Any help would be greatly appreciated! 
-Before
Edited by Before, 30 May 2016 - 07:13 PM.
File hoarder
Posted 30 May 2016 - 07:36 PM
Administrator of CNCNZ.com and EVA Database, the C&C Wiki
You are also welcome to make use of my archives of official files:
Splitting Hares
Posted 30 May 2016 - 08:06 PM
Even in 1.06, you'll likely still see that error message a lot, but not on immediate boot. Saving your work often crashes WB as well, so make sure you always know where your auto saves are going.
Posted 30 May 2016 - 08:15 PM
Even in 1.06, you'll likely still see that error message a lot, but not on immediate boot. Saving your work often crashes WB as well, so make sure you always know where your auto saves are going.
If you're using version 1.08, switch to 1.06. 1.08 breaks the Worldbuilder.
Thanks for the help but I'm pretty sure we're all better without me http://prntscr.com/bac97t
File hoarder
Posted 30 May 2016 - 08:17 PM
That shouldn't happen if there's no erroneous modded data in the BFME2 directory. Worldbuilder can detect even the smaller coding errors that do not disturb the game itself. Learned that with the Zero Hour Worldbuilder off which it is based (if not almost the same).Even in 1.06, you'll likely still see that error message a lot, but not on immediate boot. Saving your work often crashes WB as well, so make sure you always know where your auto saves are going.
Edited by Plokite_Wolf, 30 May 2016 - 08:17 PM.
Administrator of CNCNZ.com and EVA Database, the C&C Wiki
You are also welcome to make use of my archives of official files:
Splitting Hares
Posted 30 May 2016 - 09:09 PM
That's why it's usually an issue with maps that have lots of stuff. WB can't handle rendering a handful of textures and objects together, and sometimes just moving around a large, heavily textured map is enough to crash it. On my last map, I had to very slowly place textures near the final stages to avoid constant crashes with that exact error message Before posted, and it's even something mappers have dealt with since the game's release. It's not too bothersome if you're making smaller maps, but it still persists on occasion then.
Posted 16 March 2020 - 04:31 AM
Coming late to the party, but I'm having the exact same issue 
How was this solved? The one I'm getting is:
0 members, 1 guests, 0 anonymous users
