Openmsx ignores toggle_freq when done externally

Page 2/2
1 |

By Manuel

Ascended (14675)

Manuel's picture

24-03-2018, 14:54

mars2000you wrote:

what openMSX can't do for the VDP frequency, not only for the launching of the emulated MSX machine

I'm not sure what you mean here, but I think all was already said about this topic.

By Meits

Scribe (5113)

Meits's picture

24-03-2018, 15:25

JohnHassink wrote:

Maybe it is a message from the creators that they want you to play the game as it was intended. Wink Running Naked in a Field of Flowers

Sometimes it's not only an intended frequency, but a mandatory frequency. But that's only sometimes.

By mars2000you

Enlighted (5372)

mars2000you's picture

24-03-2018, 15:46

Manuel wrote:
mars2000you wrote:

what openMSX can't do for the VDP frequency, not only for the launching of the emulated MSX machine

I'm not sure what you mean here, but I think all was already said about this topic.

It means that blueMSX is able to directly boot a 50hz machine in 60hz mode when the 60hz mode is selected instead of the default Auto mode for the VDP frequency. Not only MSX2 and higher machines, but also MSX1 machines.

And of course the same for 60hz machines, they can be launched in 50hz mode if this mode has been selected instead of the Auto mode.

Besides, when the Auto mode is not selected, the eventual VDP frequency changes 'commanded' by the software are ignored by blueMSX on MSX2 and higher.

By brakenwagen

Supporter (14)

brakenwagen's picture

24-03-2018, 20:17

Wait a minute what if I just use the bind command and bind toggle_freq to a key press, ha ha I’ve done it. Hmm now another question some programs change the hz on their own easy enough to just change it back with a key press but do all programs tell you when there changing the refresh rate? Xak The Tower of Gazzel popes up something on the screen that indicates the change (capes on => 50hz) do others do this as well? Otherwise I need some way of openmsx reporting this to me.

as for blueMSX I already got that covered its my back up emulator. Its just that somehow I think openmsx has the best ctr filtering ever and is the only instant were i actually prefer ctr filtering over the usual hq filtering. It because you can set the individual aspects to what you want and I set them all really low. I believe that when it comes to ctr filters less is more, and most filters exaggerate the features of ctrs way to much.

I had a crt growing up and i don't remember them being that bad, to point were when i first saw scanline filters I was like what even is that? maybe if you had a really really old one like from the 60s or 70s but come on most weren't that pronounced. I'm left to wonder if maybe its because the filter artiest are looking at crts today and they have all aged to the point were they look nothing like what they did when they were relatively new idk. Old films are like that, we will never see King Kong the way they saw it back in the 30s. Black and White films like fugly today but back when they came out they were crisp and clear its just that the film has deteriorated over the years.

I've seen other crt filters that let you edit them but they give like 20 different options to change. Again less is more, meaning three options is plenty. Its like those stupid character creators in games my god I just want a character that looks good and is my own. I don't wont to have to take up an art major just to make an avatar.

And one final note if i ever want to play msx games on a Linux opnemsx is really my only option so best to know how to use it.

By Manuel

Ascended (14675)

Manuel's picture

24-03-2018, 22:27

The Gazzel thing you are talking about is actually a feature of the crack... it allows you to play the game at 50Hz if you turn on the CAPS LOCK. (So, no need for the toggle stuff then.)

It may be possible to make a script that sets the VDP back to PAL or NTSC mode whenever the software writes that register. I'll try to find that out. (It's a bit tricky, as usually first the value is written and then the register number...)

And indeed, you can always toggle it with a hotkey bind. Or manually toggle from the console or the OSD menu.

By Manuel

Ascended (14675)

Manuel's picture

25-03-2018, 16:22

It appears to be not too hard to create a small script to keep the VDP frequency to a certain value. If you're still interested, I'll work out the script into a usable command.

By brakenwagen

Supporter (14)

brakenwagen's picture

26-03-2018, 07:41

sounds cool

By brakenwagen

Supporter (14)

brakenwagen's picture

28-03-2018, 02:26

Any updates? I've been looking into to the tlc language and figured out how to output a messages to the screen. And I figured out how to replicate the toggle_freq function for example I can make "hz" do the same as "toggle_freq". what I need is some sort of listener that I can use to constantly check in the background the value and change it back whenever it detects a change. I tried a while loop but having an infinite loop just crashes the program. I found something called vwait but it seems that also makes everything else wait not just that one script. If anybody got has a suggestion I'm all ears.

By Manuel

Ascended (14675)

Manuel's picture

28-03-2018, 08:17

You could do something like this:

proc force_50hz {} {
  if {[expr {!([vdpreg 9] & 2)}]} {
    toggle_freq
  }
}
after frame force_50hz

(untested, but you got the point, I think.)

Page 2/2
1 |
My MSX profile