CycloDS iEVO

I dont think this DSi feature adds anything at all ?
what are the upsides of having this, other than running 1 or 2 homebrew in DSi mode?

Not to mention that the main homebrew app that takes advantage of the extra speed is twice as fast on the DSTwo anyway (40mhz 386 on the DStwo vs 20mhz on the iEvo). So much for the whole "but the bottleneck issues and slower ram mean it sucks compared to DSi mode" thing.
Mhz do not reflect the factual speed of a processor. You should know that.

is there a DS homebrew benchmark app that evaluates the processing speed of the CPU ? :P
we should run it on both the DSTWO and the CycloDS in DSi mode to see who's right lol
 
I dont think this DSi feature adds anything at all ?
what are the upsides of having this, other than running 1 or 2 homebrew in DSi mode?

Not to mention that the main homebrew app that takes advantage of the extra speed is twice as fast on the DSTwo anyway (40mhz 386 on the DStwo vs 20mhz on the iEvo). So much for the whole "but the bottleneck issues and slower ram mean it sucks compared to DSi mode" thing.
Mhz do not reflect the factual speed of a processor. You should know that.

is there a DS homebrew benchmark app that evaluates the processing speed of the CPU ? :P
we should run it on both the DSTWO and the CycloDS in DSi mode to see who's right lol

That benchmark came from DSix86 and DS2x86. To confirm it, have someone with both an iEvo and DSTwo run Windows 3.0 and Arena (elder scrolls 1) in both DSi mode and on the DSTwo.
 
I dont think this DSi feature adds anything at all ?
what are the upsides of having this, other than running 1 or 2 homebrew in DSi mode?

Not to mention that the main homebrew app that takes advantage of the extra speed is twice as fast on the DSTwo anyway (40mhz 386 on the DStwo vs 20mhz on the iEvo). So much for the whole "but the bottleneck issues and slower ram mean it sucks compared to DSi mode" thing.
Mhz do not reflect the factual speed of a processor. You should know that.

is there a DS homebrew benchmark app that evaluates the processing speed of the CPU ? :P
we should run it on both the DSTWO and the CycloDS in DSi mode to see who's right lol
I'm not saying that he's wrong - it'd be my guess to assume that the DSTwo in conjunction with the standard DS CPU is infact faster than just the DSi's CPU in DSi-Mode. What I'm saying is that he's using the wrong argument. Not only that, speed isn't always everything, what about RAM? More is better, quite obviously, and the DSTwo is still limited to the 4Mb of the DS-Mode.

Now, if there were a "DSiTwo"... Insta-buy.
 
I dont think this DSi feature adds anything at all ?
what are the upsides of having this, other than running 1 or 2 homebrew in DSi mode?

Not to mention that the main homebrew app that takes advantage of the extra speed is twice as fast on the DSTwo anyway (40mhz 386 on the DStwo vs 20mhz on the iEvo). So much for the whole "but the bottleneck issues and slower ram mean it sucks compared to DSi mode" thing.
Mhz do not reflect the factual speed of a processor. You should know that.

is there a DS homebrew benchmark app that evaluates the processing speed of the CPU ? :P
we should run it on both the DSTWO and the CycloDS in DSi mode to see who's right lol
I'm not saying that he's wrong - it'd be my guess to assume that the DSTwo in conjunction with the standard DS CPU is infact faster than just the DSi's CPU in DSi-Mode. What I'm saying is that he's using the wrong argument. Not only that, speed isn't always everything, what about RAM? More is better, quite obviously, and the DSTwo is still limited to the 4Mb of the DS-Mode.

Now, if there were a "DSiTwo"... Insta-buy.

Nope, the DSTwo has 32MB. In fact, without special handling the DS's RAM isn't used at all. Even DS2x86 only uses the DS's CPU and RAM for Adlib/Soundblaster emulation thanks to custom transfer code and a custom DS side executable.

Even before the full SDK source was released and when DS2x86 used the DSTwo CPU/RAM exclusively it was still much faster DSix86.
 
Nope, the DSTwo has 32MB. In fact, without special handling the DS's RAM isn't used at all. Even DS2x86 only uses the DS's CPU and RAM for Adlib/Soundblaster emulation thanks to custom transfer code and a custom DS side executable.

Even before the full SDK source was released and when DS2x86 used the DSTwo CPU/RAM exclusively it was still much faster DSix86.
Ah, I see. First time I hear of this. That's good then, I stand corrected.
 
Nope, the DSTwo has 32MB. In fact, without special handling the DS's RAM isn't used at all. Even DS2x86 only uses the DS's CPU and RAM for Adlib/Soundblaster emulation thanks to custom transfer code and a custom DS side executable.

Even before the full SDK source was released and when DS2x86 used the DSTwo CPU/RAM exclusively it was still much faster DSix86.
Ah, I see. First time I hear of this. That's good then, I stand corrected.

You might want to check out some of the DSx86 blog archives as he does get into the whole DSi mode vs DSTwo thing. Also remember that this is the guy who REWROTE the DSTwo-DS transfer code to make it much more efficient (though the modified SDK, available on the gbatemp dstwo development forum, doesn't have sound support).
 
  • Like
Reactions: 1 person
A lot of good information here, didn't mean to start a flame war but looks like everyone can back up their claims with factual evidence and sound logic.

Thanks

and yah... Imigine if the DSTWO made a revision to the hardware that supported DSi Mode, plus if they made a new card at this stage in the game it most likely would ship with better hardware, so it'de have all of that power (it be nice to see a dual core and more ram) on top of DSi mode.

Anyone think it'll happen?
 
A lot of good information here, didn't mean to start a flame war but looks like everyone can back up their claims with factual evidence and sound logic.

Thanks

and yah... Imigine if the DSTWO made a revision to the hardware that supported DSi Mode, plus if they made a new card at this stage in the game it most likely would ship with better hardware, so it'de have all of that power (it be nice to see a dual core and more ram) on top of DSi mode.

Anyone think it'll happen?
Doubt it. Nobody's interested in DSi-Mode, really. They should busy themselves with 3DS carts for now... :P

All I really want from the DSi are DSiWare dumps and some sort of a loader for them - too many of those games gets recalled and there's no way to actually store them with 100% certainty that they're complete.
 
All I really want from the DSi are DSiWare dumps and some sort of a loader for them - too many of those games gets recalled and there's no way to actually store them with 100% certainty that they're complete.
I agree with this. While loading DSi-mode ROMs is nice, that can wait. The preservation of DSiware is important. We don't want another BS-X scenario.
 
Does it recognize the ram and the cpu of ds to improve homebrews like moonshell(see DPG high bitrate videos with no lag) and emulators?????
 
Does it recognize the ram and the cpu of ds to improve homebrews like moonshell(see DPG high bitrate videos with no lag) and emulators?????
It recognizes the 16 MB (up from 4MB) RAM and 133Mhz (up from 67Mhz) CPU from the DSi's extra capabilities. However the homebrew in question has to be compiled relatively recently or it can't take advantage (Moonshell isn't, sorry).

Then there is the extra issue of the ievo being blocked from recent firmwares on both dsi and 3ds. Its a dead card essentially, the cyclo team is no longer active.
 
Good to know, but I sad to know that is not possible to improve the performance of moonshell :(, I hate to have to convert DPG with wide screen and with medium/low bitrate and fps :(.
 

Site & Scene News

Popular threads in this forum