-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for 680x0 CPUs #122
Comments
Wow this is fantastic! Many thanks to both of you! |
fixed and pushed to uat |
Great, thanks a lot! |
new version without 68020 instruction logging pushed to uat |
Great, thanks, works fine now! |
restored cpu type in settings from a snapshot load and removed the pushed to uat environment (https://vamigaweb.github.io/uat/) |
Great idea, thanks! |
I restored snapshots from the previous version. |
with the 68000 oder 68020 ? I mean what was inside the snapshot, which type of cpu? If 68020 then maybe still some bug in restoration of the internal CPU state? I see some more commits on vAmiga which I have not yet merged into vAmigaWeb ... this one |
Yes, 68020 for everything... |
ok ... too new stuff 😅 ... just merging in the latest commits from dirk... |
merged latest commits from vAmiga (no 68030 yet) but probably more stable than the code base from three days ago pushed to uat |
Now both previous snapshots reset the amiga and reload their floppy or hdd! :) |
That is because the internal structure of the snapshot has changed. There were this missing CPU stuff mentioned above. (Which caused probably the issue after restoring snapshot of interceptor. ) Therefore it cannot load it anymore. I did not increased the version therefore also no compatibility warning. Uat version is only for tests. |
Ok, understood, thanks! |
what exactly means distorted ? I tried interceptor with 68020 to reproduce it and what I see on iPhone after snapshot restoring in |
I don't get it ... I literally searched minutes for something odd on the pictures above ... I mean I can not see the distortion in your picture nor the difference... can you describe with words what you think is wrong ? |
The first picture is much taller, the letters are quite stretched vertically |
Ah ok, I understand now ... reproduced it and now I see it too ... => that happens only in test case: load it from start test case: load it from a snapshot, where there is not much drawn on the left and right border sides of the screen
bottom line: when using its kind of a trade off ... |
Ok, thanks a lot! I thought it was the first time I see it that way... Maybe because my snapshot starts from the intro scren, not the intro image as before... |
exactly... also when loading with What could be done is to not reset Or maybe a |
I think the aspect ratio should always be preserved no matter what... No reason to have a distorted image! :) |
ok I see will create a separate issue ... |
Great! |
68030 has no internal FPU ... only 68040 starts with an embedded one I think... concerning the crashes on sysinfo which probably does some extra extensive tests which then lead to a guru meditation ...see here dirkwhoffmann/vAmiga#732 dirk already set up toni wilens cpu tester to iron them out ... probably the crashes will then go away when dirk fixes a bunch of them |
Yes, I know about the FPU, I meant that Settlers is able to detect 68881 or 68882 but doesn't seem to do anything useful with them. Indeed let's hope this guru meditation thing can be solved! I have another problem... I tried to push Settlers to its limit with map size 8 and experienced sluggish sound again with a low number of frames... Even when I load the snapshot again (beginning of Settlers prior to choosing a map size) the problem remains... Even after restarting the phone!! |
Getting worse... Not only everything is saturated (to few rendered frames whatever the game, reset...) but also my Interceptor snapshot start working fine for a few seconds then... Guru meditation! This never happened before... |
And suddenly after one hour of sluggishness, now sound and speed is OK again. I didn't do anything! But the guru mediation on Interceptor snapshot is still there... |
I will looking into the speed thing on a modern i5 gen 11 laptop and watch the rendered frames under different configurations despite that: speed should be comparable to 68000 because it is the same way of implementation but maybe still a bit buggy or has still some sort of debug code or superfluous code paths in it ... I wouldn't test too much by now ... it is still full of bugs and untested as dirk said much better is it to solve all the errors which tonis cpu_tester reports ... after that it should theoretically not again guru |
I have saturation problems even with 68000 now... |
Is the regular version different? |
I'm not too sure. Long time didn't use the regular version, my snapshots are not valid any more... |
I think it found the guru problem. |
great finding ... maybe snapshot restore does not correctly restore the cpu type in the describe use case and leads to the guru ... @dirkwhoffmann possibly a fault in the core ? for the framerate drops I guess thermal throtteling is a candidate to explain the cause for it .... found a german article on the net which says that z3 fold while overall being a great phone is plagued with aggressive thermal throtteling... and it also says that one can disable some settings to partially avoid this |
Wow... Many thanks aks for this, I didn't know. I'm so disappointed... You buy the flaghsip model, you pay a bomb, and you still have to deal with issues like this! I activated the "enhanced processing" option (they say it works for everything except games, I hope vAmigaWeb is not reported as a game?). Now it seems from the console that I have no frame drops. Also it is morning, the phone could cool off for the whole night, so maybe it plays a role... Even when I have no frame drops the sound is not perfect, some glitches here and there in Settlers music... Is it the case for you as well? Cheers |
I spoke too fast... Even with this option enabled, I'm back to heavy frame drops... :( What I don't get is that Retroarch / puae (this again, sorry) never ever game me this. I just tried it again, so the phone is in the same state... 68030, 35Mhz cycle-exact, Settlers works like a charm in perfect sound... For the same kind of processor load, right? |
for the guru issue you found I asked dirk whether he sees something ... for the performance thing:
|
|
I have just tried both versions side by side in comparable situations: 68000 (only option in the regular version anyway), 28Mhz, Settlers. |
switched the same setup to 28 Mhz ... use case with use case with bottom line:
|
Ah, thanks, so it is pretty consistent with my findings! Maybe not Z3's fault after all! :) |
@Vweber73 you wanted a 68020 CPU ? for the settlers ?
at least sysinfo reports now with the above setting an 68EC020
pushed an early preview to uat
be aware the 68020 CPU implementation is still under heavy construction but already working somehow...
also follow progress on dirkwhoffmann/vAmiga#728
The text was updated successfully, but these errors were encountered: