Details for the next generation of Flickerfixers from Individual Computers

[Retrofan]

Originally Posted by BarryB

Tried FBlit & FText but they seem to cause graphic corruption, any other ways to save chip ram?

CyberBugFix. It's already used with ClassicWB39 and AmiKit for Real.

[BarryB]

Originally Posted by Art

They should have released A1200 with 4MB of Chip RAM just like Atari Falcon.
That would be something! Amiga 1200 with 4MB of CHIP RAM

Originally Posted by Retrofan

CyberBugFix. It's already used with ClassicWB39 and AmiKit for Real.

Think I've sorted it!

Prefs/Workbench > Images in Graphics Memory
FBlit
WBCtrl IMT=ICONFAST
FText
LoadWB SIMPLEGELS.

Seems to be corruption free so far, however, my PAL non Laced screens that used to be fine are now stretched 2x vertically but only showing the top half? I thought these modes were independant in the Indi MKII? What are the chances of a 4mb Chip Ram upgrade kit?

[Retrofan]

Absolutely none. How many colors are you using?
Well, really I think it doesn't matter. I woudn't use more than 1024x768 (perfect size) without rtg. Xtreme for example eats too much chip ram, no matter what you do.

[BarryB]

I'm using 64 colours, was 256 but not interested in an Eye Candy Workbench just one that works quickest. Using HIGHGFX again and going to stick with this for now.

Next problem is DBLPAL, Audiomaster IV seems to use this according to the Indi OSD but can I as HELL get this mode to display, let alone fullscreen, anyone have DBLPAL working?

[lolof]

I am also waiting the test button to start to play with the config tool....

[demolition]

Originally Posted by lolof

I am also waiting the test button to start to play with the config tool....

Use some program on another screen like PPaint in your desired screen mode like previously suggested here. Then you can switch back and forth between resolutions by clicking in the upper right hand corner. It works almost as good as a test button would.

[Retrofan]

Originally Posted by demolition

Use some program on another screen like PPaint in your desired screen mode like previously suggested here. Then you can switch back and forth between resolutions by clicking in the upper right hand corner. It works almost as good as a test button would.

If what he wants is to center the Games display then he would like to read this post too (I understand that here PPaint or Sysinfo has the same result):

Originally Posted by bbond007

There are a number of factors that will affect the centering.

Sysinfo is a WB program so it is affected by WB overscan prefs. Most games don't observe WB prefs because they don't load WB and have their own bootloader.

Not all games run centered (tend to run to the right) because if they did they would loose use of a sprite or 2... I'm sure someone could offer a more technical explanation at the hardware level, but I have experienced it in a program I wrote, so I do know the limitation exists.

if you go through the games and are happy with the centering, and then set WB app centering inside overscan prefs last.

[keropi]

Personally I still don't really get how the MK2 works with the config tool. It seems that the behavior is not constant.
btw, I did a complete re-flash and re-installation so everything went back to stock before doing those tests.

Jens stated previously that one can configure the MK2 to output an amiga resolution within a user resolution: for example PAL 640x400 in a 800x600 screen with black borders all around. If you choose a 1280x1024 resolution then the borders are bigger.

Now I don't get this:

take for example these settings as they show on a TV - 664x534 amiga resolution , fullscreen and nice




and this is how it shows on a 1280x1024 MK2 screen:



why is it "zoomed" ? shouldn't the 664x534 amiga resolution be a centered area in the larger resolution with back borders?


and here is MK2 1024x768 (changing the "width" value to 1024 makes no difference at all , I just left it as the tool pre-configures it)




and here is MK2 800x600 , terrible





In all cases the image gets cropped at the bottom, right and on the 1024 case it also crops at the left... 800x600 is the worst of all
So it appears that it just centers a 1:1 screen at some cases while exploding in some others? Shouldn't the amiga 664x534 look fine in anything 800x600 and above?
I don't get it.

[johnim]

hi keropi look at my pics 2 and 4 post 2025 notice the unticked button on screen prefs and set to 512

and set to that for pal high res laced

you my need to adjust h-offset to your monitor

dont forget to press enter when changing options

[keropi]

didn't help johnim ... checking/unchecking or setting to 512 the height on sceenmode prefs did nothing.
I also tried playing with h-offset so I could center the screen, with offset set to 0 the screen starts at the center of the panel... if you put 50 then it moves to the far-left ... I can't seem to get it centered correctly, it either crops or leaves a huge border (then crops on the right side)

edit: there must be something wrong with the mk2 settings for PAL , HighGFX 1024x768 is centering and displaying perfect on the same 1024x768 MK2 setting

[Schoenfeld]

Originally Posted by keropi

why is it "zoomed" ? shouldn't the 664x534 amiga resolution be a centered area in the larger resolution with back borders?

The actual Amiga resolution is Hires, but you have set the configtool to S-Hires. This will put not 664, but 1328 pixels into the Indivision framebuffer. However, you tell Indivision to only display 1280 pixels. The picture is therefore cut at the right side.

Originally Posted by keropi

and here is MK2 1024x768 (changing the "width" value to 1024 makes no difference at all , I just left it as the tool pre-configures it)

Same cause, worse outcome, because your framebuffer gets filled with S-Hires pixels.

Originally Posted by keropi

and here is MK2 800x600 , terrible

Same cause, even worse outcome, because your framebuffer gets filled with S-Hires pixels - every Hires pixel gets written twice if you set "S-Hires" in the configtool. Indivision is doing exactly what you're telling it to do!

Jens

[johnim]

hi jens so why does my screen work see post 2025

[demolition]

Originally Posted by johnim

hi jens so why does my screen work see post 2025

Because you're using other overscan settings? Yours is 640 wide, so no overscan, so it fits perfectly with 1280x1024 in shires mode.

[keropi]

Originally Posted by Schoenfeld

The actual Amiga resolution is Hires, but you have set the configtool to S-Hires. This will put not 664, but 1328 pixels into the Indivision framebuffer. However, you tell Indivision to only display 1280 pixels. The picture is therefore cut at the right side.

thanks for the explanation, but still after switching to "Hires" I get this on a 1024x768/60hz screen:





I have set the width to 664 and for some reason height was 572
If I put height=534 (the actual native resolution is 664x534) then the screen does not receive a usable image.

If I put height=535 then I get this , with the image shifting to the right (still missing from left and lots from bottom)




the same resolution set to 800x600/60hz with Hires setting produces no usable signal for the monitor. S-Hires just gives the zoom deal. 1280x1024 is pretty much the same deal , problematic for me.

Please tell me what else is wrong or what I can do to help pinpoint the problem

[Schoenfeld]

Originally Posted by keropi

thanks for the explanation, but still after switching to "Hires" I get this on a 1024x768/60hz screen:

You set the width to 512, so Indivision must put 256 pixels left and 256 pixels on the right in order to get the 1024 pixels "left to right" that the output screenmode is supposed to have.

Further, you have switched line doubling to "on" with every other line at 75% brightness. However, you already have an interlace screen that puts over 530 lines into the framebuffer. After line doubling, this is 1060 lines. Naturally, this does not fit on a 768-line screen, so it's cropped at the bottom. Switch off line doubling for interlace, and you'll see the rest of the screen.

Originally Posted by keropi

I have set the width to 664 and for some reason height was 572
If I put height=534 (the actual native resolution is 664x534) then the screen does not receive a usable image.

If I put height=535 then I get this , with the image shifting to the right (still missing from left and lots from bottom)

You are missing lots of pixels on the left, because your output window has an offset set to 68. This means: The left 68 pixels are put in memory, but they are not displayed.

This - in combination with other settings - is causing "not usable display", because you are already in a tight corner setting here: If the output stage of Indivision AGA MK2 finds that the line in memory has ended, then it ends the actual output line in order not to display any memory-crap (people complained about this before). This will cause the output frequency to be higher than calculated, and it may exceed the capability of your monitor.

Let's do some calculation:
there are 664 pixels in the line buffer. You skip 68 of them, so 594 pixels remain to be displayed. You still tell the flixerfixer to display 664, but this amount it just not available in the framebuffer (there's nothing to display at the end of the line!). It may actually be an FPGA core bug that the right black border is not displayed in that case, causing even shorter lines and even more critical frequencies. I'll investigate that.

Jens

[keropi]

^ thanks for the info , I will try to make some usable screenmode with the new info you gave
please keep in mind that the only setting "I made" was the lines 75% so I have scanlines, all others (H-offset=68 , S-Hires, etc) were what the config tool had by default when I select the resolution I decided...
maybe it can be hardcoded so that you don't get unusable settings by default in resolutions that won't work? I am pretty sure it will save others from frustrating too

I will report back on the evening , hopefully I will get it working this time

[keropi]

awesome!
thanks to the valuable explanations I was finally able to setup a proper screenmode:



I had to mess with the H/V=offset values with a "hit and miss" strategy so I could get the whole screen non-cropped , if both are 0 then you get cropping. (I also noticed the screen is not centered, it is full but not centered - has more black space on the left , I would say it has the double blank space on the left... vertically seems centered though , still I think I am missing a couple of pixels - they eother get cropped on the left or the right, I can't find a value to actually center perfectly)
The picture is great and well worth the effort
Now all I need is some "v-synced" mode so that gaming is a delight

[Schoenfeld]

New tool with test button, core with a few bug fixes:

http://icomp.de/products/AGAmk2/MK2_CFG_V10.LHA

too tired for today to make this a news item. A few hints on what's new in the readme. Lots of new pixel clocks bloated the archive...

Jens

[BarryB]

Thanks Jens, and also thanks to whoever is helping Jens with the Config Tool.

[NovaCoder]

Thanks Jens, great job!