Quote from Scawen :

No... tyre warmers in racing are changing with the new tyre physics (most classes don't have tyre warmers any more). I don't know if we'll have adjustable ones in the future but I don't want to get into that now, implementing it into multiplayer packets to pass the information around and so on, it would take more time.

Anyway, the same problem doesn't exist in racing - people don't start doing donuts and all manner of crazy looking things to warm up their tyres before they start going round the track.

Except for some drifters and 'special' people during qualifications :P

Quote from Woz :

Scawen, finally got around to testing the checkpoint stuff.

I created a track with Start, CP1, CP2 and End. All fine.

If I delete CP1 and start the race it gives warning that CP1 not found. You do not get a split if you cross CP2 as it appears to want to detect crossing CP1 first.

I could get around this by always having the 3 on track and then when I want to move one just delete old position and add at new.

With the quick play around I have had I have found it does not always detect crossing the checkpoint. Not sure if I had too close together as all were within 1-200M of each other when I was testing as no wheel at the mo. I was testing with a mini "oval" on Fern Bay on mini loop people always asked to open on that track

Looks like I will not have time for this project for a while so if I am only one asking about dynamic checkpoint placement dont put any priority on it. I could always implement my own checkpoints using other items such as road marking items and collision detection on those for checkpoint processing when I can get back to this.

I think he means say you pass through checkpoint 1 first time, try moving it afterwards, does it work in 'lap 2' in the new position? If so you could make a route yourself using multiple laps by moving each checkpoint as you go through them. Only problem would be it would only work for 1 car in race afaik

Quote from Bass-Driver :

hi
I found a LX4 3d modeling bug
If someone hit the LX4 backend u get something like this.(see attachment)

i know its hard to fix and its not something to worry about it , i just thought to report it here.

And the rear wheels can still spin and have grip whilst not attached to the car visually :P

ghowden
24
UK

FBM@BL1 = not set
XFG@BL1 = 1.38.28
XRT@SO1 = not set
FXR@AS3 = 2.04.57 <---LOL!

I don't think I can beat the XFG@BL1 without lots of practice, the others I'll set some times tomorrow

From liverpool:
53ms
69ms
84ms

From London:
17ms
40ms
44ms


All averages from 6 pings

Changes needed for z32:

Still wrong code for VW in Car.java, should be VWS (non essential)

In SetDirectCameraRequest, CameraPositionResponse and StateResponse the line:


Is no longer needed as the flag can be removed (Shouldn't the flags be in some kind of ISS State enum anyway?)

In OutGaugeResponse the following two lines need to be added:


Attached is the new code for RaceStartResponse to be cleaned up to be inkeeping with the style of the rest of the library

Assuming everything was implemented for z28 this is all that needs doing/testing for it to work with z32

I noticed you updated the Track list, how about the MessageToConnectionRequest? Is that alright?

Fixed a couple of spelling mistakes and what looks like a numbering issue for Aston in the Track class, also added all the new open configs

EDIT:
new MessageToConnectionRequest with larger message size and sound field

Last edited by ghowden, Thu 5 May 2011, 13:23.

Quote from Brilwing :

I have created a new development branch for the Z30+ changes add have added your changes (with some modifications):
https://jinsim.svn.sourceforge.net/svnroot/jinsim/branch/z30

I have not applied the changes in the OutGaugeResponse file, cause the current version is correct.

(If you want build the jinsim jar use gradle (http://www.gradle.org/))

Thats great thanks, its ok I merge the source with my code and build in eclipse in one final jar using fatjar

Is there any other changes needed for z31? I looked at changelog and it seemed to be only a couple of length changes

Here is the latest source code plus my collision packet code seems to work fine now. Learnt bitwise operators in java at long last lol

Quote from morpha :

You have to initialise the connection with ISF_CON for LFS to send CONs

ah great work , added the flag for collision events. Now I get buffer underruns, need to have a look at my response code now

EDIT: Buffer underrun fixed, I thought char would mean char, but no it's a byte. Closing speed seems to be returning 0 though, still needs more work

I reckon its java not having unsigned stuff messing with me, ffs

Last edited by ghowden, Tue 3 May 2011, 15:10.

Here's what I have for the new car contact stuff, I added COLLISION_REPORT(50) to the PacketType enum and registeredTypes.put(PacketType.COLLISION_REPORT, CollisionResponse.class); to ResponseFactory too. Testing shows nothing happening at all atm

Last edited by ghowden, Tue 3 May 2011, 13:49.

You have:


in that version for OutGaugeResponse, shouldn't the DL_* ones be:

seeing as the documentation says its bit numbers?

EDIT:
Yes it is, worked out dashlights wasn't in flasg (duh), then tried working with dashlights, then realised its in showlights lol xD I blame the alcohol. Anyways works fine now, thanks a lot Now to the program itself lol

Last edited by ghowden, Sun 1 May 2011, 01:58.

Yeah sorry, I decided to try updating jinsim instead of using a relay seeing as I'm trying to keep the thing pure java. Where can I find the technical details about insim/outgauge?

Well I've just tried this:


With the values found here:

http://pyinsim.codeplex.com/So ... b8d279#pyinsim%2finsim.py

Which I'm assuming is current.

It prints nothing at all in normal use when flicking lights/indicators, but pressing 1/2 seems to give random flags and getting wrong route/restricted area seems to do the same. Even entering pits or pressing Esc seems to give results, anything but what I expected really. BAR and KM work tho.

Am I still using outdated flag values or has outgauage packets changed too and I need to fix parsing of them?

Ah thats great didn't know it was outdated code, the main download link pointed to 0.3, I went and got 0.5. Looking at this thread there seems to be a 0.6 out but I can't find source for it.

I'll use the relay for now, I can't seem to find the specs for outgauge atm, but I'll have a go at updating jinsim for new patches when I've finished my program.

Last edited by ghowden, Fri 29 Apr 2011, 21:44.

So basically:


would check if the pressure is in bar?

Would clear what I have up a touch lol


edit:
Think I'm doing something wrong, the only flags I seem to be able to get are BAR and KM :/

Last edited by ghowden, Fri 29 Apr 2011, 16:49.

Ah OK makes sense, I haven't done algorithm stuff for ages, am I right in thinking to get the individual flags that are on I try taking away the largest flag number, if the result is minus it means its false, if its positive I make the flag number that amount less and then do the same with each of the rest of the flags in reverse number order?

Just looking through outguage, I understand what most of the flags are, except OG_1 OG_2 OG_3 OG_4, what are they?

My first skin, rendered. Only 2h 47mins!