CTRL + right click to copy a colour
SHIFT + right click to paste a colour
The shadows are all done a very good way in the new version I am working on, but it is totally impossible to update the public version with the new shadows. Eric is working on all the tracks to get them working with the new shadows. It's the thing I am trying to get back to.
I'd really like to do Arabic at some time. It's just the sort of thing I like to do because I like LFS to be accessible to everyone and I'd be interested in learning how the Arabic alphabet works. But it is much more difficult than you imagine. We are talking weeks of work for me before you guys can start to translate it. Of course languages like Arabic and Hebrew have the difficulty of being right-to-left text (but with occasional left to right Latin text within that) and this means a lot of rewriting of many functions in Live for Speed.
There will be a lot of studying for me to do and a lot of problems to solve. I can't just click my fingers and magically all the code is done.
Now, I hope you will understand, I am in the middle of some extremely important graphical work and need to get the tyre physics finished. This must be done or Live for Speed sales will dry up completely and we will have to go and get another job. There is no doubt at all, this is a higher priority than adding a couple of tricky languages.
Unfortunately I was interrupted by someone taking our servers down two weeks ago, so I had to stop all the work I was doing and make a new patch in this old version of LFS which can resist the attacks. So that attack has slowed my development by maybe three weeks so everything that I will do in future will come a little later than it would have been
The new PMO_POSITION packet does have the Zbyte set, but I don't that is what you are asking.
I can't set the Zbyte in the reporting AXM in the case of a dedicated host receiving the packet, as it doesn't know where the ground level is.
I'm getting a bit confused trying to think of when that Zbyte adjustment could be done and when it would need to be done. Maybe I need a more specific case to try and understand where it would be helpful and to think if it can be done without causing problems.
One thing to note though, it is acceptable and usually OK to simply use the value 240. From the notes:
It seems from this crash address that LFS was loading an object and crashed while checking for a type of reflection material that it can do a better way now.
I think when you first open LFS, in the first instant it loads humans, car objects and the helmet.
As you say it works on a fresh install, could it be you had some VOB mods installed before? I suppose it is possible that a VOB mod could be incorrectly formed in such a way that it didn't crash before but does crash in this new function.
I'll try to figure out exactly which line it crashed on but it would be interesting to know if a modified model was to blame, and why it doesn't crash on most installs.
I have heard that from one other person. I asked for more information but he wasn't able to give it and just reverted to the old version. I would really like to have this information so I can fix the bug. Otherwise the crash will still be there when we release the official update!
What I need to know is:
- Crash offset or crash address
- Exception code
In older versions of Windows the information was offered to you in the crash dialog when you pressed "more info" or similar. I think in more recent versions of Windows you can find the information in an event log, accessed through control panel.
If you can give me this information that would be great and I can try to find out what causes the problem. If you would like more information on how to find the crash address, please tell us you Windows version.
Information: We did intend to release the full version this weekend but for various reasons we have decided to go on a few more days. I hope to put another test patch here on Monday or Tuesday. But for now it seems R12 works well.
New free view camera position text command /cp
/cp will copy a text camera position to the clipboard
The resulting text can be saved in a text file, forum, etc. or into
another instance of Live for Speed to reproduce.the camera position
Many translations updated - Thank you translators!
Slight reduction in some excessively bright driver models
New value PMO_POSITION for IS_AXM packet to report a blank position
New packet IS_CIM reports a connection's interface / editor mode
That is really off topic as it's nothing to do with the test patch.
But, for a quick answer, the new tyre physics is based on a mathematical model for producing the output forces from the current state of the tyre (velocity, rotation, camber etc.) instead of a 'made up' combination of lateral and longitudinal forces from 'made up' slip curves to try to match the data. It provides a more realistic response for steering and application of throttle and brakes, affect of camber and so on. It feels good to drive but is not finished and I would like to get it done for the big update we are currently working on (which is a really important graphical update).
I guess you could find more information about the tyre model by searching for my posts, but you would have to search back quite far. I'm a bit too busy to go looking for it now.
I'm still very interested to know the error code that should now be reported with "Unknown file transfer error". Just to know if it's some kind of temporary internet issue or something that LFS needs to deal with. Only problem is I think only two people have reported it and one of them doesn't get the issue any more.
So if any of you see "Unknown file transfer error" please let us know the rest of the message that LFS now displays!
EDIT : It's when it fails to download a skin and it says: SKIN : Unknown file transfer error (X)
The X is the new part I want to know.
Test Patch R11 is now available with more graphical fixes.
Changes from 0.6R9 to 0.6R11 :
More informative error report for "Unknown file transfer error"
FIX : Lighting restored to most objects (to appear darker in shade)
FIX : Some objects at Blackwood looked the same e.g. ads over pits
FIX : XR front lights were plain white in the recent test patches
I know there are more things to fix but I wanted to get this one out more quickly so we can solve the skin download issue that affects some people. Anyone else can also benefit from the restored lighting on objects.
I think that is because of the lighting information that was removed because of changes to modeller objects.
Today I've disabled some of those modeller object changes to allow me to disable the lighting removal but there are some issues I still need to solve.
Unfortunately the code now in the public version contains an early version of some of the graphical updates that was merged in. But then the graphical updates went so much further it has become something that can't be merged in at all and for the new graphics we will be releasing new versions of all the tracks and most of the textures.
For this current update I just need to try and backtrack a little so everything looks OK with the lighting mostly restored, in a small patch.