InsideQC Forums

I didn't play through it all (shame on me!), but it was working fine.

How about some volumetric fog first?

I thought qbism supported protocol 666? I can play big maps, but not demos with protocol 666, it seems. hm.

It seems to be working now.

Probably some old software that used to run on NeXT that no one has anymore.

What's the point of checking what version of the os is running? Wouldn't it be more useful to check drivers and whatnot?

goto in hud scripting language? :p

Just hard code it.

Qbism supports coloured lighting, doesn't it? I have a map i made that uses coloured lights and they weren't showimg in game. I used mh's new arglight with colour support. i can post the map later.

I thought about that, but then I thought about to actually do it.

How would you do it? 70 pipes for each file? sed -f file.sed file(s). file.sed contains multiple lines of search and replace regex commands, which will be iterated through on the file.

The file given to -f doesn't need the suffix ...

Try sed.

Have you had any time to look at that resolution bug? Even with the new version, the screen becomes skewed, like before.

CleanQC 1.06 isn't really that clean. I went through it and there are still a fair amount of unused variables, some unused functions, &c.

1366x768 is the native resolution of the monitor (laptop display). It' fairly common among laptops with 15.6" displays, I know I've seen at least four other brands with that as the native resolution.

edit: engine just crashed after getting the SSG in VeniVidiFutzi. No idea why.

Ok, I updated to the newest version and that does fix things. My monitor's native resolution is 1366 x 768, which is butchered in qbism, see here for what I'm talking about. I also noticed some messed up textures in e1m1, here is an example.

ps: qbism reverts to 640x480 when trying to run marcher ...