Recent content by KennyPowers

Bloop is less than 5 minutes from our house (I could walk there), and we've been helping him out when we're able. He has a large collection of stuff and a LARGE building that's gradually being built-out to display it all. You should definitely come check it out, and maybe come geek out at our...

I re-did 5 of those MO drives recently...they are certainly a pain. At least you can separately verify that the motor board is working and properly regulating RPMs before reassembly using a bench power supply. Still, I won't be upset if I never work on one of those again :LOL: It should be...

I'll be there for the 4th year in a row :)

That appears to be an unoptimized debug build with the console window enabled...I built a release build from the latest source though :) It looks like all that was needed all along was to apply gamma correction and variable white/black points to the color rendering path (and therefore the...

I would first try getting rid of the dedicated "Xceed/Bolle" option (go back to the 1.1.0 code), and then applying the gamma correction to the color palette. Then just let QuickDraw take care of the grayscale conversion. Color output could probably benefit from gamma correction too.

I already did that. It looked basically the same as with the Xceed/Bolle option disabled. I was just going to do it in-game with a hard-coded gamma correction value, and then maybe you could add a user option to allow changing that gamma correction value if it worked. The best solution would...

It seems pretty clear to me why calculating luminance and then only applying it to the blue channel while zeroing the red and green channels made everything basically black. The QuickDraw documentation says this: Clearly QuickDraw is doing color->grayscale conversion when the screen is set to...

I did some more testing of the 1.1.0 build on an '040 IIci with a Radius Thunder 24/GT video card (again running System 7.1), and was able to reproduce the artifacting in the status bar that we're seeing on the grayscale SE/30: So, maybe that further supports the idea that the darkness...

Ok, video of that build (temporarily maxed CRT brightness about 40 seconds in): As you can see, it's much darker than before...about what you'd expect if two of the three color channels were set to zero: I then altered the code shown above to set the red and green channels to the same...

I was about to cross-post this in the long-running Daydream thread on nextcomputers.org when I saw you've already been discussing this kit there recently...very cool. I feel called out :LOL:

This is basically the same thing Bolle told me (I wanted that increased vertical resolution his card offered, but I digress :)). So, MacDoom *could* convert its color palettes to grayscale palettes when loading them from the WAD, and then it wouldn't matter that Micron-derived cards only use...

I have been...all of the videos I've shown are with the system set to 256 grays. 256 "color" mode actually looks worse. I DMed you on discord with part of a convo I had with Bolle about how his card (and the original SE/30 grayscale cards) works.

It trying to display color instead of grays might explain why the game content is so dark too. I also run Wolfenstein 3D on this machine, and that game actually switches the mode to 256 colors (have to switch it back in the monitors CP after closing the game). Wolf3D also appears a bit dark in...

@MacOfAllTrades So I misspoke earlier when I said the border was black for me. It's light gray, even with the CRT brightness at a reasonable level. Here's a video of a complete run at default settings with the system set to 256 grays and the CRT brightness slightly higher than where I usually...

Could have something to do with those. I also see that 7.5 is listed as the minimum OS version, and like I said in my previous post, I'm running 7.1. Until I cranked the CRT brightness, the game content and the border were all very, very dark...too dark to see much of anything. Other...