Magic Data Discussion

Interesting, thanks Turbo.

The first example of that which comes to mind is the very long pit lane exit at Monza, where the cars are not allowed back on the racing line until just before the first chicane. I'm going to go try it out!

=====================================================


Intel NUC 8i3, 8GB RAM, MS Sidewinder Wheel

Yep, very neat. Setting a value of 70 sectors for "sectors to pit end" at Monza makes the cars follow the right hand side of the track all the way to Turn 1, just like they do in real life these days.

However, they don't accelerate to full speed on pit exit

Maybe there's another value to fix that?

=====================================================


Intel NUC 8i3, 8GB RAM, MS Sidewinder Wheel

In that case I assume it would be better not to use this value and make the pitlane longer, up to the first chicane... never tried though

Well, I think we now at least probably know why the cars tended to slid off in Redgate on the Donington Park GP4 track initially, when exiting the pits.

Sorry if this has been spotted before in the case of that track and I did not realized it.

TomMK écrivait:
-------------------------------------------------------
> Yep, very neat. Setting a value of 70 sectors for
> "sectors to pit end" at Monza makes the cars
> follow the right hand side of the track all the
> way to Turn 1, just like they do in real life
> these days.
>
> However, they don't accelerate to full speed on
> pit exit
>
> Maybe there's another value to fix that?

I don't know if it works the same way than in GP3 tracks but you should have to put a "speed limit off" flag somewhere in a sector of the pitlane exit

---

There is a pit exit flag yes. The cars do accelarate from the 50mph limit to about 100mph / 120mph when they reach that flag, but then they "hesitate" and hold this speed for several sectors, rather then going to full racing speed.

Still, it's useful to understand the function, even if it is a bit limited.

=====================================================


Intel NUC 8i3, 8GB RAM, MS Sidewinder Wheel

Some investigation I did a long time ago, but it seems this particular value (air resistance) is absent from the TSM window as well.



Uploaded with ImageShack.us


My unfinished tracks: [www.grandprixgames.org]
Send bug reports and track editing questions to f1virtualblog@gmail.com

TomMK écrivait:
-------------------------------------------------------
> There is a pit exit flag yes. The cars do
> accelarate from the 50mph limit to about 100mph /
> 120mph when they reach that flag, but then they
> "hesitate" and hold this speed for several
> sectors, rather then going to full racing speed.
>
> Still, it's useful to understand the function,
> even if it is a bit limited.

Interesting... Are you sure that the pit exit is strictly a straight line after that flag ? If there is a short turn, AI cars are slowing to take the turn, even if it's really, really short (less than 1 degree)

---

Great analysis Prblanco, I'm annoyed I never saw that before! I prefer CMagic to TSM for editing Magic Data because, as above, there are some values missing from TSM that are important. TSM is good for quick tweaks when testing things, like fuel consumption etc, so it still has a purpose.

=====================================================


Intel NUC 8i3, 8GB RAM, MS Sidewinder Wheel

do all new tracks made by several people here always contain a magic data file?

Not every track, no.
Launch your Cmagic1.00/1.02, select the track file (the .dat) and click on 'edit'/'Get magic data from track file' to see whether there is a magic data included or not.

i see, thanks for letting me know.... but what happends when you put a new track without magic data in lets say s1ct01.dat? does it use the magic file of the original track (melbourne)?

You're completely right.
When a track contains no magic file, the GP4.exe will use the original magic data from track slot #1, so here: melbourne .

that's not very realistic....

Hi guys,

It's sad discussion in this topic paused recently.

The reason I bring it up is twofold.

First of all, I now use the enhanced GPxTrack to swap tracks around instead of the old school overwriting of the original tracks via copy-paste. I use Monaco 1967 as I like it very much - and it's Monaco time in a week anyway - and for some reason cars now sit 90° in the 'pit lane' instead of the Monaco standard 45°. Do you know which parameter of the magic data defines this? (I tried the Special (Monaco) setting in GP4 Builder, but it was not it.)

I tried to resolve the issue on my own, so I sort of rechecked what magic file line is what, and this is what came out:

desc1=fw dry player ?
desc2=rw
desc3=1st
desc4=2nd
desc5=3rd
desc6=4th
desc7=5th
desc8=6th
desc9=fw dry AI ?
desc10=rw
desc11=1st
desc12=2nd
desc13=3rd
desc14=4th
desc15=5th
desc16=6th
desc17=fw wet player ?
desc18=rw
desc19=1st
desc20=2nd
desc21=3rd
desc22=4th
desc23=5th
desc24=6th
desc25=brake bias dry
desc26=fw wet AI ?
desc27=rw
desc28=1st
desc29=2nd
desc30=3rd
desc31=4th
desc32=5th
desc33=6th
desc34=brake bias wet
desc35=soft tyre (52-55)
desc36=hard tyre (52-55)
desc37=>= 50 tyretype 1 else 0
desc38=unused
desc39=unused
desc40=unused
desc41=unused
desc42=track grip
desc43=unused
desc44=unused
desc45=downforce
desc46=ride height
desc47=air density
desc48=fuel (for 1.0 lap)
desc49=????? - subtracted from diff between field_e2 of 2 cars and then compared to speed of first car
desc50=tyre wear player
desc51=AI aggressiveness in attacking corners (lower, more)
desc52=AI aggressiveness finetune
desc53=cc power factor ace
desc54=cc grip factor ace
desc55=cc power factor pro
desc56=cc grip factor pro
desc57=cc power factor semi-pro
desc58=cc grip factor semi-pro
desc59=cc power factor amateur
desc60=cc grip factor amateur
desc61=cc power factor rookie
desc62=cc grip factor rookie
desc63=random perf range min
desc64=random perf range max
desc65=nr of AI errors
desc66=nr of sectors checked by AI after spin
desc67=sectors to pit in begin
desc68=sectors to pit in end
desc69=pre pit speed limit
desc70=fuel consumption player
desc71=fuel consumption AI
desc72=tyre wear AI
desc73=????? - a segment nr before which flag 0x80 in car.flags_ce is not cleared
desc74=????? - timing factor? (dw)
desc75=????? - timing factor finetune? (dw)
desc76=????? - helps decide if a tyre set needs changing? (dw)
desc77=????? - same as above (dw)
desc78=rain chance
desc79=????? - segment nr (start of some range)
desc80=????? - segment nr (end of some range)
desc81=AI race grip
desc82=????? - unk (dw)
desc83=????? - unk (dw)
desc84=black flag penalty
desc85=black flag
desc86=????? - unk (dw)
desc87=????? - unk (dw)
desc88=????? - new (dw)
desc89=????? - new (dw)
desc90=????? - new (dw)
desc91=????? - new (dw)
desc92=????? - new (dw)
desc93=????? - new (dw)
desc94=????? - new (dw)
desc95=????? - new (dw)
desc96=unused
desc97=unused
desc98=unused
desc99=unused
desc100=unused
desc101=unused
desc102=pitstop group 1 %
desc103=stop 1
desc104=pit window 1
desc105=
desc106=
desc107=
desc108=
desc109=
desc110=pitstop group 2 %
desc111=stop 1
desc112=pit window 1
desc113=stop 2
desc114=pit window 2
desc115=
desc116=
desc117=
desc118=pitstop group 3 %
desc119=stop 1
desc120=pit window 1
desc121=stop 2
desc122=pit window 2
desc123=stop 3
desc124=pit window 3
desc125=
desc126=failure chance : suspension
desc127=failure chance : loosewheel
desc128=failure chance : puncture
desc129=failure chance : engine
desc130=failure chance : transmission
desc131=failure chance : oilleak/waterleak
desc132=failure chance : throttle/brake
desc133=failure chance : electrics
desc134=unused
desc135=unused
desc136=unused
desc137=unused
desc138=????? - bump factor
desc139=????? - bump shift

Based on TomMK's excellent work exclusively. This is just an overview and I'd like if discussions on the values would restart.

As we can see, there are only 23 lines remaining, of which we have no idea, what they are. (The '?????' ones to make it easier to see.)

maybe the easiest way would be to simply include the original monaco magic data to the file ? you could do this by the help of CMagic4.exe. once it is started go to the edit-menu and choose "create magic file from gp4.exe". now you can choose the desired slot (7 for monaco) and you get a txt-file with the original monaco-magic data. this file you can import into the .dat with CMagic again.

maybe I should add, before you create the mentioned magic-file you may want to load the .dat into cmagic, because that way the new file is created in the same directory as the .dat, so its easy to find. if no .dat is loaded, the file is created in the CMagic4-directory.

- - - - - - - - - - - -
please no PMs; but you're welcome at: [addie3 at waa63 dot ch] and [www.waa63.ch]



Edited 1 time(s). Last edit at 05/18/2013 03:47PM by addie.

I believe it's Desc93 for garage car angle

Lo2k Wrote:
-------------------------------------------------------
> I believe it's Desc93 for garage car angle


actually you need to set 90..95, as far as I recall ?!

from my notes (values as seen in original tracks):
90: 0, except monaco: -312 (“handbrake”)
91: 1814, except monaco: 840
92: 896, except monaco: 512
93: 0, except monaco: 8192
94: 0, except monaco: 640
95: 0, except monaco: 864

- - - - - - - - - - - -
please no PMs; but you're welcome at: [addie3 at waa63 dot ch] and [www.waa63.ch]

8192 sounds like 45°.

René Smit, Independent Software Developer.
Download my GPx tools here.

desc93 is for the garage car angle
desc90 is for the garage car "depth" (how deep the car will be in the garage) (as far i can remember...or the other way around... )

for desc51 i found out, that if you set it on 0, the ai-cars will drive fast times from the beginnig of a session (training,quali).
with higher values they will drive their fastest times towards the end of a session.
so it raises the track grip or the skills of the ai´s

matt



Edited 1 time(s). Last edit at 05/18/2013 08:24PM by schroeder.