Please help testing upcoming openMSX release!

Page 40/45
33 | 34 | 35 | 36 | 37 | 38 | 39 | | 41 | 42 | 43 | 44 | 45

By ren

Paragon (1458)

ren's picture

23-06-2020, 22:40

Go? Smile

Probably you'll be making a thing or two clear in the release notes.
As there have been some big changes, and perhaps something unforeseen may still show up, and people will encounter things that are a bit different now (as we've been discussing here), you could suggest people to keep 0.15 around?

I think it's not a problem to have them both installed, and let them both use the same userdir? (Same thing regarding Catapult <> registry?)
I checked: 0.15 doesn't complain e.g. about the vsync setting, and I've been testing that way these last few days Smile

Although I don't now how that would work for the installer, Linux repo's etc. as I always use the zips (and extract them in separate dirs obviously).. Flatpack apps?

ps. note that I earlier was primarily referring to the possibility to have e.g. a 1280x960 image centered FS instead of a image that's using all of the available space.

By Manuel

Ascended (16702)

Manuel's picture

23-06-2020, 22:42

Well, that's not full screen, that's just windowed, centered with the rest black Smile

Anyway, the current release notes draft can also be seen in the doc folder. Comments always welcome.

I wouldn't recommend to run two releases mixed. This may have unforeseen effects, especially on your settings. And replays or savestates saved with the later version may not load in the earlier version.

if there's a problem with the new release, people can just report it and we'll fix it.

By ren

Paragon (1458)

ren's picture

23-06-2020, 23:05

Manuel wrote:

Well, that's not full screen, that's just windowed, centered with the rest black Smile

Hehe, I guess you're right Smile You could call it 'distraction free' mode then Wink (Funny stuff aside, I think that would be a nice thing to have Smile)

Ah yes, save states might be a thing of course.. Smile

Note that I've largely remedied my issues (thanks for pointing that one out Grauw Wink) So my test results are not random bullshit or something Wink
And normally, running 2 version alongside, I follow the changelog/commits of course Wink (Now, I guess I was too lazy to completely separate the things, figured it wasn't necessary.)

Yeah sure, so go? Smile

(edit: I think I depleted the smilies.. Tongue)

By Manuel

Ascended (16702)

Manuel's picture

29-06-2020, 08:41

We added some code that automatically sets maxframeskip to 20 when vsync is enabled if you use the full throttle mode. Please confirm.
It also helps to test whether nothing else broken, so when not using vsync or when recording AVI videos. (In the latter case we must render all frames for the video file but when full throttle is enabled, we do not show all frames on screen.)

By Manuel

Ascended (16702)

Manuel's picture

29-06-2020, 18:24

@grauw can you also confirm/check?

By Grauw

Ascended (9181)

Grauw's picture

29-06-2020, 18:51

I checked, everything is working well and I’m 100% happy. The recording change is also a welcome improvement.

My only consideration would be that the unthrottled play is now very fast, which is great, but which also makes it hard to fast-forward through sections without overshooting by a lot. E.g. earlier when I played Darwin 4078 with maxframeskip 100 I wanted to fast-forward through the level intro and died instantly. So I set maxframeskip back to 3, the ability to change the throttling amount was useful to me. Currently the value of 20 is hardcoded, would it be worth making a setting?

Yes ren, you depleted the smileys Big smile.

By Manuel

Ascended (16702)

Manuel's picture

29-06-2020, 22:02

You could replace the binding for F9 to a temporary speed change of 200, or 500% or whatever suits you best.

We have plans to change this in the future and do not use the throttle in the F9 key binding anymore, but something like I described above.

By ren

Paragon (1458)

ren's picture

02-07-2020, 14:17

Had a look/go with the new turbo stuff (869-g569de531b).

Observation: maxframeskip 0 practically means turbo has no effect (well, it does mean a stuttering PAL demo scroll @ 60hz res, starts running smoothly.. so it seems openMSX is throttling to match display refresh perhaps? The fps OSD does confirm 60). It is speeding up when vsync is set to 0, but still slower than with a maxframeskip setting of > 0.

I think maxframeskip is meant to kick in / have an effect only during normal run conditions, so it shouldn't have an effect when using enabling turbo (F9) or when throttle is off (previously F9), am I right?

Oh, and playing with the turbo, throttle and maxframeskip settings I managed to get openMSX in a state where it wouldn't go back to 100% (normal) anymore Smile

With the new turbo toggle, what's the use case for throttle? (Btw: when using throttle I see fps goes down, whereas w/ turbo it's going up Smile)

Other remark: isn't the term 'turbo' a bit (much, esp. in MSX-land) ambiguous?

-edit: hmm.. turns out in a 2nd test that w/ maxframeskip 0 & vsync off it's just as much turbo as w/ maxframeskip > 0. Note that sometimes I reach up to ~ 1000fps, at other times it seems it won't go past ~ 650fps (running the same bit of software on same config).
-edit2: ah, when vsync is on, the fps indicator always goes to ~60 (= monitor refresh?) when using turbo/speed...

What's the relation to the speed setting? Seems to do the same thing as turbo? Only difference is that the speed setting seems to be hard capped @ ~ 250fps?

By Grauw

Ascended (9181)

Grauw's picture

02-07-2020, 14:40

The maxframeskip is scaled by the turbo speed, but I think instead of turboMultiplier * maxframeskip, the formula should be turboMultiplier * (maxframeskip + 1) - 1. So if sped up x20 with a maxframeskip of 0, it should render every 20th frame, iow be allowed to skip 19 frames.

I like this new turbo btw. Also a better term than unthrottle.

By mth

Champion (494)

mth's picture

03-07-2020, 00:08

We're considering renaming "turbo" to "fastforward", to avoid possible confusion with R800 mode.

"turbo"/"fastforward" works in exactly the same way as the "speed" setting: there are two speeds (typically 100% and something much faster) that you can swap between with a hotkey (F9/Cmd+T).

Turning off throttle is still useful if you want to run as fast as possible and don't care to see what is going on or be able to stop in time for something to happen. openMSX will display at 10 fps to make sure you still see something happening, but skips most frames so it can run faster.

Grauw's scaling formula makes sense; I'll change the code to use something similar to that. (We don't actually scale the limit in the code, but scale the counter instead, since that way we don't accumulate rounding errors.)

Page 40/45
33 | 34 | 35 | 36 | 37 | 38 | 39 | | 41 | 42 | 43 | 44 | 45