mirao

I've just upgraded Ubuntu 23.10 => 24.04 and now "wine" (Ubuntu 9.0~repack-4build3) installed from the internal Ubuntu repo works with Direct3D 9 fine. So IMHO WineHQ repo is not needed anymore.

That's great. However could you use a more prominent color (e.g. light blue instead of light gray)?

I had the same issue, see I reported it to Wine: https://bugs.winehq.org/show_bug.cgi?id=54182 Interestingly when I'm trying it now, it's working well. Just tested with Altirra 4.20-test29, wine-8.21 (Staging), Ubuntu 23.10

An easier way than building from a source exists: using a binary from WineHQ repository: https://wiki.winehq.org/Ubuntu. Then Direct3D 9/11 works too. So I would prefer to use this repository and not rely on internal Ubuntu repo. Some more "performance" testing in Altirra: CPU Ryzen 4700U, GPU AMD Radeon RX Vega 7 - animation with Direct3D 11 is slower than with Direct3D 9 CPU Ryzen 5800H, GPU AMD Radeon RX Vega 8 - animation with Direct3D 11 is the same as with Direct3D 9 As for various filter settings when using Direct3D 9 or 11, if I set "Filter mode => Point", image seems to be sharpest (it can be checked e.g. on GR.0 font), the same way as when I disable Direct3D completely. If I use other filter modes + various value of "Filter sharpness", screen is still a bit blurred (less or more) when comparing with "Filter mode => Point".

If you can look at the log .... This is a log from a distribution's Wine, Direct3D 11: https://gist.github.com/mirao/5ed6224a2668a2cb8fc758d181a4e1ce , where I'm getting gray screen only. And this is a log from a custom (my own built) Wine, Direct3D 11: https://gist.github.com/mirao/e1cc0f98a8fc09069dba1b46a87f958d , where a display output is correct (but worse performance than with Direct3D 9). Thanks.

It seems to be an issue with a distribution's Wine only. When I build Wine from sources (tested with 6.23, 7.22, 8.20), Direct3D 9 a 11 work in Altirra (tested by change of filtering mode). It looks like the Wine version distributed since Ubuntu 22.10 (22.10, 23.04, 23.10) doesn't have built right stuff to be working with my HW correctly (CPU Ryzen 4700U, GPU AMD Radeon RX Vega 7). I enabled Direct3D 9 because animation with Direct3D 11 is noticeably slower than with Diect3D 9 or with GDI.

Altirra crashes when using a command line help in my Wine environment this way: Run this command from a terminal: Altirra64.exe /? Click into the window with the help so that you can see a text cursor Press Ctrl + C (selecting of text doesn't matter) Click on the button "OK" Altirra will crash in a moment 🐞 Here is a a crash dump: AltirraCrash.zip Used SW: Ubuntu 23.10 Wine wine-8.0.1 Altirra 4.20-test29

I can confirm similar issue as @VinsCool. The version 24 is buggy, the version 23 works fine. Steps: Run Altirra Debug => Open source file Open a source file (an ASM file) You get an error instead of file open in a viewer: If you close the error dialog and try to open the source file again, Altirra will crash in a few seconds AltirraCrash.zip My environment is Ubuntu 23.04, Wine 8.0 My Altirra configuration: Base system PAL 800XL (320K) Additional devices Host device (H:), Printer (P:), MidiMate OS firmware Atari XL/XE OS ver.3 [29F133F7] Mounted images None

One more tip for a gamepad: Recently I bought https://www.tomtop.com/p-paa5368-128a.html. You can connect its wireless gamepad conroller to a PC and both included gamepads work well in Altirra in Wine with the configuration "Gamepad -> Joystick" (XInput Controller #1 and #2). Tested on Ubuntu 23.04. The controller is detected by OS as a USB device "Twin USB Joystick". I guess it could work in native Windows too.

These two solutions work for me: Install an external CHM viewer, e.g. xCHM and open "Altirra.chm" using it Install wine-gecko into wine. Then you should be able to open a help from Altirra (Help => Contents). I can't remember exact instructions, but Google should help you.

Yes, similar way I tested a network in MIDI Maze, with multiple Altirra instances on one host:

BTW did anybody finish that game? (it's also here: http://www.atarimania.com/game-atari-400-800-xl-xe-jet-set-willy_2664.html). I collected only 73 items. It seems that there are missing some rooms when comparing with the version Jet Set Will 2007 or 2019 where 83 items are available.

View => Save Frame May I ask how did you get the graphics working? I have similar issue on Ubuntu 23.04. I must disable the "Direct3D 9" setting (which means fallback to GDI) otherwise I get a gray screen only.

This works for me: Click on "Escape", "Control" and "<" (to the left from "Ins")

It works, thank you. I didn't know that a screen watch is tracked in watches, because I didn't see it in the window "Watch". But now I can see that the window "Watch" contains different items than "wl".

I can enable tracking of a value in "Debug => Window => Memory" on a screen. I just right click a memory value and select "Track On-Screen". But how could I disable the tracking? If I click to "Track On-Screen" again (on the same value I'm already tracking), unexpectedly the value will be tracked twice on screen. Only way how to get rid of tracking is a restart of Altirra. Any idea?

This is an annoying issue because if you enter "10 DIM" and run program, interpreter freezes. Moreover even if you warm reset and run "LIST" or "NEW", interpreter still freezes. Not sure if there is some better workaround than cold reset (which obviously causes that your program is lost). I remember the issue from my real Atari 800 XE a now I can see it also in Altirra in ATARI BASIC rev. A/B/C. Altirra BASIC isn't affected. Yeah, the issue is also mentioned in http://atariki.krap.pl/index.php/Atari_BASIC#B.C5.82.C4.99dy_w_Atari_BASIC

Great. I did a network setup again, this time with a game started after that configuration and now it's working. So maybe a cold reset could solve the issue and it was only about order of setup and start of game. I think originally I tried only warm reset when a network setup was done. Thank you very much.

Nice, two nodes setup works for me. But unable to get working three nodes. I have exactly the same loop setup as on your screenshots and I use listening on "localhost" on three Altirra instances (ports 9001, 9002 and 9003 on the same real machine where the emulators are running). There is no error in Devices. But MIDI Maze shows me only "This is a slave machine" in all three instances. Am I missing something?

What I like on the Disassembly view in the debugger is that I can use e.g. dw vvblki (implemented in 4.10) But the same thing isn't possible in the Memory view. E.g. if I want to see a display list content using dw sdlstl it doesn't work. At first I have to find a value of sdlstl and then enter "HIGH" and "LO" bytes to get appropriate content. Is it possible to unify it with the Disassembly view? One more thing: I noticed that the Memory view doesn't store previously entered addresses, therefore they are not visible in a drop down menu. It works well in the Disassembly view: BTW editing of memory content in the Memory view is great feature and allows quick testing of change of value without interrupting of app and using debug console. Thanks for it!

A triviality: A help in debugger shows the "wx" command twice:

What's purpose of the arrows in Disassembly view in debugger? I thought that they could navigate between addresses in the drop down menu. But nothing happens if I click to any of them.

I noticed a crash when converting unformatted disk. Tested with 4.01/4.10/4.20, all the versions are affected. File => Disk drives D1 => New disk Keep default values, i.e. "Single density", "unformatted" D1 => Convert filesystem => Select any format (e.g. DOS 1.0) Altirra will crash in a few seconds instead of formatting of an empty disk to the selected format Used SW: Ubuntu 22.10, wine 7.0, Altirra 4.20-test9 AltirraCrash.mdmp

Thanks for the info, I just was wondering why in Altirra the drive D3 doesn't work in DOS 2.5 😀. Finally I found out a HOWTO here: https://www.atariarchives.org/mapping/memorymap.php#1802 It can be also setup by the tool SETUP.COM provided by DOS 2.5 (see http://www.atarimania.com/documents/Atari DOS 2.5 - 1050 Disk Drive Owner's Manual.pdf, APPENDIX L, The DOS 2.5 disk utilities)

I know. DX9/DX11 doesn't work for me since I upgraded Ubuntu to 22.04 => 22.10 and so far haven't found any solution: Actually I don't know what the option "Calibrate..." is good for, just hit it and wanted to report that it crashes in my env.