@kedy89: I'm not sure, but in the past it helped to lower the font quality by adding a Quality=0.75 (for example) in fonts.ini under the appropriate section for the font. @TGF1Driver2: This is how I intended it to work. When you do the last lap again, then at the end of it the autosave.raj (which was the old last lap) is moved to autosave1.raj, then the autosave.raj is created (which is tby SDI - Grand Prix 4
Ok, maybe you're right. After all these variables weren't designed to be driver specific but track specific.by SDI - Grand Prix 4
@Noog: I honestly have no idea about another variable for this behaviour, or if this is indeed something that happens in the code. @ParisHL: I see no logic behind setting BRMin the negative of BRMax. As far as I know, the difference (BRMax - BRMin) is the braking consistency. So what you're doing is make them brake later sometimes but also making them brake earlier sometimes. Unless you cby SDI - Grand Prix 4
The crash is because of a missing .wad file.by SDI - Grand Prix 4
BRMax would make the driver brake later most of the time, especially if BRMin is increased too. If that is too late to make the corner, he would overshoot it many times. Error Chance seems to randomly force the driver to make a mistake. With an aggressive braking range and a high error chance, I wouldn't be able to tell the actual cause if he overshoots the corner. If BRMax is too high but Bby SDI - Grand Prix 4
Please use the latest GPxPatch (4.52). If that doesn't help, post a crash log from that version.by SDI - Grand Prix 4
It is GPxPatch that reads the magic data from the track file and patches the number of laps in memory. I guess GP3 Master changes the magic data inside the executable.by SDI - Grand Prix 3
The recurring question to calibrate might have something to do with compatibility settings or GPxPatch debug mode, I'm not sure. You can try to calibrate the graphics once without GPxPatch, as it may interfere.by SDI - Grand Prix 4
It's interesting that it happens on every track, because it seems to be a problem with the track. You have a track sector with length 0 and it divides by it.by SDI - Grand Prix 4
No, unless I swap them in the code.by SDI - Grand Prix 4
See? I predicted the correct moment of overflowby SDI - Grand Prix 4
For the internal speed value 492 kph is not the maximum. The theoretical maximum is more like 561 kph (32767 * 0.3048 * 3.6 / 64).by SDI - Grand Prix 4
That's not strange because the power is randomized (reduced by a small random amount). If you want to make the cars faster perhaps you can play with the physics editor? Maybe you can also reduce the air resistance.by SDI - Grand Prix 4
The game uses fixed point calculations for most stuff. The result is that many parameters have a maximum, and will become negative beyond it. E.g. if there is a 16-bit internal value and it reaches 32767, then if you increase it more it becomes -32768, -32767, etc. The default power value is 16384 internally. It will overflow to -32768 if you double it, making the car drive backwards. A value ofby SDI - Grand Prix 4
The log shows many problems, try to fix them first.by SDI - Grand Prix 4
Can you also show gpxsound.log? I suspect a sound file did not load. If you fix that then it should not crash anymore. I also just made a fix for the next version so that won't happen again in the future.by SDI - Grand Prix 4
@heidern: perhaps you forgot to set Ext under to png in drivers.ini?by SDI - Grand Prix 4
@heidern: you can check gpxsat.log for any errors.by SDI - Grand Prix 4
Yes, you can, just make sure they are under the right section.by SDI - Grand Prix 4
@RegularJohn: is it possible the replay length is not set to maximum in the settings?by SDI - Grand Prix 4
Thanks heidern Creating another GPxSAT mode is too much work for me. But if you only want to change the appearance of 2010, I think you can easily change the graphics yourself?by SDI - Grand Prix 4
I'd say try to tune the graphics options. Does the PO go beyond 100%? If not, do you have the frame rate set to max?by SDI - Grand Prix 4
I also noticed this a few times. But I have no idea how to fix it.by SDI - Grand Prix 4
Can you be more specific? I'm not sure what you mean.by SDI - Grand Prix 4
The center point is 0. Using a negative value like -1000 will make them brake earlier than normal. And a positive value like 1000 will make them braker later than normal. For the performance file you shouldn't use values higher than 32767 or lower than -32768. And as the magic data values are added to it, I'd say keep it between -15000 and 15000. You can edit desc51 and desc52 inby SDI - Grand Prix 4
BrakingRangeMin and BrakingRangeMax together work like a range around a default braking point. The car is likely to brake randomly within that range (smaller range makes the driver brake more consistently). A higher value means he can brake later. You can try to increase both values with steps of 1000 until you're satisfied, then 100 to finetune. And then lower BrakingRangeMin to make them bby SDI - Grand Prix 4
The "old behaviour" is basically the same as belini's grip and bhp patch, but without the above mentioned part of the grip patch that also affects computer controlled cars (so yes, "old behaviour" has less effect on grip). The "new behaviour" is basically the same as belini's grip and bhp patch, but with an additional patch to exclude the magic data powerby SDI - Grand Prix 4