Jump to content
Visual Boy Advance-M

Boksha

Members
  • Content Count

    0
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Boksha

  • Rank
    Newbie
  1. Boksha

    Need help testing XAudio2

    So that's speaker setup in the configuration panel set to "Desktop stereo speakers" or "Stereo headphones" and all VBA-M settings on default, right? Seems to work fine here (build 634). I've got a Creative SB X-Fi XtremeGamer.
  2. Boksha

    Core rewrite

    The core code itself may be a mess, but as far as I can see (which isn't that far; I've only browsed through the sources for a bit; most of it's way beyond me anyway) the interface to it seems reasonably clean, with just a few functions that get called from outside of the core files. Maybe you could keep the changes "under the hood" so to speak? Keeping the same interface could mean you can keep improving on the Qt and MFC GUIs while using the old core (and maybe get a working Qt port with emulation soon), while at the same time being able to test a modified/rewritten core by directly plugging it into the existing MFC GUI to see if it works.
  3. Boksha

    Qt GUI feature suggestion thread

    I don't really know anything about Qt myself. (well, besides what I learnt from the first few tutorials, some experiments and the manual) Seems Qt at least has full threading support. If using that the Qt port ends up running as smoothly as the Win32 VBAM does right now that'd be great.
  4. Boksha

    Qt GUI feature suggestion thread

    Looking forward to it. Wouldn't idle time processing cause 100% CPU load by the way?
  5. Boksha

    Qt GUI feature suggestion thread

    Speaking of reporting, you guys might've already done something about this (last SVN I got was 595), but anyway I noticed this in the MainWnd.cpp: // 1000 / 60 = 60 fps, but only results to 40 fps in reality. // possible workaround: call timer more often and return or wait if too early After tinkering with it for a bit, I found that the timer Qt provides has a granularity of 1ms, but only if you set it to a repeat of less than 10ms; above input of 10ms, it first skips to slightly over 15ms real time, and input of 16ms and above it waits 25 real milliseconds every time (hence the 40 FPS). Constantly changing the timer causes some delay as well; on my PC the Qt port runs at almost exactly 60 FPS when first setting the timer to wait 7, then 8 ms, before every repaint, even though that should be 1000/(7+8)=67 FPS. Using a QBasicTimer object with a period of 1ms in the GraphicsOutput object (with timer.start(1, this); in the constructor) and the following timerEvent function: void GraphicsOutput::timerEvent(QTimerEvent * event) { const int tickms[3] = {16,17,17}; static unsigned char curframeof3 = 0; static int counter = 16; counter--; if (counter <= 0) { counter = tickms[curframeof3]; curframeof3++; if (curframeof3 > 2) curframeof3 = 0; repaint(); } } The FPS seem to converge to 60 or at least something very close to it (60.005 or 59.995 or something)
  6. Boksha

    Qt GUI feature suggestion thread

    Well, it's still a WIP. I'd actually love to play with this port for a bit (seeing as it's the only one I can even compile as I CBA to get any version of MSVC) but right now we'll just have to wait and see what's being done with it.
×