Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
BadCompany

Doom Builder 2 make nuts...

Recommended Posts

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?

Share this post


Link to post
BadCompany said:

Of course, there aren't active programms includes my mod, except DB2.

What about some anti virus program?

Share this post


Link to post

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.

Share this post


Link to post

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???

Share this post


Link to post
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.

Share this post


Link to post

***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."

Share this post


Link to post

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:

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
×