Fuse 1.5.2 released
Re: Fuse 1.5.2 released
Double sided disk images are still somewhat counter-intuitive to use. You need to set the drive options to be a double sided drive to create both sides of the disk (format, flip it, format again). That image will then work with a single head drive (both sides must be formatted though or saving the image fails with bad geometry).
It would be nice if the act of flipping a single sided disk in a single sided drive added the second side, but I guess that could be difficult to achieve.
It also still creates a file with two side 0s. Side 1 of a double sided disk image can't be formatted by fuse by flipping the disk as far as I can see.
It would be nice if the act of flipping a single sided disk in a single sided drive added the second side, but I guess that could be difficult to achieve.
It also still creates a file with two side 0s. Side 1 of a double sided disk image can't be formatted by fuse by flipping the disk as far as I can see.
- Ast A. Moore
- Rick Dangerous
- Posts: 2641
- Joined: Mon Nov 13, 2017 3:16 pm
Re: Fuse 1.5.2 released
Thanks. That’s too convoluted, though, but I might give it a shot, after Fred cooks up v1.5.2 for macOS.serbalgi wrote: ↑Sat Mar 31, 2018 3:36 pm I think you can still use the old autoload snapshots on a dev workflow:
Choose the autoload snapshot from an old version or here:Code: Select all
fuse tape_48.szx --tape your_tape.tap
https://sourceforge.net/p/fuse-emulator ... compressed
Every man should plant a tree, build a house, and write a ZX Spectrum game.
Author of A Yankee in Iraq, a 50 fps shoot-’em-up—the first game to utilize the floating bus on the +2A/+3,
and zasm Z80 Assembler syntax highlighter.
Author of A Yankee in Iraq, a 50 fps shoot-’em-up—the first game to utilize the floating bus on the +2A/+3,
and zasm Z80 Assembler syntax highlighter.
Re: Fuse 1.5.2 released
I've just built and tested fuse 1.5.2 for Linux. I thought I might time a drag and drop load so you'll know what to expect. Truth is, with the "phantom typist" in working in "auto mode" (whatever that is) it's too fast to time. You don't actually see the typing like you used to; you don't actually see anything happen in the Spectrum window. It looks like they've optimised it by turning off the screen updates or something.Ast A. Moore wrote: ↑Sat Mar 31, 2018 4:12 pmThanks. That’s too convoluted, though, but I might give it a shot, after Fred cooks up v1.5.2 for macOS.serbalgi wrote: ↑Sat Mar 31, 2018 3:36 pm I think you can still use the old autoload snapshots on a dev workflow:
Choose the autoload snapshot from an old version or here:Code: Select all
fuse tape_48.szx --tape your_tape.tap
https://sourceforge.net/p/fuse-emulator ... compressed
Assuming the Mac version you're after is the same as the Linux version, I think you'll like it.
Derek Fountain, author of the ZX Spectrum C Programmer's Getting Started Guide and various open source games, hardware and other projects, including an IF1 and ZX Microdrive emulator.
Re: Fuse 1.5.2 released
HI [mention]Fred[/mention] I just tried to download from Sourceforge and got an error on the Windows Setup:
The "/fuse/1.5.2/fuse-1.5...5.2-win32-setup.exe" file could not be found or is not available. Please select another file.
The "/fuse/1.5.2/fuse-1.5...5.2-win32-setup.exe" file could not be found or is not available. Please select another file.
- Ast A. Moore
- Rick Dangerous
- Posts: 2641
- Joined: Mon Nov 13, 2017 3:16 pm
Re: Fuse 1.5.2 released
Thanks for the info, man! I sure hope so, as I’m really used to seeing my program already running by the time the OS switches focus from the text editor to Fuse. Fuse for macOS is a special beast, though. Pretty much a standalone app and not a port. I think Fred builds it using the latest Fuse source as a base, and puts a lot of extra effort into making it a native macOS application. So, we’ll see.dfzx wrote: ↑Sat Mar 31, 2018 7:46 pm with the "phantom typist" in working in "auto mode" (whatever that is) it's too fast to time. You don't actually see the typing like you used to; you don't actually see anything happen in the Spectrum window. It looks like they've optimised it by turning off the screen updates or something.
Assuming the Mac version you're after is the same as the Linux version, I think you'll like it.
Every man should plant a tree, build a house, and write a ZX Spectrum game.
Author of A Yankee in Iraq, a 50 fps shoot-’em-up—the first game to utilize the floating bus on the +2A/+3,
and zasm Z80 Assembler syntax highlighter.
Author of A Yankee in Iraq, a 50 fps shoot-’em-up—the first game to utilize the floating bus on the +2A/+3,
and zasm Z80 Assembler syntax highlighter.
Re: Fuse 1.5.2 released
Hi @PeterJ, I just checked the download and it was OK - could you try again to see if the problem is resolved?
Re: Fuse 1.5.2 released
That's pretty much the process. A future version will warn when trying to save unformatted sides to DSK images. An UDI format can save unformatted tracks.Guesser wrote: ↑Sat Mar 31, 2018 4:04 pm Double sided disk images are still somewhat counter-intuitive to use. You need to set the drive options to be a double sided drive to create both sides of the disk (format, flip it, format again). That image will then work with a single head drive (both sides must be formatted though or saving the image fails with bad geometry).
Thanks, it's a nice idea to consider.It would be nice if the act of flipping a single sided disk in a single sided drive added the second side, but I guess that could be difficult to achieve.
I'm not sure that's an issue to fix. Tracks of both sides are correctly stored in the DSK image, but tracks are formatted by +3DOS and the ID address mark that precedes every sector are always set as head 0:It also still creates a file with two side 0s. Side 1 of a double sided disk image can't be formatted by fuse by flipping the disk as far as I can see.
Code: Select all
DD FORMAT
016Ch (364)
Format a track. (Uses the uPD765A format track command.)
Buffer contains 4 bytes for each sector as follows:
C - Track number (0...39)
H - Head number (always 0 on the +3's single-sided drives)
R - Sector number (0...255)
N - Log2(sector size)-7 (2 for 512 byte sectors)
Also, I guess your version of Spin Disk Manager use the first address mark to name the side (couldn't found that version). Newer versions of Disk Image Manager use the information in the image rather than the address marks.
Re: Fuse 1.5.2 released
I thought I was using the latest version. It's entirely possible I'm using it incorrectly though
It's not an important problem, just noting that disk images formatted double sided can't be reformatted to single sides in fuse.
Since I doubt anyone is emulating double sided 40 track drives in anger it's rather irrelevant.
Re: Fuse 1.5.2 released
Thanks [mention]Fred[/mention] now working fine. Cheers
- Einar Saukas
- Bugaboo
- Posts: 3143
- Joined: Wed Nov 15, 2017 2:48 pm
Re: Fuse 1.5.2 released
Hi [mention]Fred[/mention], may I provide another suggestion for improvement?
When users save a screenshot, it's always their intention to obtain an accurate copy of whatever they are seeing on screen. However that's not what happens in practice. Every emulator I know will simply dump a copy of memory content from screen area starting at 16384. The problem is, quite often this content doesn't correspond to currently visible screen, because the program may have already started to modify screen area in preparation for the next screen. There's a reasonable chance the saved screenshot will contain parts of the current frame mixed with parts of the next frame.
It would be more accurate to "remember" exactly the bytes that produced each piece of the current screen, and save those instead. Fuse is already managing this information anyway for saving MLT screenshots, so it should be trivial to use it for regular screenshots (SCR or otherwise) too.
Games that update screen at 50Hz will mostly benefit from this feature. It's very hard to save a proper SCR image of those games, that won't show parts of 2 different images.
The only drawback is, if users save a screenshot immediately after loading a snapshot, the emulator won't have the same detailed information about generating current screen. In this case only, it can simply fallback into saving a memory dump of the screen memory area. But that's nothing new, really. Try pausing any emulator, then loading a multicolor game, for instance. The screen will appear distortrd, because the emulator won't know how to reconstitute current screen, until running the program for another frame.
When users save a screenshot, it's always their intention to obtain an accurate copy of whatever they are seeing on screen. However that's not what happens in practice. Every emulator I know will simply dump a copy of memory content from screen area starting at 16384. The problem is, quite often this content doesn't correspond to currently visible screen, because the program may have already started to modify screen area in preparation for the next screen. There's a reasonable chance the saved screenshot will contain parts of the current frame mixed with parts of the next frame.
It would be more accurate to "remember" exactly the bytes that produced each piece of the current screen, and save those instead. Fuse is already managing this information anyway for saving MLT screenshots, so it should be trivial to use it for regular screenshots (SCR or otherwise) too.
Games that update screen at 50Hz will mostly benefit from this feature. It's very hard to save a proper SCR image of those games, that won't show parts of 2 different images.
The only drawback is, if users save a screenshot immediately after loading a snapshot, the emulator won't have the same detailed information about generating current screen. In this case only, it can simply fallback into saving a memory dump of the screen memory area. But that's nothing new, really. Try pausing any emulator, then loading a multicolor game, for instance. The screen will appear distortrd, because the emulator won't know how to reconstitute current screen, until running the program for another frame.
Re: Fuse 1.5.2 released
Hi [mention]Einar Saukas[/mention] ,
Yes, that should be fairly straightforward to do as basically writing out the first row of each MLT attribute line as the attribute for the SCR - note that there may be some glitches at some points as the real breakdown of the screen image is the MLT image.
I've added your feature request to the Fuse sourceforge tracker here: https://sourceforge.net/p/fuse-emulator ... uests/127/.
Yes, that should be fairly straightforward to do as basically writing out the first row of each MLT attribute line as the attribute for the SCR - note that there may be some glitches at some points as the real breakdown of the screen image is the MLT image.
I've added your feature request to the Fuse sourceforge tracker here: https://sourceforge.net/p/fuse-emulator ... uests/127/.
- Einar Saukas
- Bugaboo
- Posts: 3143
- Joined: Wed Nov 15, 2017 2:48 pm
Re: Fuse 1.5.2 released
And it's now implemented for the next release.
- Einar Saukas
- Bugaboo
- Posts: 3143
- Joined: Wed Nov 15, 2017 2:48 pm