Dreamcast-Talk.com

|darc| wrote:At this point I'm guessing
1) perhaps the culprit is a different component (e.g. different Holly revision, different RAM vendor?)
2) it may have something to do with the contents of flash memory? Most of my DCs have had their flash memory wiped recently, but this one my fiancee owns hasn't.

You’re just posting baseless speculation and I can’t do anything about that. Knock yourself out lol
Having a little fun with ya here...^


If at anytime you want to go back to the tinfoil thread, pls let me know.
No1 has proven a damn thing as of yet.

The beta leaker and the original source of the cracked beta may have been found though. <--
Anyway good to see ya around.
Thanks for the heroes of might and magic .cdi

Wiping my Dreamcasts Flash Memory by running the DCFlash utility solved the controller problem for me:

https://dreamcast.wiki/File:DCFlash.zip

Great job in tackling this weird bug

thedoctor45 wrote:Wiping my Dreamcasts Flash Memory by running the DCFlash utility solved the controller problem for me:

https://dreamcast.wiki/File:DCFlash.zip

Just asking: Is this tool save to use? Is there anything else I will lose besides a PSO serial number? Does it work on USB-GDROM or am I risking to brick my DC?

Yep its save to use. You won't brick your DC.

From my experience you will also have to reset your language settings and your connection information (ISP) if you use a Dreampi for example. Apparently there is only a brick risk if you modded your DC

Ian Micheal wrote:

beanboy wrote:@Ian and others

What programming language was the dreamcast version of this game written in?

I dont even know.. but saying not enff ram i think is not correct they wanted 1 on 1 port that not how you port things to consoles of this time nothing was a one on one port..

thats just setting your self up to fail..

Yeah. That's the same thing I was thinking.

streeker wrote:

thedoctor45 wrote:Wiping my Dreamcasts Flash Memory by running the DCFlash utility solved the controller problem for me:

https://dreamcast.wiki/File:DCFlash.zip

Just asking: Is this tool save to use? Is there anything else I will lose besides a PSO serial number? Does it work on USB-GDROM or am I risking to brick my DC?

Well, I have used "DC Flash Eraser" to wipe the DC clean to allow PSO to work for me when one of my DC's motherboards died on me. It worked, so I flashed Radkin's replacement DC's so it would work and it did. I flashed my son's DC which also worked for his PSO character. Then I flashed Radkin's husbands DC for PSO, success!

4 for 4.

Here to report, that using the Flash Eraser resolved the controller bug.
Thanks @thedoctor45

beanboy wrote:

Ian Micheal wrote:

beanboy wrote:@Ian and others

What programming language was the dreamcast version of this game written in?

I dont even know.. but saying not enff ram i think is not correct they wanted 1 on 1 port that not how you port things to consoles of this time nothing was a one on one port..

thats just setting your self up to fail..

Yeah. That's the same thing I was thinking.

Game is written for a pc with large amounts of ram you dont do 1 to 1 port thats just insane not the dreamcast but the engine this whole game could be done on a amiga 2000 with 100 times less spec then a dreamcast

There are games like this on amiga 2000 settlers 1 and 2 with more indepth then this is using less ram under 2 meg.. They would had to write the engine from the start not port it.. this porting pc games to dreamcast was always a mistake I have made it my self .. the dreamcast is a 3d powerhouse need to use the sh4 and pvr to do your work then it's much more powerful then the same spec pc.. You can use the 3d hardware to do 2d very well use less ram then just blit it using a framebuffer doing it like a pc.