02-18-2014, 11:29 PM -
(02-18-2014, 08:38 PM)ssshadow Wrote: Ok. Should the new option to log all syscalls be checked in order to better follow what happens when you submit a log?
(02-18-2014, 09:02 PM)AlexAltea Wrote:I just left off, it slowed down too much.(02-18-2014, 05:59 PM)Dante38490 Wrote:(02-18-2014, 05:05 PM)ssshadow Wrote: This might be a pain to administer though. Some people might get additional errors due to missconfiguration and such, and even just a single new revision might make half the old logs irrelevant. Perhaps there is a different way of organizing things?
I do not think normally we should all have the same result on the same games.
Nope, that's not right
Different resolutions affect the stuff like cellGcmSysstuff different results.
Different GPUs produce different behaviours in the OpenGL thread.
Different OS may also produce different behaviours.
Different releases (x86 or x64) also produce different results. However in the future the 32 bits version will be probably removed.
Well, and then we have the threading issues which sometimes I'd swear that these are just pure evil randomness.
Anyway, I don't think this differences are a big problem for your repo.
(02-18-2014, 08:38 PM)ssshadow Wrote: Ok. Should the new option to log all syscalls be checked in order to better follow what happens when you submit a log?
I think, it would be better to keep that option disabled. That would make the logs massive, and probably a lot of samples / homebrews that used to work will break. This option was a just a feature request by Nekotekina for testing one game, and it's not designed for having it always on.
Alex for the resolution I know, some are hombrow works only in 1080 but the rest I did not know ^ ^.