blueMSX status

Página 4/6
1 | 2 | 3 | | 5 | 6

Por dvik

Prophet (2200)

Imagen del dvik

19-01-2019, 23:33

Hi,

While working on the V9958 emulation I ended up a bit confused about how horizontal scroll works (in particular the lower 3 bits and edge masks). If someone could help me understand I'd be very thankful.

What I'm trying to fully understand is how the first 24 pixels of a scan line (including border) is rendered given the horizontal scroll register. Assume with hscroll = 0, the following pixels are rendered (I assume):

b b b b b b b b 0 1 2 3 4 5 6 7 x x x x x x x

where b is 8 left border pixels and x'es are the next 8 pixels on the scan line.

so first question: With hscroll = 1 how are the pixels 0-7 mapped (e.g.):
b b b b b b b 0 1 2 3 4 5 6 7 x x x x x x x x

second question assume border masking is set, which pixels are masked (both in the hscroll = 0 case and when hscroll = 1)

third question, how is border masking looking at the right border?

Any thoughts that can help me fully understand this is appreciated.

Por dvik

Prophet (2200)

Imagen del dvik

22-01-2019, 08:14

Thanks for feedback and help.

@NYYRIKKI: I fixed several bugs in the command engine and the renderers so the Alt demo runs (almost) correct now. Still puzzled about the blink color issue.

I Also fixed some minor MoonSound issues, and I added a special rom insert menu to add MSX Audio and Moonsound easily.

The command engine fixes I'd like to port back to mother blue as the web version now has (apart from new unknown bugs possibly introduced) better emulation.

Check it out and lmk what you think.

Por Parn

Hero (557)

Imagen del Parn

23-01-2019, 19:22

@dvik, has anyone answered your question about the V9958 horizontal scroll registers? I don't see any messages between your last one and your previous one. I think I can help if it's still needed, but I wouldn't want to waste forum space if it isn't.

Por mars2000you

Enlighted (5630)

Imagen del mars2000you

23-01-2019, 19:32

The answers have been given in this specific thread: https://www.msx.org/forum/msx-talk/emulation/help-understand...

Por dvik

Prophet (2200)

Imagen del dvik

23-01-2019, 22:04

Thanks, Yes it was answered and I implemented the change, however I don't mind hearing your explanation as well because I'm still not 100% confident I got it right. wouter_@ gave me good insight and the latest version is a quite big improvement and I also did some smaller but quite impactful fixes in the command engine. So now beppin and the alt demo works almost 100%. One small potential issue is in the last scroller in the alt demo where I would expect masking to look different. So happy to hear your explanation of the hscroll.

Por Parn

Hero (557)

Imagen del Parn

24-01-2019, 23:46

Ok, I'll post my observations on that thread as well. Smile

Por ren

Paragon (1455)

Imagen del ren

17-04-2019, 16:01

Cool to see some development again here.

I concur with what Garudian said earlier (page 3): having these changes find their way to the Libretro core would be pretty awesome.

I don't care much for the web version myself (ATM): it lacks features and seems slow. (Though the latter may also have to do with my browser config/settings.)

Since there's WebMSX, which seems to do a pretty good & cool job already, my vote would go to the invest into the Libretro core option as well here Smile

Cheers!

ps: I'll test some stuff in the latest version when I have some time.

Por dvik

Prophet (2200)

Imagen del dvik

22-04-2019, 07:25

Yes I'd like to get the c version updated, a fair bit of work to get the windows version working again, but I can probably use another port to just get the core fixes in.

Curious ren what you are lacking from the web version (if it is slow for you it may not be that interesting indeed, but I'm running it quite successfully in chrome on both windows, linux, and on my Pixel phone).

Por ducasp

Champion (304)

Imagen del ducasp

06-09-2019, 04:33

Hi Daniel,

https://msx.org/forum/msx-talk/development/vdp-v9938-blinkin...

Both the online version as well as Windows version do not implement page flipping correctly when R13 has a non 0 value and R2 has an odd page address in SCREEN 5 to 8....

BTW, I've downloaded the latest code from Sourceforge ( https://sourceforge.net/p/bluemsx/code/HEAD/tree/trunk/blueMSX/ ) of Windows version, but I couldn't compile even following the instructions in the make folder, I get the following errors and weird warnings using visual studio 2008 / Microsoft Platform SDK for Windows Server 2003 R2 / Microsoft DirectX SDK (August 2007):

c:\bluemsx-code-r1295-trunk-bluemsx\bluemsx-code-r1295-trunk-bluemsx\src\win32\win32.c(872) : warning C4013: 'actionQuickSaveStateUndo' undefined; assuming extern returning int

c:\bluemsx-code-r1295-trunk-bluemsx\bluemsx-code-r1295-trunk-bluemsx\src\win32\win32.c(3320) : warning C4013: 'strcasestr' undefined; assuming extern returning int

c:\bluemsx-code-r1295-trunk-bluemsx\bluemsx-code-r1295-trunk-bluemsx\src\win32\win32menu.c(1968) : warning C4013: 'showLoadMemoryDlg' undefined; assuming extern returning int

To compile qedit.h you must install the DirectX 9 SDK, to obtain the dxtrans.h header.

And then everything falls apart starting with:

1>Win32.obj : error LNK2019: unresolved external symbol _D3DEnterWindowedMode referenced in function _archUpdateWindow
1>Win32.obj : error LNK2019: unresolved external symbol _D3DEnterFullscreenMode referenced in function _archUpdateWindow
1>Win32.obj : error LNK2019: unresolved external symbol _D3DExitFullscreenMode referenced in function _archUpdateWindow
1>Win32.obj : error LNK2019: unresolved external symbol _D3DUpdateSurface referenced in function _emuWindowDraw
1>Win32.obj : error LNK2019: unresolved external symbol _D3DUpdateWindowedMode referenced in function _wndProc@16

(and I've checked the project settings, both C++ settings as well as linker are referencing to the August 2007 Direct X folder)...

If you have any hints to spare, I'll be grateful, would like to try to fix one UDP bug to use BlueMSX to debug some UNAPI stuff I've been working as well as the VDP R#13 on Screens 5-8. :P

Por ducasp

Champion (304)

Imagen del ducasp

23-09-2019, 21:48

ducasp wrote:

Hi Daniel,

https://msx.org/forum/msx-talk/development/vdp-v9938-blinkin...

Both the online version as well as Windows version do not implement page flipping correctly when R13 has a non 0 value and R2 has an odd page address in SCREEN 5 to 8....

BTW, I've downloaded the latest code from Sourceforge ( https://sourceforge.net/p/bluemsx/code/HEAD/tree/trunk/blueMSX/ ) of Windows version, but I couldn't compile even following the instructions in the make folder, I get the following errors and weird warnings using visual studio 2008 / Microsoft Platform SDK for Windows Server 2003 R2 / Microsoft DirectX SDK (August 2007):

c:\bluemsx-code-r1295-trunk-bluemsx\bluemsx-code-r1295-trunk-bluemsx\src\win32\win32.c(872) : warning C4013: 'actionQuickSaveStateUndo' undefined; assuming extern returning int

c:\bluemsx-code-r1295-trunk-bluemsx\bluemsx-code-r1295-trunk-bluemsx\src\win32\win32.c(3320) : warning C4013: 'strcasestr' undefined; assuming extern returning int

c:\bluemsx-code-r1295-trunk-bluemsx\bluemsx-code-r1295-trunk-bluemsx\src\win32\win32menu.c(1968) : warning C4013: 'showLoadMemoryDlg' undefined; assuming extern returning int

To compile qedit.h you must install the DirectX 9 SDK, to obtain the dxtrans.h header.

And then everything falls apart starting with:

1>Win32.obj : error LNK2019: unresolved external symbol _D3DEnterWindowedMode referenced in function _archUpdateWindow
1>Win32.obj : error LNK2019: unresolved external symbol _D3DEnterFullscreenMode referenced in function _archUpdateWindow
1>Win32.obj : error LNK2019: unresolved external symbol _D3DExitFullscreenMode referenced in function _archUpdateWindow
1>Win32.obj : error LNK2019: unresolved external symbol _D3DUpdateSurface referenced in function _emuWindowDraw
1>Win32.obj : error LNK2019: unresolved external symbol _D3DUpdateWindowedMode referenced in function _wndProc@16

(and I've checked the project settings, both C++ settings as well as linker are referencing to the August 2007 Direct X folder)...

If you have any hints to spare, I'll be grateful, would like to try to fix one UDP bug to use BlueMSX to debug some UNAPI stuff I've been working as well as the VDP R#13 on Screens 5-8. :P

Well, it seems the vcxproj file for VS2008 is broken and my issues were all from:

Missing D3d9.lib D3dx9.lib in linker settings....

Missing quite a few files in the project file that were not being compiled, but were present in the trunk.

After fixing the vcxproj I could compile and run it fine.

Whoever has this issue, I've created a blueMSX repository to hold my changes:
https://github.com/ducasp/blueMSX

And the working vcxproj for vs2008 can be found at:

https://github.com/ducasp/blueMSX/tree/master/Make/msvc2008

Página 4/6
1 | 2 | 3 | | 5 | 6