Actinide

Installed the 64 bit version, it no longer crashes. I guess I'm just dumb and somehow didn't notice I had the 32 bit executable... Well, problem solved I guess.

It turns out I am, and for some reason I didn't notice it until now. I'll reinstall it, 64 bit version, see how it goes.

I'll check later today when I have access to my computer, but as far as I remember, I should've downloaded the 64 bit version...

That's the thing. I should have more than enough memory to deal with it... over 80 GB free on my SSD, at least 3 to 4 GB of ram still available even with UDB open, and I'll be damned if my RTX card can't load some PNG previews that don't even amount to 1 GB total...

Tried that, it appeared to work... for like 10 seconds.

So recently, I've downloaded a texture pack that I thought would be useful for my maps, FoxTex, volumes 1 and 2. I was surprised at the sheer size of the texture pack, lots of great looking textures from what I checked on SLADE. I decided to pop the two .PK3s into one of my test WAD's resources in Ultimate Doom Builder, so I can try it out on an actual map. One problem though. Whenever I try to actually replace any linedef textures with one from FoxTex in Visual Mode, UDB first struggles to load the textures in the selection popup, and even if it does, it quickly displays several fatal errors and forces me to close it. I couldn't pin down the exact cause of the errors due to... apparently no one posting anything similar in the forums, as well as there being multiple types of fatal errors I've already come across. Sometimes it's a default Windows Error pop-up, sometimes it's an UDB Error pop-up, hell, sometimes the program just crashes without warning when I do so much as try to check out a texture from either PK3s! It only seems to happen with FoxTex, as far as I can tell, and I have no clue of what's causing it. My computer should be more than capable of dealing with this task. I've got an RTX 3050 mobile GPU with 4 GBs of VRAM, an AMD Ryzen 5600H CPU, and 16 GB of RAM. Despite what the error screens below might indicate, the system did not exceed its memory budget, as I've checked Task Manager several times during these crashes, and not once RAM or VRAM was a problem. Here are some of the error messages from UDB and Windows: Memória insuficiente. (Insufficient memory) em System.Drawing.Graphics.CheckErrorStatus(Int32 status) em System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height) em System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height) em System.Drawing.Bitmap..ctor(Image original) em CodeImp.DoomBuilder.Data.ImageData.MakeUncorrectedImage(LocalLoadResult loadResult) em CodeImp.DoomBuilder.Data.ImageData.LoadImage(Boolean notify) em CodeImp.DoomBuilder.Data.DataManager.BackgroundLoad() em System.Threading.ThreadHelper.ThreadStart_Context(Object state) em System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) em System.Threading.ThreadHelper.ThreadStart()

As in, map format? Texture format? I'm mapping on UDMF, with Ultimate Doom Builder All I did was load the two PK3s into the resource list. The textures are the original PNGs, they have not been tampered with. My computer should be able to load both packs. I have more than enough room in my SSD, and more than enough RAM to run UDB.

Uhhh... I have no clue what's causing this. Happens whenever I try to open FoxTex Volume 2 specifically. Downloaded it just today. UDB is up to date... Help?

Currently making a set of mugshots for personal use. The start of my Doom spriting efforts. Had the brilliant idea to just work on it like regular, low res digital art and convert the final result to the Doom palette. I'm not sure it's going that smoothly though. It might need more than just a couple of touch ups... Working on getting it to be compatible with Smooth Doom, since I regularly use that for casual gameplay as well, and it has quite a bit of extra mugshot frames.

Pics taken with my phone can easily get doodoo, and coloring with markers is a pain. Here's a thingy with a character of mine in a blocky-looking marine outfit.