ZDoom

Glad to know this is fixed! Thanks!

I'm using subsilver2 and the colour difference is really obvious, and it's still *fairly* clear for me when I go into prosilver brown (but I can definitely see how certain lighting and contrast combinations would make them indistinguishable), but going into prosilver blue I can barely notice any difference if I didn't already know the link was there. Is it possible to set the forum so that the http:// is visible on all links of that kind?

Here's a link to the last time I brought up cameratextures on the HUD in software (I'm just copypasting the URL): https://forum.zdoom.org/viewtopic.php?f=2&t=62012

Okay I pushed a fix for this to master.

I also made the software renderer not crash, but it will still appear black on the HUD there. Reason being that there's currently no way for the software renderer to feed the canvas pixels back to the 2D drawer.

[quote="Rachael"]What style are you using? They appear just fine, for me.[/quote]
Using the zdoom brown default or whatever color it is. I suppose technically there is a color difference but its so subtle I didn't notice it.

What style are you using? They appear just fine, for me.

Ah so there was a link there - great css with nothing to indicate that :)

There's one linked in the OP, though it has ZIP as the extension instead of PK3.

Anyone have a pk3 which demonstrates the issue?

[quote="phantombeta"]Just tested, turning on shadowmaps stops the camtexes from updating.[/quote]Confirmed that's the case for me too!

Once I turn off that option in f10ded7 they work fine.

Just tested, turning on shadowmaps stops the camtexes from updating.

Well, this can be caused by a particular option or their combination. Could you please try with default settings?

I tested the attached file and the camera textures are also black for me using OpenGL.

Windows 10, NVidia GeForce 1080 GTX, driver version 417.35

For what it's worth, I'm using a EVGA Geforce 400-something with the nonfree nVidia drivers.

Is this considered too old for GZDoom now?


(then again I'm not having this problem on my Windows machine which uses an integrated Intel graphics thing and inferior specs in pretty much every other respect, so....)

Been using:
1. Your sample without -noautoload
2. HD with -noautoload

Just tried 7b16433 now with your sample with -noautoload. All cameratextures black.

Now looking for the most recent commit that doesn't do this. [s]8da1b5c is okay so far.
EDIT: 4f4d10c is also good. This seems to have started in one of the Jan 4 commits.
EDIT: It's either 980977d or the one right before it...[/s]

EDIT: Confirmed it is [url=https://github.com/coelckers/gzdoom/commit/f10ded756e6e47ccd225e105a5c24c00ef51ca9f]f10ded7[/url] where the bug first appears.


(The software crash happens on 4f4d10c and 3.7.1 as well, so I think we can pretty safely say it's unrelated.)


EDIT: this bug doesn't seem to happen at all on my Win7 machine running the 32-bit devbuild (gzdoom-g3.8pre-148-g32cf79c51). Can't test 64-bit.


EDIT: did a dist-upgrade and restarted my computer. Still got the black camtexes.

Are you using other custom mods or maps except my sample? I tested on Doom II MAP01 with the sample only.

I also get the crash, and in GL it's black for the entire session.

Crash might be related to [url=https://forum.zdoom.org/viewtopic.php?f=2&t=62012&hilit=cameratexture+software]this[/url] though.

Is it black with OpenGL renderer? If so, for me it's only black for the first tick.
However, it crashes with any software render mode. Most likely it's not related to this report.