BadCompany Posted December 15, 2011 Hey, today I updated the Doom Builder 2. I opened levels of my mod - all is okay. But if I save levels, DB2 says the wad isn't accessible or used in other program. Now I checked the Game Configurations inclusive Re-Browsing. Nothing wrong I think...In second try, DB2 says same shit. I tried on "Save into...", but the result is same. Of course, there aren't active programms includes my mod, except DB2. The solution? 0 Share this post Link to post
boris Posted December 15, 2011 BadCompany said:Of course, there aren't active programms includes my mod, except DB2. What about some anti virus program? 0 Share this post Link to post
CodeImp Posted December 15, 2011 What boris said (some crap virus scanners could cause this), or any other program that hasn't closed your file properly. Might want to try a restart. 0 Share this post Link to post
BadCompany Posted December 15, 2011 The problem is solved - the DB2 afore hasn't administration rights. :) But another DB2 problem is appeared: After I starting "Testmode", this says: "File C:/Program Files (x86)/GZDoom/gzdoom.pk3 is overriding core lump mapinfo/doom2.txt." What here means??? 0 Share this post Link to post
boris Posted December 15, 2011 BadCompany said:The problem is solved - the DB2 afore hasn't administration rights. :) [...] "File C:/Program Files (x86)/ [...] DB2 doesn't need admin permissions, but normal users aren't allowed to write into the program files folder. 0 Share this post Link to post
BadCompany Posted December 18, 2011 ***stronger PUSH*** I had set all needing files out of Program Files. But DB2 says same thing as over here. "File C:/****/GZDoom/gzdoom.pk3 is overriding core lump mapinfo/doom2.txt." 0 Share this post Link to post
CodeImp Posted December 18, 2011 I don't think that is Doom Builder which says that, but the sourceport you are trying to launch. And you probably don't want to use gzdoom.pk3 when launching your sourceport, simply because it is hardcoded in the sourceport that that file is already loaded first. You still may want to use that file in DB2, so instead of removing it completely, exclude it from your testing with a sourceport: 0 Share this post Link to post
BadCompany Posted December 18, 2011 Thank you, now all things go perfectly. :-) 0 Share this post Link to post