Closed dirkwhoffmann closed 5 years ago
Finally, I think I got it right. vAmiga now has a two-pass upscaling pipeline that can be configured individually in the video preferences:
I also figured out that the xBR shader relies on pixel blending to work properly. The results is quite nice I think.
Upper picture: Original Amiga output (pipeline setting: none + none) Middle picture: In-texture lowres scaling: (pipeline setting: xBR + none) Lower picture: Two-pass xBR (pipeline setting: xBR + xBR)
Looks brilliant sharp like a vector monitor now. Played once asteroids on a Vectrex. That was as sharp as the results of your two pass xBR pipeline.
Another epic moment: My first Guru meditation π².
it starts talking to us ... It is already some kind of dialog I think. It says something to us and expects our action in form of a left mouse button click. Surly some kind of intelligent life form... Maybe it wants to test your reaction...
it starts talking to us ...
Yes, it becomes scary now π¬.
Fortunately, it only shows this mean reaction when I restore it from a snapshot. Maybe, it doesn't like it's brain to be frozen π€. Denise really has to work on her handwriting. The Guru meditation is hardly readable.
Opening two emulator instances in parallel seems to work. I therefore conclude that it doesn't have a problem with multiple personalities.
Oh, just noticed that I don't save the CPU state into the snapshot π.
So when it wakes up from hyper sleep, it works with his current brain state on old memories. No wonder he's a little disoriented. Must be like a big hangover for him π₯΄. Poor thing π.
Time to release a first beta of vAmiga 0.1 π:
http://www.dirkwhoffmann.de/vAMIGA/vAmiga_0.1b1.zip
If you want to check it out, make sure that an original Kickstart is used (1.2 or 1.3). Booting the Aros replacement produces a permanent black screen.
vAmiga follows the tradition of UAE 0.1: It runs Kickstart to the point where the hand & disk logo shows up, but because the disk drive is a stub yet, it cannot go further.
Nevertheless, many GUI functions already work. They give you a glimpse what the emulator will look like. You can take snapshots and screenshots, emulate keystrokes by typing on a virtual keyboard, or adjust video settings. The CPU, Memory and Event Inspector windows are nearly complete. You can stop the emulator there and single-step through the code, view the memory layout and content, or watch the currently scheduled events (vAmiga is event-based, so there's a lot going on there).
Any bug reports are welcome, even tiny things. Finding bugs shouldn't be too difficult at this early development stage π.
Hi to all, It starts well with my kickstarts: Kickstart v1.2 rev 33.180 (1986)(Commodore)(A500-A1000-A2000) Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV)
The kickstart hand seems to me more shifted to the left and not centered.
Hi everyone, my kickstart 1.3 works, but the image is not centered even to me, it seems to the left a little. With the options in the preferences menu the image is not centered because black vertical bands appear.
Please ignore the centering issue for now (I am displaying almost the full texture yet). I'l take care of that once the DIWSTRT and DIWSTOP registers are implemented properly (but to do this, I need to be able to boot the Workbench first).
I am going to use this thread as a logbook in the near future to document the progress towards version 0.1. V0.1 should have about the same functionality as UAE 0.1. We'll then have a (completely useless) emulator that can do nothing but show the Workbench initial screen. To speak with a picture:
This is the current situation:
We have
So letβs see how far we can get with this. These are the first lines of Kickstart 1.2 which I want to step through:
Before we can get started, we need to install the Kickstart Rom. This is done in the hardware preferences. By default, the Aros replacement Rom is installed.
It can be replaced by an original Rom via drag & drop, so why stick to the clone if we can have the real stuff π:
The Kickstart Rom is usually located in the upper memory area. On startup, the Amiga mirrors it in the lower memory banks to enable the CPU to find the correct start vector. The memory inspector shows the details:
When powering on the Amiga, the CPU loads the start vector from the mirrored Kickstart Rom and jumps to address FC00D2. For testing purposes I let the emulator stop at FC00DE at a predefined breakpoint which can be watched in the CPU panel:
Letβs set another breakpoint at FC00FE by double clicking the corresponding line in the program window:
By pressing the Run button the CPU starts and stops at FC00FE.
Pretty nice so far π₯³, but at this point the Kickstart Rom writes into the CIA registers π. Two CIAs are already present in the current implementation, but they are not yet connected to memory. Therefore I have to stop here. I'll continue this thread once the CIAs are connected. Stay tuned ...