Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
WipEout Pure
#61
1120 was ok. I've tested 1140 and 1142 and it crashes. I will try to pinpoint where it starts. No complaints about speed (45 - 50 fps with frameskip)
Reply
#62
Would be great if you could narrow it down a bit more.
Reply
#63
No problem here on windows (build 1142). Also the blooming is slightly better, now there is just some sort of graphical issue at 3/4 of the screen (some kind of reflection??)


Attached Files Thumbnail(s)
   
Reply
#64
from catlog:
Code:
03-11 18:56:46.497 E/NativeApp(15338): 56:46:498 Main thread E[G3D]: jni/../../GPU/GLES/DisplayListInterpreter.cpp:470 Signal without wait. signal/end: 0200 0000 03-11 18:56:46.512 F/libc (15338): Fatal signal 11 (SIGSEGV) at 0x00000005 (code=1), thread 15351 (Thread-596)
cant post the entire log.its 1.6mb
Reply
#65
(03-11-2013, 03:57 PM)ufdada Wrote: No problem here on windows (build 1142). Also the blooming is slightly better, now there is just some sort of graphical issue at 3/4 of the screen (some kind of reflection??)

That looks like it's actually gotten more broken Tongue Probably raven02's hacks to fix Saint Seiya character scaling. Will really need to look into framebuffer sizing more...
Reply
#66
(03-11-2013, 04:04 PM)sfageas Wrote: from catlog:
Code:
03-11 18:56:46.497 E/NativeApp(15338): 56:46:498 Main thread E[G3D]: jni/../../GPU/GLES/DisplayListInterpreter.cpp:470 Signal without wait. signal/end: 0200 0000 03-11 18:56:46.512 F/libc (15338): Fatal signal 11 (SIGSEGV) at 0x00000005 (code=1), thread 15351 (Thread-596)
cant post the entire log.its 1.6mb

No need to post the log, I just need to know the exact first build that's broken.
Reply
#67
I've tested builds and here my results: 1124 - OK, 1130 looks like Sfageas was right - there is slowdown about 5 fps and since 1132 crashes occurs. Hope this helps.
Reply
#68
I think I've worked around the crash in 1143 (and a better fix in the next one).

Will look into the slowdown.
Reply
#69
still crashing v0.6-1144-gac47d74
Reply
#70
Now played about 5 races without crash (build 1145). Looks good Smile. But since 1142 the pads are all square (the ones for boost usually are arrows and those for power-ups are x )


Attached Files Thumbnail(s)
   
Reply
#71
Yeah, looking into the pads, probably my alpha testing hack, grrr
Reply
#72
okay, fixed in the next build.
Reply
#73
(03-11-2013, 05:38 PM)Henrik Wrote: Yeah, looking into the pads, probably my alpha testing hack, grrr

Wasn´t probably as useless as expected Wink
Reply
#74
Actually I just had a bug, but I turned off a couple of cases that aren't 100% safe too.
Reply
#75
1147 crashes, much faster (about 55 fps), and new graphical artefacts (instead arrows for boost and crosses for weapon pickup now squares)
edit: sorry, have not seen couple of posts before.
Reply


Forum Jump: