Jump to content

Planescape: Torment - controls freezing


lapis

Recommended Posts

Posted

I have installed GemRB and Planescape:Torment to my HTC EVO 3D phone. It looks nice (but a bit small), but I have problems with freezing controls. After a short time of playing (usually when I click to a portrait in bottom of the screen), all buttons stop responding. The game still runs, but no button on the screen work, I can only walk by clicking on the screen. Then I have to kill the process and start GemRB again.

 

How to fix this issue?

 

I tried both GemRB 0.6.6 from market and latest binary of 0.7.0 from sourceforge but it is still the same.

The game has widescreen fix applied and resolution 800x480 fullscreen (however the display is 960x540, it looks fine).

Posted

Something must go wrong in the guiscripts, but we can't help if we don't know what. Get alogcat and maybe you'll be able to catch the python runtime error that causes it.

Posted

I found that it happens when I click any portrait at bottom of the screen and then move mouse out of there, without switching the portrait to other position. It happenes quite often in tablet mouse emulation mode, but when I use touchpad mode, I can just avoid clicking to portraits area... Taping the portrait and switching its position with other portrait fixes that problem and the game is usable again.

 

Tablet mouse emulation mode is easier to use. Touchpad mode is slower to use, but more precise....

 

What resolution do you recommend for playing on EVO 3D? 960x540 looks nice (native resolution), 800x480 makes controls and text a bit bigger, but more ugly.

 

Is there any possibility how to increase font size?

Posted

I tried setting a TTF font (DroidSans in system fonts directory or Arial copied from Windows) according to alx3apps' guide, but it seems that I have an encoding problem. I have Czech language loaded into the game and TTF fonts don't display Czech characters properly. Is it possible to define a code page (windows-1250) or do I need some special fonts?

 

Avenger: Try to set Tablet mouse emulation method, then just tap to a portrait at the botttom and then try tapping to some other place. Controls then don't work - buttons just push in and stay pushed without any action...

Posted

at the bottom of the TTF page on the wiki there is a blurb (probably somewhat inaccurate) about non-ASCII languages. Basically the ttf plugin just creates a sprite map for whatever values are passed via the fonts.2da file. most TTF fonts (if not all) those values will map directly to ASCII characters.

 

Forgive me if this is an ignorant statement, but i thought Czech used only characters that are part of the extended ASCII table. so I would think this should work as it is... If BAM fonts are working for you the only thing I can think of is maybe that font you are using is lacking those glyphs??? (doubtful)

 

can you be more specific about what it is doing? maybe a screenshot?

 

Also I dont think we know what "tablet mouse emulation is" that isn't part of gemrb. avenger is likely testing on his computer.

Posted

indeed those are quite different (with some overlap)

 

so is this an issue with the font files not being latin2 then? I'm perhaps a bit ignorant about fonts and character encodings for how much work i've done with the gemrb font system :)

Posted

Yes, Czech is just extended ASCII charset, it is 8 bit (so no UNICODE or UTF). There are 3 standards - windows-1250, cp-852 (latin2) and iso-8859-2. Characters are overlapping, so standard letters are displayed always correctly, but national characters are bad if wrong coding is used.

Texts for PS:T are in win-1250 codepage and GemRB probably reads it as cp-852 (this one was used in DOS or Linux) or iso-8859-2 (this was used in Linux too).

If I would have some tool to decompile Dialog.TLK, I would be able to convert the codepage of the text. Otherwise I probably need some special font, I am not sure.

 

SyntaxError: "tablet mouse emulation" is probably Android specific. It is in GemRB's options -> Mouse emulation -> Mouse emulation mode (it also asks for this when you run GemRB on Android for first time). Tablet mode simulates mouse clicks in place where I tap by a finger, touchpad mode uses relative method for moving the cursor and tapping simulates click in place where the cursor is.

 

Anyhow, problems with buttons not working after clicking to portrait is not related to language installed (it does the same thing with original English game texts) and I can imagine that it probably doesn't occur on a computer, but rather on an Android touch-screen device.

Posted

it sounds like you need to take your original issue to the android developer (Beholder)

 

latin2 and latin1/extended ascii are not compatible. all GemRB does for text is read a byte from dialog.tlk and use it as an index to lookup the corresponding glyph. TTF plugin isnt currently compatible with non latin1 compatible text at this time. I'm not sure when it may become compatible either. GemRB has much work to be done before it is truly internationalized unfortunately.

 

EDIT:

reading the sdl_ttf documentation it says it always interprets text as latin1/utf/unicode. i had hopped it used a system setting or something more useful. we are planing on using freetype library directly at some point and i suspect we will be able to set the encoding at that point.

Posted

Hmm, I managed to get it working with czech language. I converted Dialog.tlk from win-1250 to iso-8859-2 codepage and defined to use some special Latin2 Arial font and it seems to work properly with all czech letters now. However some codepage settings in GemRB.txt would be useful in future builds.

 

I don't have any screenshoting tool installed yet, but I made a photo using a camera

http://img515.imageshack.us/img515/48/pstfoto.jpg

Posted

If the problem is capitals (most buttons), then maybe the charset setting in cfg can help.

Like:

 


[charset]
Letter1 Á,á
Letter2 É,é
Letter3 Ó,ó
...

Posted

Does GemRB.cfg support such character remappinng?

Unfortunatelly problem is not only with capitals, but all letters like: š ž ť and with using normal fonts also all others like ěčřýáíéůú (including capitals)

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...