Os4depot does allow multiple versions, usually best to add a note to say that the new version is an alternative to rather than a replace of the previous version.
BUt if there a lot of data in the archive dual binaries might well be the way to go.
just tried new version tonight and got guru after setting up the game and immediately after hitting create new world. Submitted crashlog to OS4depot.
update: after about 2 minutes of inactivity while I was loggin on here and typing this message all of a sudden the game screen popped up and I was playing minecraft fine on a 1920x1280 screen, game play was fine but a small bit laggy at times (I'm sure if I reduce screen size that won't be an issue). Dug a hole, built a small house, killed some sheep to eat and quit the game fine...strange.
Edited by 328gts on 2016/9/23 5:06:28 Edited by 328gts on 2016/9/23 5:07:02
just tried new version tonight and got guru after setting up the game and immediately after hitting create new world. Submitted crashlog to OS4depot.
update: after about 2 minutes of inactivity while I was loggin on here and typing this message all of a sudden the game screen popped up and I was playing minecraft fine on a 1920x1280 screen, game play was fine but a small bit laggy at times (I'm sure if I reduce screen size that won't be an issue). Dug a hole, built a small house, killed some sheep to eat and quit the game fine...strange.
The guru happened and it still loaded up? Or did you try again and it worked after a few minutes? And it crashed immediately after pressing the 'create' button, or after a few seconds?
Changing the screen size will make it faster, but making the view distance smaller will help a lot more. The screen size also has nothing to do with the lag, just the frame rate.
guru happened and it still loaded up? Or did you try again and it worked after a few minutes? And it crashed immediately after pressing the 'create' button, or after a few seconds? Changing the screen size will make it faster, but making the view distance smaller will help a lot more. The screen size also has nothing to do with the lag, just the frame rate.
yes guru happened I clicked 'ignore dsi errros' and then opened OWB to post here. It crashed immediately after hitting create. Changing the view distance made a small improvement on forward/backward movement. left/right is always fast.
That's mostly gibberish to me, is it saying the DSI was in a kickstart module?
Yes, it's crashing in the kernel. Unfortunately the machine froze before it could print the stack trace. Without the stack trace it's impossible to figure out where in your program the function call was made that ended up with a crash in the kernel.
The only way to debug stuff like this is to add progressively more IExec->DebugPrintF() calls to your code so you can narrow down where it's happening. Of course, that could alter the timing to the point where the crash no longer happens...
If you create a version of the executable with debug output as Hans suggested I can test it for you.
BTW I tried AmiCraftNova 1.0.1 on my beta install and it crashed in a different place in the kernel (on a load (lwz) instruction) but still no stack trace.
If you create a version of the executable with debug output as Hans suggested I can test it for you.
BTW I tried AmiCraftNova 1.0.1 on my beta install and it crashed in a different place in the kernel (on a load (lwz) instruction) but still no stack trace.
rp=get it from your context stored as a global variable... SetAPen(rp, 1); Move(rp,10,10); sprintf(text,"Line:%ld",line); size=strlen(text); Text(rp,(void*)text,size); }
Thanks, it didn't show where the crash was but it ruled out all the places I was looking. I've started testing and disabling other parts of the game and I've isolated the area where the crash occurs. Hopefully I can narrow it down and fix it tomorrow.