| |
ciccior2003
Account closed
Registered: Jun 2012
Posts: 12 |
Ultimate II+ .crt+reu
i have tested a demo made to work in .crt + reu. It works in vice but with 1541 ultimate II+ to work i have to start demo,crt than disable reu from menu. Return to demo, enable the reu and reset the system without reload the demo.crt.
I have made the same with RR.crt and Reu doesn’t work until i don’t disable and enable the Reu.
There is a settings to start .crt and use Reu without this method? |
|
... 17 posts hidden. Click here to view all posts....
|
| |
TheRyk
Registered: Mar 2009
Posts: 2107 |
How about contacting Firmware developers of 1541UII+?
If it's still markus, he'll be glad to help if it's fixable via fw update.
And he's very trustworthy, he fixed some EF issues of 1541UII+ some years ago with a some crack we've never released and never leaked anything :) |
| |
ciccior2003
Account closed
Registered: Jun 2012
Posts: 12 |
Quote: Quote:in c64 scene the 95% of people use Vice
in the actual c64 scene 100% use real hardware.
Can be true but 95% of demos are seen from vice or youtube.. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11164 |
the point being? |
| |
ciccior2003
Account closed
Registered: Jun 2012
Posts: 12 |
the point is a compromise to have real c64 and emu cartridge to have simil REU.
I think that using virtual-REU mixed at .crt can boost the c64 in new way. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11164 |
wat |
| |
Raistlin
Registered: Mar 2007
Posts: 587 |
The point is... if we’re creating a product for people to enjoy... and if it doesn’t work in an emulator - and we can easily fix that... we will likely fix it. And let the developer of the emulator know what we found.
I agree that the pure scene is on real hardware. BUT... you can’t on one hand say that the people making releases have a responsibility to release something that bugs on an emulator just to push the developers of the emulator to fix their shit... while also saying that those developers won’t be bothered to fix it if we just tell them about it? That makes it sound like the emu devs don’t care about purity - but that the release (demo/intro/whatever) devs should? |
| |
JackAsser
Registered: Jun 2002
Posts: 1997 |
Quote: The point is... if we’re creating a product for people to enjoy... and if it doesn’t work in an emulator - and we can easily fix that... we will likely fix it. And let the developer of the emulator know what we found.
I agree that the pure scene is on real hardware. BUT... you can’t on one hand say that the people making releases have a responsibility to release something that bugs on an emulator just to push the developers of the emulator to fix their shit... while also saying that those developers won’t be bothered to fix it if we just tell them about it? That makes it sound like the emu devs don’t care about purity - but that the release (demo/intro/whatever) devs should?
I'd never tbh. If it works on the real thing and not in VICE, well, tough luck. I would likely try to fix VICE myself actually instead of spending time working around the bug in the demo/game. Or at the very minimum harass Groepaz and Blacky. |
| |
Walt
Registered: May 2004
Posts: 47 |
I agree, of course, that real hardware is the correct way. And as others have said, finding a real REU is hard.
1541 Ultimate is a great product and as I wrote, I have contacted Gideon but he has not (AFAIK) fixed the issue.
Me being oldschool means that I still use old VICE versions, especially as I'm not very fond of GTK on Windows ;)
If I had released Expand with no checks and no delay for fixing the loader issue on 1541 Ultimate I'm 100% certain that I would be getting the blame :
"He can't even time a magic byte raster effect, what a lamer!!!11"
"The demo crashes at random, when will he learn to code???"
The above was also the reason for releasing REU Tools, not so much in regard to VICE as the newer versions (and dropping x64 in favor of x64sc) means that only the older versions have problems, but then the hardware implementors have something to test their products... |
| |
TheRyk
Registered: Mar 2009
Posts: 2107 |
Walt: I used to think this way, too (if coder can't work around new fancy hardware spoofs, coder is the one to blame). But the firmware developers of both 1541-U-II+ and TC64 assured me, it's the other way round. If sth works on real (ancient) hardware but not on "unreal" but nice-to-have new stuff, it's up to the firmare developers to make their hardware behave as accurately as possible compared to original hardware. |
| |
oziphantom
Registered: Oct 2014
Posts: 480 |
lets do our best to avoid the ZSNES problem ;) |
| Previous - 1 | 2 | 3 - Next |
