The online racing simulator
Test Patch Y13 - East Asian Support
(119 posts, closed, started )
It works for me and looks better than before. I always used MIP bias clamp and MIP bias=0 in LfS (now using MIP=0 too).
I use WinXP32bit, 8600GT and 171.16 drivers. The global option is to force 16xAF and the LfS profile says app controlled. Also negative-MIP-bias is allowed.
Quote from aroX123 :Bringing up the Ai again
...

This is a compatible patch to support East Asian languages and brings ingame AF options, so I recommend you to list these AI bugs here.
During the check of my translations of help files I found bug which is causing LFS to crash.

Steps to reproduce:
Click one of the buttons with question mark. Staying at help screen try to reload translation (SHIFT+F5).
Attached images
HelpReloadCrash.jpg
I don't have any bugs or anything since I am actually not following this specific test patch (yet anyways), although I was wondering if Scawen could tell me the effects multibyte character sets are going to have on the InSim protocol. Will there be a way to accept or deny multibyte vs single byte characters? I would be willing to test this interface in some of the projects I have started, if you are planning on implementing it of course.
#106 - dev
Quote from yaper :During the check of my translations of help files I found bug which is causing LFS to crash.

Steps to reproduce:
Click one of the buttons with question mark. Staying at help screen try to reload translation (SHIFT+F5).

I can't reproduce this...
blackbird04217: I think insim already works with these characters? There was a picture somewhere of a guy testing LFS Buttons and they had chinese characters in them. I could be wrong?
I haven't downloaded the new patch - maybe I should start there although I haven't... Are you sure its UNICODE / multi-byte and not just the special ascii codes?
Very nice, downloading test patch now so I can try myself soonish...
Quote from detail :BTW, now when the ground objects looks better, the sky is notably low-res.

Do you mean you can adjust the sky's resolution with one of the mip bias sliders?

If that is what you mean, I can't seem to reproduce that.

It shouldn't happen anyway, because the sky is loaded as only a single texture with no mipmaps.
So then character counts are halved due to their size? Example: an ascii username is 24 characters and when using the other code pages it would only be 12 characters?
Having some strange issues with the AF too, I believe it's the same issue that STROBE is having - despite having everything set at off or application controlled on the Nvidia control panel, everything still seems to be turned on. Here's some examples, hope they help.

GFX Card: Nvidia Geforce 6800 AGP
Driver: 169.21
Mip Bias sliders are all at zero, all options in the Nvidia control panel are at "application controlled" where available

I'm seeing some people here with blurry images, but I never get this, everything is always quite clear even with everything turned off

The images: the first one is with LFS's AF turned off. The second shows it with it on 1x, you can see a slight difference but nothing really major has changed, just small subtle changes. The third image shows it at 2x - here you can see that nothing has changed at all, it's exactly the same as at 1x. This also happens on all of the remaining higher settings, exactly the same.

Strangely, if I alt-tab or ctrl+f4, and then back again, I get image 4 - everything goes very sharp and grainy. This only happens on 2x AF and upwards - at 1x and off, it doesn't

No idea if this is an LFS issue or a driver issue, but anyway...
Attached images
off.jpg
one.jpg
two.jpg
three.jpg
Quote from blackbird04217 :So then character counts are halved due to their size? Example: an ascii username is 24 characters and when using the other code pages it would only be 12 characters?

Well, user names are only in Latin but regarding driver names, yes, less characters would be available in a full double byte name.

23 bytes of space
- 2 bytes for the ^H
= 21 bytes for characters
/ 2 for double byte characters
= max 10 double byte characters in a driver name
Oh wait, I just had a sudden brainfart and fixed it. I remembered that months ago I had nHancer installed and was using that to set LFS's graphic settings, but I uninstalled it. So I thought that maybe nHancer had left something behind that was causing a confilct, so I installed it again and used it to set everything to application controlled - and bingo, LFS's AF is now responding exactly as it should

So... worth trying - if you used nHancer (or any other prog like it) at some point, try sticking it on again

Sorry for the useless post
Quote from Scawen :Well, user names are only in Latin but regarding driver names, yes, less characters would be available in a full double byte name.

23 bytes of space
- 2 bytes for the ^H
= 21 bytes for characters
/ 2 for double byte characters
= max 10 double byte characters in a driver name

Thanks for the info and quick response time, I figured this was the case and now I know...
This thread is closed

Test Patch Y13 - East Asian Support
(119 posts, closed, started )
FGED GREDG RDFGDR GSFDG