openMSX upcoming release: please help! | MSX Resource Center (Page 4/6)

Prophet (2409)

21-12-2008, 18:39

Thanks Slotman, i think this is one of those freak occurrences that probably will happen once in a blue moon.

I think the OSD and console should not be visible together, keep in mind that the OSD is still a technology preview which hasn't been finalized yet ,feedback is appreciated though for the means of improvements. There is still a lot to do before we have a working OSD on the WII version for example. But once that all works we should be good

By Manuel

Ascended (19314)

22-12-2008, 09:42

Thanks Slotman, i think this is one of those freak occurrences that probably will happen once in a blue moon.

Never underestimate these things! A guy at work here was right when he said: incident == Santa Claus. (Both don't exist.)

Anyway, without a way to reproduce it, it is almost impossible to fix it, though

I think the OSD and console should not be visible together, keep in mind that the OSD is still a technology preview which hasn't been finalized yet ,feedback is appreciated though for the means of improvements. There is still a lot to do before we have a working OSD on the WII version for example. But once that all works we should be good

We'll include such a remark in the release notes indeed.

By mfeingol

Champion (293)

25-12-2008, 00:34

Well, quite some people downloaded the beta, but we didn't get many reactions yet... (about 2). So, what's up folks? What's bad? What's good? Any bugs?

Latest Windows beta (with fixed crash, thanks to Muffie for finding out): http://openmsx.sourceforge.net/temp/openmsx-0.6.3-dev8409-win32-bin.exe

Actually, I do have a bug to report: sometimes, when I hit the quicksave button, I get a quickload instead.

Context: Vista x64, openMSX version mentioned above. Playing Xak II, using quicksave states pretty frequently. I've also remapped quicksave to F6 and quickload to ALT+F6, using the console 'bind' command. The bug shows up using the remapped keys - I haven't seen it happen using the defaults (ALT+F8 / ALT+F7). It also takes quite a while to repro.

(If I had to guess, I'd say the emulator is getting confused somehow about whether the ALT key is pressed or not.)

By Manuel

Ascended (19314)

26-12-2008, 23:56

Hmmm, I can't see how openMSX can be 'confused' about keys being pressed. But sounds like the key binding you choose is not the ideal one, you can easily make mistake (e.g. by not pressing ALT firmly enough or so). Also, if this is a bug, it's more likely to be a bug in SDL than on our code, so not something we can easily fix...

Anything else, though?

By mfeingol

Champion (293)

27-12-2008, 21:59

Manuel:

Evidently the keybinding I chose wasn't ideal. But this wasn't a PEBCAK issue. In the rare cases where the problem would repro, I'd press F6 *without* ALT, and it would be interpreted by openMSX as a quickload (bound to ALT+F6). I've since gone back to the default keybindings. But this *is* a real problem, not user error.

It's interesting that you mention that you're using SDL. I encountered a somewhat similar bug working with Santi Ontañón on his Maze of Galious remake several years ago. You can see the results of that in the following thread: http://www.braingames.getput.com/forum/forum_posts.asp?TID=114. The solution we came up with for Win32 there may be of use to you.

Aside from that, the beta bits are working very well for me. Save-states are awesome when they work; thanks for implementing those! At this point, the only nits I have at the moment with openMSX are probably old ones:

1) SDL-PP at 1x pegs a CPU core at 50% emulating a GT. This is with a dual core Intel E8400, latest nVidia drivers, Vista x64. In contrast, CPU usage with the SDL renderer at 1x is about 10%.
2) Catapult loses the list of .ips patches when I switch disks. Given that the list exists in the first place, this feels like a bug.

By Vampier

Prophet (2409)

27-12-2008, 22:22

Thanks Max,

SDL has quite some keyboard issues, I've pasted the link onto Manuel.

By Manuel

Ascended (19314)

28-12-2008, 00:50

mfeingol: ALT: we'll take a look, but it won't be in the upcoming release anymore, it's too dangerous to do stuff like this such a short time before the release.

1) as SDLGL-PP mostly runs on your videocard, you probably do not have a very good card for OpenGL 2.0. Which model is it?
2) Ah... sounds like a bug, but I'm afraid we're not going to fix it (unless someone else provides a patch), as the old Catapult is presumed dead.

Thanks for reporting!

By mfeingol

Champion (293)

28-12-2008, 00:56

Understand the hesitance to take any keyboard related fixes now.

My video card is an nVidia 8600GT.

Will there be a new Catapult?

By Vampier

Prophet (2409)

28-12-2008, 01:14

There will be a new catapult.

http://video.google.com/videoplay?docid=-2573417155828621119&ei=4MRWScPtJqa2qAOT8I26AQ&q=openmsx+catapult&hl=en

and yes the sound is out of sync

By mth

Champion (507)

28-12-2008, 01:21

A 8600GT is a decent card and should not have problems with the OpenGL functionality we use.

Vista has a somewhat higher overhead for OpenGL than XP, because OpenGL in Vista has to share control of the video card with the Aero system. 50% CPU sounds a bit high though.

About the ALT problem: Since this seems to be an SDL problem, it should be fixed there; I'd rather not put a workaround in the openMSX code if we have an opportunity to fix it at the source. The openMSX binaries we release are statically linked against SDL, so if we would have a patch that fixes SDL, the openMSX binary would be fixed too.

In any case, a fix would have to be made and go through a lot of testing, so it's too late for this release. As a workaround, you can go to fullscreen with F12, which should avoid the hanging ALT. Alternatively, stick to the default keyboard bindings

We are working on a new Catapult, but it does not yet have sufficient features to replace the old one.