Code: Select all
while(!detect_hack())
{
message("Plug the VSync cable ...");
if(key_pressed())
{
calibrate();
break;
}
}
if key press occurs - do calibration and continue with out the hack .
Code: Select all
while(!detect_hack())
{
message("Plug the VSync cable ...");
if(key_pressed())
{
calibrate();
break;
}
}
As I suggested in my mail earlier today, If you already have a working IRQ code that does not get out of sync over time, then you do not need to use the VSync hack at all during the game: Just keep your IRQ, same code path, much simpler.Chema wrote:The second question, when am I going to detect it? I think the user needs time to plug the Vsync cable after loading the game, so I guess I need to print a message such as "Plug the VSync cable if you have one and press a key". Then, after the keypress, perform the detection. If no Vsync is detected, jump to the calibration screen, else skip it.
I cannot think of a more automatic (or transparent) way, and it will be a bit of an inconvenience to the average user. Any ideas?
This looks just amazing, on tv with pal blending must look great.Chema wrote:In the process of adding suggestions from alpha testers
Still under construction, but it is nearly there. Don't hesitate to contact me with suggestions/bugs/glitches... whatever.
Ho and with a pseudo composite cable, both colour are nearly the same, I tried to show Oricium on a video projector that didn't loved the RGB output of the Oric, use the pseudo-composite cable I have (but making only grayscale level) I was unable to differentiate the Red and the Green. The contrast is too similar in this case. So if it could be one color with 1 bit (Red,green or blue) and one color with two bits (cyan, magenta or yellow) it would be better I think.Dbug wrote:Chema wrote:Now, for a purely human point of view, I would be happy if you replaced the RED/GREEN by something else like BLUE/CYAN or WHITE/BLACK or BLACK/YELLOW, because RED and GREEN together tend to bleed horribly on many screens
NiceChema wrote:In the process of adding suggestions from alpha testers
Isn't it?Dbug wrote:NiceChema wrote:In the process of adding suggestions from alpha testers
I did not notice at all that Chema was first and Dbug last in the list