letzter Beitrag von LGB-Z am
Thank you guys, we made a lot of progress so far.
You wont be able to move in the maze due to lack of some keyboard input registers.
Regarding video, next VIC-IV steps I have in mind:
* Fix the 16-color color sprite renderer (found a bug)
* Implement 4-bit character mode
* Implement Sprite Collisions (this is picky in terms of precision/performance balance).
I'm developing in two machines, MacBook with 2.7GHz i5 and my desktop with a good ol' 4790K and runs well so far; Optimizations will come later for sure.
Das ist echt mega 
To be honest, most of the VIC-IV stuff at least is more the product of Hernan, since I'm more busy with the "foundations" of the emulator recently and I have less time for the VIC-IV emulation enhancements (other than the MEGA65 palette handling stuff, more or less). Anyway, these things will be merged together at one point in the future.
To be honest, most of the VIC-IV stuff at least is more the product of Hernan, since I'm more busy with the "foundations" of the emulator recently and I have less time for the VIC-IV emulation enhancements (other than the MEGA65 palette handling stuff, more or less). Anyway, these things will be merged together at one point in the future.
Team work. And thanks for such a great foundation 
To be honest, most of the VIC-IV stuff at least is more the product of Hernan, since I'm more busy with the "foundations" of the emulator recently and I have less time for the VIC-IV emulation enhancements (other than the MEGA65 palette handling stuff, more or less). Anyway, these things will be merged together at one point in the future.
Team work. And thanks for such a great foundation
Yeah, just but I thought it wouldn't have been fair not to mention it.
(most people will see the result of better VIC-IV emulation but not the "foundations" too much, so for them, that work is more important
"it was mostly YOUR work!" - "no it was YOURS!" - "oh no it was YOURS!"
cute 
"it was mostly YOUR work!" - "no it was YOURS!" - "oh no it was YOURS!"
cute
Haha, wait for the bugs. Then: Ahaaaa, I told it's not my work ;-P [just kidding of course] More seriously, in the past I had some VERY negative experience in issues like this, so since then I wanted to be extra careful not to leave any confusion, that's all.
The most important is, that the project attracted one more volunteer 
Are the Mega65 text modes reasonably well supported? I'm mainly interested in 40x25 / 80x25 / 80x50, with screen memory starting from $10000 (has to be outside of normal C64 address space), no extended colours or anything like this.
The most important is, that the project attracted one more volunteer
Are the Mega65 text modes reasonably well supported? I'm mainly interested in 40x25 / 80x25 / 80x50, with screen memory starting from $10000 (has to be outside of normal C64 address space), no extended colours or anything like this.
Yes, screen relocation is supported via $D060-63 registers. You can check the Mega65 Sprite Editor Im working on and the related CONIO library that I have created for the MEGA65 libC . In that case I needed to make room for the code which grew up fast; so I put screen at $12000 without hassle. I think that in $10000 you will encounter CBM DOS code -I'm not 100% sure- or if this ROM can be banked out.
Ref:
https://github.com/MEGA65/mega…b/master/freeze_sprited.c
https://github.com/MEGA65/mega65-libc/tree/master/cc65
Also, see for reference
The most important is, that the project attracted one more volunteer
Are the Mega65 text modes reasonably well supported? I'm mainly interested in 40x25 / 80x25 / 80x50, with screen memory starting from $10000 (has to be outside of normal C64 address space), no extended colours or anything like this.Yes, screen relocation is supported via $D060-63 registers. You can check the Mega65 Sprite Editor Im working on and the related CONIO library that I have created for the MEGA65 libC . In that case I needed to make room for the code which grew up fast; so I put screen at $12000 without hassle. I think that in $10000 you will encounter CBM DOS code -I'm not 100% sure- or if this ROM can be banked out.
From VIC-IV point of view, the "fast RAM" is just RAM without any banking or such (well, from 128K, there is the 128K of "ROM" but it's really RAM - can be write protected or not - and this question does not go that high address anyway). So the "worst" can happen to overwrite some CBM DOS data/code/whatever area there but in the RAM. Thus then it's problematic to use CBM DOS to load further data from disk etc, of course, but if it's not a requirement, it won't matter too much to "mess up" that RAM area.
There is no DOS in my ROM nevertheless I just want to move screen out of the C64 address space, so that I have memory for additional features, like BASIC variable cache (I'll restore the C64 memory layout as soon as SYS command is encountered, or someone tries to load anything below $0800) - we can determine the best position later.
There is no DOS in my ROM nevertheless
Oh, so it's your own ROM. Then especially OK, if you control what RAM part is being used by yourself, it won't be a problem, for sure.
If you make it $12000 you will avoid the C65 DOS, if you choose to later implement/include it.
LG
Paul
If I choose to implement it later, I'll need more memory than just 8KB (at least the amount needed to store 1 full track of 3.5" HD disk).
In such case, it will be better to shift the screen memory towards $1F800 (if I understand correctly, above that we have colour RAM, not suitable for storing screen data).
Colour RAM 2K is shadowed at $1F800-$1FFFF, yes. But we can probably arrange to disable that shadowing, if desired.
I quite agree that a better C65 DOS would have a full track buffer, as the current one doesn't even seem to buffer one side of a track, resulting in very slow load times from real disks.
LG
Paul.
I'm not sure if complicating the Mega65 memory mapping even more is a good idea. We will see - whatever I'll do, it will be easy to change the text screen location later.
I don't think Xemu works with the enhanced sprites yet, right?
At least, that what I read here:
Alles anzeigenHi Bobaflott
since your question is XEMU related, i 'll move your post to the appropriate Thread.
LGB-Z and hernandp are constantly working on Xemu, Hernandp is working on the VIC-IV implementation.
So just follow here and you will get the latest news
Ah, thanks! I'm new here and itching to start programming before I get my devkit
Would be nice to have a XEMU version that supports the VIC-IV sprites.
It didn't seem to work on the version I found (for Windows).
