FS-UAE 1.1 Development Series

[Foul]

Originally Posted by Foul

will test some demos and give you 3-4 names

thx

Krest Mass Leftovers by Anarchy Music boosted @ start



Virtual World by TomSoft 3D is Fast and for exemple the first screen must wait a bit but scroll and skip directly to the next effect :




Vector-Balls Demo by TomSoft Little "T" too speed and all vector balls too fast too



s by skarla No time to see the first screen (Presented...)



Megademo by Red Sector Inc. Intro Logos rest 1/2 secs each ...



All this demos are started under my workbench with the lastest WHDLOAD (17.1beta registered)

Another question : is .dms supported ? can't read this floppy --> http://pouet.net/prod.php?which=4063

[Toni Wilen]

It is normal. WHDLoad does not magically fix fast CPU (unless slave is coded to slow down the demo).

Use slower configuration or use whdload config file to run uae-configuration emulation mode change command lines on the fly.

EDIT: Either you have (very) fast WB and compatibility problems or slow WB and more compatibility. You can't have both

[Foul]

@ tony : ok, thx

@Frode : viewport = 0 0 * * => * * * *, * * * * => 74 36 640 512 seems to work like i wanted (always 4/3 modes...)

Hardwired demo don't even start on 16/9 screen ...

Perfect

[FrodeSolheim]

Originally Posted by Foul

@Frode : viewport = 0 0 * * => * * * *, * * * * => 74 36 640 512 seems to work like i wanted (always 4/3 modes...)

Well, not strictly 4:3 - 5:4 in case (nitpicking)

You may also want to have a slightly larger viewport (For example, Pinball Dreams draws outside the 640x512 rectangle), for example by displaying 8 pixels more on all sides:

viewport = 0 0 * * => * * * *, * * * * => 66 28 656 528

Anyway, I have a couple of related ideas.

1. The current FS-UAE behaviour is to render the Amiga screen (at max overscan size), and then only display a rectangle if this on the screen. The rectangle is calculated using UAE autoscaling algorithm, or it is overriden by the viewport option.

But in any case, content outside the rectangle is not shown at all! When not using aspect correction, this does not matter, since the rectangle is stretched across the screen, but with aspect correction on, you will most often get black bars (and normally this is fine).

However, with a widescreen monitor, you will almost always get black bars to the left and to the right (which can be a waste if there is any interesting content outside the crop rectangle). In this case, it would perhaps be better to just use the autoscaling code for centering, not cropping (overscan / Amiga border color would then fill the sides of the screen).

But since Amiga content is generally not centered on the full overscan area, and 16:9 displays are much wider than Amiga displays, this could look a bit ugly because you would still get black bars outside the overscan area, and the left and right black bar would not be equally wide. One way to handle this could be to repeat the leftmost and rightmost pixels until the edges of the monitor...

(this could be configurable, for example viewport_mode = crop / center)

2. Since input grab can be released with the middle mouse button, perhaps the F11 key could be reassigned to toggle between autoscaling mode and a fixed viewport rectangle (such as 66 28 656 528 with centering / border fill)..

Any thoughts or wishes?

[Foul]

i agree with viewport_mode = crop / center : simple to use and configure

[FrodeSolheim]

Originally Posted by Foul

i agree with viewport_mode = crop / center : simple to use and configure

and perhaps F11 should cycle between (in high-res / line doubled coordinates):

• autoscale
• 640x512 (at 74, 36) -perhaps with a bit of extra border
• 640x480 (at 74, 36) -perhaps with a bit of extra border
• 640x400 (at 74, 36) -perhaps with a bit of extra border
• max overscan (724x566)

Then F11 would work almost like the "zoom" function common on widescreen TVs -and would be a universal "fix" when autoscaling gets confused with a particular game / demo. Of course, if you're creating configuration files specific for games, you can fix this in the config file, but when you have the games installed on HD and using a single configuration to start the Amiga in Workbench...

[FrodeSolheim]

Originally Posted by Toni Wilen

Use slower configuration or use whdload config file to run uae-configuration emulation mode change command lines on the fly.

@Foul try something like this: http://guide.abime.net/wb3.1/miscwhd.htm

I see no reason why it wouldn't work in FS-UAE as well.

[Foul]

i can't, because, this system (sdcard) is also used in my real A1200

and the site is speaking about "jit", wich is not possible (activated) on a x64 system...

NOTE: No JIT! (No one has written Amiga compatible 680x0 to x64 JIT compiler)

Not really a big problem, i will just make 2 uae config, one A1200/020 to play games / watch demos and another "SUPER" to work on a fast Workbench (copying files etc..)

[Speedvicio]

Great work Frode
In this latest version the video frame rate appears to be much better.

[FrodeSolheim]

Originally Posted by Foul

and the site is speaking about "jit", wich is not possible (activated) on a x64 system...

Well, yes it talks about JIT too (the cachesize (JIT) setting will have no effect on FS-UAE), but also about changing cpu_speed. The latter should work in FS-UAE.

Originally Posted by Speedvicio

Great work Frode
In this latest version the video frame rate appears to be much better.

Great -Thanks for letting me know!

[AmigaOnline]

Originally Posted by AmigaOnline

ls it bad, Doc?

@Frode: Any investigation?

[Toni Wilen]

Originally Posted by Foul

i can't, because, this system (sdcard) is also used in my real A1200

uae-configuration does nothing if run on real Amigas (at least it shouldn't do anything at all)

[AmigaOnline]

Originally Posted by FrodeSolheim

* Hack to correct the output of the autoscale algorithm in some specific situations (some Workbench screens, etc), hack will be updated/removed as necessary.

Thanks for that. I have noticed the same issue with other "bars" (since FS-UAE 1.1.x). It's probably better to wait for a fix in the WinUAE code

[FrodeSolheim]

Originally Posted by Foul

Another question : is .dms supported ? can't read this floppy --> http://pouet.net/prod.php?which=4063

Yes, and this one worked just fine for me. Check your log file. Perhaps you have not pointed FS-UAE correctly to the file..

Originally Posted by jondel

"White screen and white menu problem " when using F12. Kubuntu 86x64 OpenGL version 1.4

Your problem is that atlas.png is not found (I saw this in the log file). It seems you have not installed FS-UAE properly...

Originally Posted by AmigaOnline

@Frode: Any investigation?

Tricky, this one... There is no good reason why the menu should use 5 seconds to open. I suspect an OpenGL driver issue. On my netbook with Intel 945, your problem cannot be reproduced. My parents may have a laptop with the same chipset as you have...

[Foul]

Originally Posted by Toni Wilen

uae-configuration does nothing if run on real Amigas (at least it shouldn't do anything at all)

so, will try .. thx again

Originally Posted by FrodeSolheim

Yes, and this one worked just fine for me. Check your log file. Perhaps you have not pointed FS-UAE correctly to the file..

was a bad download (empty file)

[AmigaOnline]

Originally Posted by FrodeSolheim

Tricky, this one... There is no good reason why the menu should use 5 seconds to open. I suspect an OpenGL driver issue. On my netbook with Intel 945, your problem cannot be reproduced. My parents may have a laptop with the same chipset as you have...

You're probably right. I will try the latest available drivers later (it may fix the other issue too: http://eab.abime.net/showpost.php?p=...&postcount=379 )

[jondel]

Originally Posted by FrodeSolheim

Your problem is that atlas.png is not found (I saw this in the log file). It seems you have not installed FS-UAE properly...

Thanks for this, yes that has fixed the problem. Other files were not updated as well, will keep an eye on this in future before posting.

[FrodeSolheim]

Originally Posted by jondel

Thanks for this, yes that has fixed the problem. Other files were not updated as well, will keep an eye on this in future before posting.

Next version warns with GUI message when textures cannot be loaded (except when the bitmap font cannot be loaded, of course )

[AmigaOnline]

Originally Posted by AmigaOnline

You're probably right. I will try the latest available drivers later (it may fix the other issue too: http://eab.abime.net/showpost.php?p=...&postcount=379 )

@Frode: Some news: I've installed the latest Intel drivers/same freeze issues.
Despite this, i've found a few useful infos. If I enable the FXT1 textures (driver option), the 2 issues are...fixed! but the downside is that...i can't see the texts anymore Any idea?

[FrodeSolheim]

Originally Posted by AmigaOnline

@Frode: Some news: I've installed the latest Intel drivers/same freeze issues.
Despite this, i've found a few useful infos. If I enable the FXT1 textures (driver option), the 2 issues are...fixed! but the downside is that...i can't see the texts anymore Any idea?

Don't do it then (force FXT1 texture compression?). But only the text is invisible?

But this strengthens the theory that it is a driver issue. Perhaps there is some other driver setting that is causing trouble?

Or perhaps.. the problem could be that the GPU memory is exhausted? (texture compression would reduce this problem...) If the driver has to swap textures in and out to system memory, this would surely slow things down a bit..

Quick calculation: FS-UAE uses (by default) a 1024x1024 (4MB) texture for the Amiga frames, 1024x1024 texture atlas (4MB), and a 2048x2048 - (16MB !) texture for text cache. Is there some way you can tell if you have about 24MB free GPU memory for textures?