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

Crash when going into ingame settings (Bad UTF-8 continuation Byte) #385

Closed
DirtGamer301 opened this Issue Aug 12, 2015 · 12 comments

Comments

Projects
None yet
5 participants
@DirtGamer301

DirtGamer301 commented Aug 12, 2015

So, I had it since ingame settings were being added and yet none of the advices helped.

The problem is simple to explain, but you most likely won't be able to reproduce it.
I press the "settings" tab and then the game crashed, giving me an error message: "Bad UTF-8 continuation Byte"
RoR.log: http://www.mediafire.com/download/fua4zd123lh5qvo/RoR.log

Cache clearing, regenerating, deleting whole RoR 0.4 folder and running RoRConfig, deleting the stuff in RoR 0.4 folder and running RoRConfig didn't help.

@Hiradur

This comment has been minimized.

Show comment
Hide comment
@Hiradur

Hiradur Aug 12, 2015

Contributor

Is 'bandit' your real Windows user name? What system locale do you use? Perhaps there is a setting in RoR.cfg using an Umlaut or other non-ASCII characters?

Contributor

Hiradur commented Aug 12, 2015

Is 'bandit' your real Windows user name? What system locale do you use? Perhaps there is a setting in RoR.cfg using an Umlaut or other non-ASCII characters?

@DirtGamer301

This comment has been minimized.

Show comment
Hide comment
@DirtGamer301

DirtGamer301 Aug 12, 2015

Yes, from "Smokey and the bandit" ^^ Couldn't think of anything better

I installed all RoR versions on C.

I found this in RoR,cfg:
Program Path=c:\progra2\rigsof1
Replay mode=Yes
Resources Path=c:\progra2\rigsof1\resources\

And this:
plugins.cfg=C:\PROGRA2\RIGSOF1\plugins.cfg

It btw says it's a runtime error so I did what I always did when having a runtime error, too, but it didn't help either (worked with "normal" runtime errors).

DirtGamer301 commented Aug 12, 2015

Yes, from "Smokey and the bandit" ^^ Couldn't think of anything better

I installed all RoR versions on C.

I found this in RoR,cfg:
Program Path=c:\progra2\rigsof1
Replay mode=Yes
Resources Path=c:\progra2\rigsof1\resources\

And this:
plugins.cfg=C:\PROGRA2\RIGSOF1\plugins.cfg

It btw says it's a runtime error so I did what I always did when having a runtime error, too, but it didn't help either (worked with "normal" runtime errors).

@Max98 Max98 added the bug label Aug 12, 2015

@Max98 Max98 added this to the Post-Nextstable milestone Aug 12, 2015

@Michael10055

This comment has been minimized.

Show comment
Hide comment
@Michael10055

Michael10055 Aug 12, 2015

Contributor

This same error also happens in .truck files: #364

Contributor

Michael10055 commented Aug 12, 2015

This same error also happens in .truck files: #364

@Hiradur Hiradur modified the milestones: Post-Nextstable, 0.4.6.0 Oct 24, 2015

@Hiradur

This comment has been minimized.

Show comment
Hide comment
@Hiradur

Hiradur Nov 18, 2015

Contributor

@DirtGamer301 Is that the correct log? It looks like a normal session without a crash to me.

Contributor

Hiradur commented Nov 18, 2015

@DirtGamer301 Is that the correct log? It looks like a normal session without a crash to me.

@DirtGamer301

This comment has been minimized.

Show comment
Hide comment
@DirtGamer301

DirtGamer301 Nov 18, 2015

Oh, are there any other information beside gameplay in RoR.log?
Idk, but maybe this RoR.log was created the session before and as I didn't play to get this log (only pressed on the "Settings" tab) it might not be created.
I'd then have to upload another file, but which one?

DirtGamer301 commented Nov 18, 2015

Oh, are there any other information beside gameplay in RoR.log?
Idk, but maybe this RoR.log was created the session before and as I didn't play to get this log (only pressed on the "Settings" tab) it might not be created.
I'd then have to upload another file, but which one?

@Hiradur

This comment has been minimized.

Show comment
Hide comment
@Hiradur

Hiradur Nov 18, 2015

Contributor

upload the whole logs folder, maybe there is something useful in one of the logs.

Contributor

Hiradur commented Nov 18, 2015

upload the whole logs folder, maybe there is something useful in one of the logs.

@DirtGamer301

This comment has been minimized.

Show comment
Hide comment
@DirtGamer301

DirtGamer301 Nov 18, 2015

I'll do so tomorrow, I sadly have nomore time today.

DirtGamer301 commented Nov 18, 2015

I'll do so tomorrow, I sadly have nomore time today.

@DirtGamer301

This comment has been minimized.

Show comment
Hide comment
@DirtGamer301

DirtGamer301 commented Nov 19, 2015

@Hiradur

This comment has been minimized.

Show comment
Hide comment
@Hiradur

Hiradur Nov 19, 2015

Contributor

hmm, I couldn't spot anything suspicious. Can you upload your config folder, please?

Contributor

Hiradur commented Nov 19, 2015

hmm, I couldn't spot anything suspicious. Can you upload your config folder, please?

@DirtGamer301

This comment has been minimized.

Show comment
Hide comment
@DirtGamer301

DirtGamer301 commented Nov 19, 2015

@Hiradur

This comment has been minimized.

Show comment
Hide comment
@Hiradur

Hiradur Nov 19, 2015

Contributor

Couldn't spot anything special here either. The only thing which puts me off are these weird Windows 8.3 file path abbreviations such as c:\progra~2\rigsof~1\. You could try to replace them with the full path instead. What version of Windows are you using?

I don't think a video could help here. A Remote session could do maybe but since I'm a Linux guy I'm not sure if I could solve it.

Contributor

Hiradur commented Nov 19, 2015

Couldn't spot anything special here either. The only thing which puts me off are these weird Windows 8.3 file path abbreviations such as c:\progra~2\rigsof~1\. You could try to replace them with the full path instead. What version of Windows are you using?

I don't think a video could help here. A Remote session could do maybe but since I'm a Linux guy I'm not sure if I could solve it.

@DirtGamer301

This comment has been minimized.

Show comment
Hide comment
@DirtGamer301

DirtGamer301 Nov 19, 2015

I use Windows 7.
I'll give the file path renaming a try.

DirtGamer301 commented Nov 19, 2015

I use Windows 7.
I'll give the file path renaming a try.

@Hiradur Hiradur changed the title from Game crashed when going into ingame settings to Crash when going into ingame settings (Bad UTF-8 Bad UTF-8 continuation Byte) Nov 22, 2015

@Hiradur Hiradur changed the title from Crash when going into ingame settings (Bad UTF-8 Bad UTF-8 continuation Byte) to Crash when going into ingame settings (Bad UTF-8 continuation Byte) Nov 22, 2015

@only-a-ptr only-a-ptr self-assigned this Jan 31, 2016

only-a-ptr added a commit to only-a-ptr/rigs-of-rods that referenced this issue Jan 31, 2016

[fix] Added full-scale UTF-8 sanitization; no more crashes.
This resolves the inflamous "Bad UTF-8 continuation byte" error dialog. Fixes RigsOfRods#237 RigsOfRods#385 RigsOfRods#664 RigsOfRods#445 RigsOfRods#364

Incorporated UTFCPP library: (utfcpp.sourceforge.net/; License: boost) and added UTF-8 sanitization to all text-file processing.

@InvalidUTF8character: YOU SHALL NOT PASS! :D
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment