Carrier - text does not display correctly with dynarec enabled

gechdcb / nulldc

Automatically exported from code.google.com/p/nulldc

0 stars 0 forks source link

Carrier - text does not display correctly with dynarec enabled #258

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

In-game text appears garbled with dynarec enabled.
Text appears correctly with dynarec disabled.
See attached pics.

Tested on r78, NTSC GDI version.

Original issue reported on code.google.com by matbur...@gmail.com on 13 Oct 2010 at 1:48

Attachments:

[Carrier dynarec on.jpg](https://storage.googleapis.com/google-code-attachments/nulldc/issue-258/comment-0/Carrier dynarec on.jpg)
[Carrier dynarec off.jpg](https://storage.googleapis.com/google-code-attachments/nulldc/issue-258/comment-0/Carrier dynarec off.jpg)

GoogleCodeExporter commented 9 years ago

Damn, did you really have to spam-test nullDC? now i have to spam-fix ... :p
Yet another instance of the classic dynarec bugs ... OKAY I'LL FIX THEM.

Original comment by drkIIRaziel on 16 Oct 2010 at 11:58

Changed state: Accepted
Added labels: Type-Defect, Priority-Critical, emu-sh4-rec
Removed labels: Type-Enhancement, Priority-Low

GoogleCodeExporter commented 9 years ago

Heh, I didn't spam-test, I've been testing over about 3 months.
Instead, I spam-uploaded issues :)

Still, I tested 300+ games and relative to that I haven't uploaded that many 
issues, so on the bright side there's plenty which DOES work well in nullDC.

Original comment by matbur...@gmail.com on 16 Oct 2010 at 1:06

GoogleCodeExporter commented 9 years ago

We really need to fixup ndcs site and make a compatibility database :/

Original comment by drkIIRaziel on 16 Oct 2010 at 2:16

GoogleCodeExporter commented 9 years ago

Recheck with r79 !

Original comment by drkIIRaziel on 20 Oct 2010 at 10:33

GoogleCodeExporter commented 9 years ago

Still an issue in r84.

Original comment by matbur...@gmail.com on 27 Oct 2010 at 6:20

GoogleCodeExporter commented 9 years ago

Still exists in r111 and r134 :(

Original comment by pav...@gmail.com on 2 Jun 2011 at 4:17

GoogleCodeExporter commented 9 years ago

Original comment by KrossX3 on 3 Jun 2011 at 3:21

Added labels: Restrict-AddIssueComment-Commit

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Here's a temp binary with the fix until Drk confirm the changes.

Original comment by Dimitris...@gmail.com on 3 Jun 2011 at 2:30

Attachments:

nullDC_Win32_Release-NoTrace.zip

GoogleCodeExporter commented 9 years ago

Unrestricted again. So users can post feedback on the new binary.

Original comment by KrossX3 on 3 Jun 2011 at 3:55

Removed labels: Restrict-AddIssueComment-Commit

GoogleCodeExporter commented 9 years ago

I can verify that the changes are fine (talked with dimitris over msn :p). 
Apparently an error message was disabled on the dynarec making this bug (and 
possibly others) not properly notify us. The binary should have both this bug 
fix, and the error check properly enabled again !

Original comment by drkIIRaziel on 3 Jun 2011 at 4:46

GoogleCodeExporter commented 9 years ago

Well then, commit while I mark this as fixed. :p

Original comment by Mr.PsyMan on 3 Jun 2011 at 8:58

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Issue 257 has been merged into this issue.

Original comment by Mr.PsyMan on 3 Jun 2011 at 8:59