Jump to content
IGNORED

Altirra 2.70 released


phaeron

Recommended Posts

Version 2.70 of my emulator Altirra is now out:

 

http://www.virtualdub.org/altirra.html

 

It's been about nine months since the last release. Thanks to everyone who tried it out, reported bugs, and gave suggestions. 2.70 final is almost the same as the last test release (2.70-test40), except for a minor fix to the assembler.

 

Highlights of the 2.70 release:

  • Accuracy: Many 65C02/65C816 fixes; core ANTIC/GTIA/POKEY/PIA fixes; added 800 floating I/O bus emulation; many fixes for undocumented U1MB and XEP-80 behavior.
  • Built-in ROMs: Improved compatibility of AltirraOS; many fixes and nine new keywords added to Altirra BASIC.
  • Debugger: Many 65C816 fixes; new stepping and search commands; expanded profiling support with basic-block mode, multi-frame capture, and performance counter tracking.
  • Device emulation: Added R-Verter and Veronica; added 1050 timing and drive sounds.
  • Format support: SAP playback; SAP type R recording.
  • Input: New interactive controller tuner with tunable dead zones; fully customizable keyboard mapping.
  • Performance: Faster NTSC artifacting, more efficient Direct3D 11 vsync, reduced audio load on Vista+.

Also, now that 2.70 is finalized, it's time to start the prerelease test versions for 2.80:

 

http://www.virtualdub.org/beta/Altirra-2.80-test1.zip

http://www.virtualdub.org/beta/Altirra-2.80-test1-src.zip

 

Changes in 2.80-test1:

  • Added new profile system. The emulator now has the notion of an active profile, where the emulator configuration can be changed quickly by switching profiles, and profiles can selectively inherit categories of settings from parent profiles. The primary impact of this is that the emulator can now keep different settings for 8-bit computer and 5200 console modes, including mounted images, display settings, and input controllers.
  • There is now a button in Options to reset all settings.
  • File associations can now be registered in Windows as user-local as well as system-local. This allows associating the emulator with file types without needing administrator access.
  • /si and /nosi are now synonyms on the command line for /singleinstance and /nosingleinstance.
  • The 256K Rambo memory configuration is now supported. This memory configuration aliases 64K of extended memory against main memory, and is useful for testing memory sizing routines.
  • The debugger now automatically switches the active window between the Console and Display panes when execution starts and stops.
  • The debugger's heat map engine now has support for tracking movement of data between memory and the CPU and can stop execution when uninitialized memory is used.
  • Many fixes at source code level for VS2015 compatibility (note that VS2013u4 is still the main compiler).

 

  • Like 33
Link to comment
Share on other sites

i installed 2.8 t1... deleted the settings and configured everything from scratch...

 

now what makes me wonder... when launching EXE files Altirra shows the error report dialog.... they are launched via WUDSN IDE... so when I set option to break into debugger... now the debugger appears and autoamticly the exe starts... again it does not stop at EXE launch as it should...

 

and I am not able to enable drive sounds even switching from waveout to directsound.

Edited by Heaven/TQA
Link to comment
Share on other sites

Thank you for all the work that you've done on Altirra, Avery. Happy Holidays to you!

 

 

With the new profile system to save configuration settings, can you please give consideration for input record & playback? This feature will give us the ability to share game plays. Thanks.

Link to comment
Share on other sites

Audio settings were inadvertently left out in 2.80-test1 -- fixed:

http://www.virtualdub.org/beta/Altirra-2.80-test2.zip

http://www.virtualdub.org/beta/Altirra-2.80-test2-src.zip

 

Also, I had forgotten to mention a couple of other changes in 2.80-test1:

 

First, it has a fix for the CLI+SEI interrupt timing issue in high-speed '816 mode. Special thanks to drac030 for running tests on his accelerator hardware. tl;dr, the 65C816 acts the same as the 6502 with regard to when IRQs can actually fire around instructions that enable or disable the I flag.

 

Second, fast pot scan emulation is now improved. It is no longer possible to read paddles normally in fast pot scan mode, since the faster scan means that only 1/114th of the normal range is read. Also, the POTn values read back during the scan are now adjusted to reflect carry timing issues seen on the actual hardware. This means that fast pot scan mode unfortunately cannot be used for cycle-level timing. If you are writing code to read paddles directly, always use slow pot scan mode and always make sure that the previous pot scan has completed fully before starting the next one (>228 scanlines, regardless of ALLPOT).

 

With the new profile system to save configuration settings, can you please give consideration for input record & playback? This feature will give us the ability to share game plays. Thanks.

 

I understand the desire but don't want to implement this right now. Input recording and playback requires cycle-perfect synchronization since any change in instruction timing can desync the playback. This means that any change in emulation timing or in emulation settings can break recordings. I already have enough trouble keeping save states working.

 

Link to comment
Share on other sites

I understand the desire but don't want to implement this right now. Input recording and playback requires cycle-perfect synchronization since any change in instruction timing can desync the playback. This means that any change in emulation timing or in emulation settings can break recordings. I already have enough trouble keeping save states working.

 

Avery,

 

Thank you for the reply and I understand that you already have set priorities. But as you continue to develop new codes, can you please keep this feature in the back of your mind and have a planned code structure in place for possible future implementation? Thanks.

Link to comment
Share on other sites

I'm running into some issues with the profile system. I'm seeing "devices" being put into a profile when they are not added, or even after I remove them. Also the devices are repeated sometimes 3 or 4 times. And yes, this is with inheritance completely disabled (all boxes checked) in the affected profile.

Link to comment
Share on other sites

Fixed... had a bug where the settings loader wasn't clearing old devices before loading new ones. Since clearing an exponential growth of devices one at a time isn't fun, I also added a Remove All button to the Devices dialog.

 

http://www.virtualdub.org/beta/Altirra-2.80-test3.zip

http://www.virtualdub.org/beta/Altirra-2.80-test3-src.zip

  • Like 3
Link to comment
Share on other sites

Profiles now? Look'n'good :thumbsup:

 

It will be some time before I get back to my emulation rig, several days, a week at least.. So where are the profiles stored? A registry entry? A file? The .ini? And do they work in portable mode? All sorts of questions!

 

I am standing to be corrected, but, I am guessing that they are stored where the rest of Altirra's settings are stored. That means either the registry, or an .INI file, depending on which way you are rolling with it.

Link to comment
Share on other sites

Yes, the profiles are implemented as sliced subfolders of the original Settings branch in the Registry or .INI file. Instead of loading or saving to the base Settings folder, the categories of settings are bound to different profiles based on the inheritance settings of each profile. There are some other minor changes, such as splitting apart the active input map settings from the input maps themselves.

 

A few other details of profiles:

  • You can nest profiles more than one level. Select a profile before clicking Add to create a child under that profile. Drag a profile to reparent it. Reparenting a profile preserves its local settings and pulls inherited settings from the new parent.
  • There is a default profile for each machine type. This is used when the emulator needs to switch machines, such as trying to boot a 5200 cartridge in computer mode.
  • /profile:<name> on the command line selects a specific profile. /defprofile:xl|xegs|800|1200xl|5200 selects the profile assigned as the default profile for the specified machine type.
  • Like 2
Link to comment
Share on other sites

I went to try to get 2.70 running under Wine with OS X, and came across Wineskin. Apparently, Wineskin is a way to wrap a Windows program up with the Wine libraries as an application bundle under OS X. So, that's what I did.

 

Altirra.dmg

 

It appears to work just fine under El Capitan, except don't try to have Altirra go full screen, it gets wonky. Using OS X full screen is fine, although you're stuck with a little border and a menu.

 

(It creates a 510MB Application bundle! Ack!)

  • Like 2
Link to comment
Share on other sites

Phaeron, you did work excellent to fix a bug regarding to Rescue on Fractalus game and accelerated 65C816 processor mode! Also, drac030, you did work excellent!

 

Special thanks to Phaeron and drac030! :)

 

I can now able to play Rescue on Fractalus game in accelerated 65C816 modes! Graphics are much smoother and the game is much more playable, even though there are graphics glitches in accelerated 85C816 modes. Graphics glitches are very minor and I DO NOT CARE about minor graphics glitches!

Link to comment
Share on other sites

Many thanks, I just updated to the latest version of Altirra, because I read about Star Raiders II, thanks for all the work, I use you emulator for years now and it is nice to see how much progress you made from that last version I had installed (which did already everything I ever wanted from an Atari 8-Bit emualtor).

 

Phaeron, you did work excellent to fix a bug regarding to Rescue on Fractalus game and accelerated 65C816 processor mode! Also, drac030, you did work excellent!

 

Special thanks to Phaeron and drac030! :)

 

I can now able to play Rescue on Fractalus game in accelerated 65C816 modes! Graphics are much smoother and the game is much more playable, even though there are graphics glitches in accelerated 85C816 modes. Graphics glitches are very minor and I DO NOT CARE about minor graphics glitches!

 

Is there a way to get rid of the flickering sky? Whenever I try anything above 1.79 MHz the sky begins to flicker.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...