They can be used together. Player master grip changes a different grip value. Both grip values affect the final grip.by SDI - Grand Prix 4
I suspect that's because of Belini's grip patch that I incorporated in GPxPatch (unless you select 'old behaviour'. It affects both players and CC's.by SDI - Grand Prix 4
Yes, it's there (https://bitbucket.org/sdidit/usr/issues/157/performance-file-2-names-for-one-team), but as I commented there it's not trivial to implement.by SDI - Grand Prix 4
Seems to be related to animation data.by SDI - Grand Prix 4
Probably never, it's too much work.by SDI - Grand Prix 4
I agree with TomMK, GPxTrack handles this for you. From GPxTrack documentation: Quote Sometimes you just want to change the order of the default tracks. This case is also handled by the track manager. In GP4, when a default .dat file is detected in a different slot, the .wad file from the original slot will be loaded, as well as the .gpi (menu track map), loading screen .bmp image, and track mby SDI - Grand Prix 4
It might be related with how GPxPatch tries to patch the encrypted exe. You can find the decrypted exe for 1.02 here. Using it is more convenient and allows you to use editors that patch the exe.by SDI - Grand Prix 4
LastChance Schreef: ------------------------------------------------------- > GPx version detected: encrypted GP4 v1.00 Try to upgrade to 1.02, and if that doesn't help, using the decrypted GP4.EXE should help.by SDI - Grand Prix 4
@ParisHL, @AustinF1: If you replace GPxPatch with an older version, does it change anything?by SDI - Grand Prix 4
Seems about right. The car with error chance 10000 ended up last.by SDI - Grand Prix 4
CC setup per car should be possible to implement in the performance file I think. Not sure why you want player's setup in there? Physics can't be different for each track without restarting the game.by SDI - Grand Prix 4
Ok, I've debugged GP4 to check when it reads the values for which cars, and I saw that desc50 is sometimes used for both player and CC, but most of the time only for player. But desc72 was always used for both player and CC, but from different parts of the code. The player's car has individual tyre wear for each of the 4 tyres, but it seems the CC cars only have tyre wear for all wheelsby SDI - Grand Prix 4
As far as I can see desc50 is a factor that simply multiplies desc72, where 16384 equals 1.0. I see no difference between CC or player here, meaning they should both work for CC and player (just by looking at the code).by SDI - Grand Prix 4
Add new sections to the performance file called QualifyPower and RacePower. Specify two values for Team #00 through Team #10, separated by a comma.by SDI - Grand Prix 4
You can use TeamEditor to edit the power for each team and select the resulting file in GPxSet.by SDI - Grand Prix 4
This confirms my earlier conclusion. The crash is inside ntdll.dll from Windows. I have no further leads.by SDI - Grand Prix 3
You should at least post the complete log, not just the part with the stack. From just the stack I can see that the game is GP3-2000, and that it crashes while allocating memory with what it seems to be an access violation. This hints at heap (memory) corruption. The reason is unknown.by SDI - Grand Prix 3
You can check the log files for irregularities.by SDI - Grand Prix 4
Sure, but I might as well put it simpler: F1=1 (auto brakes) F2=2 (auto gears) F3=4 (auto right the car) F4=8 (indestructible) F5=256 (show best line) F6=512 (suggested gear) F7=16 (traction control) F8=32 (steering help) F9=64 (launch control) Add all the numbers of the aids you want to be allowed and use this sum as the value in the performance file.by SDI - Grand Prix 4
I just saw that GPxPatch itself patches the driving aids mask when reading the AidX (X=difficulty, 1 through 5)values from the section in the performance fileby SDI - Grand Prix 4
No, and it looks like I made a mistake with which digit is which help function. The correct mapping is: F1=0000000001 (auto brakes) F2=0000000010 (auto gears) F3=0000000100 (auto right the car) F4=0000001000 (indestructible) F5=0100000000 (show best line) F6=1000000000 (suggested gear) F7=0000010000 (traction control) F8=0000100000 (steering help) F9=0001000000 (launch control) Noteby SDI - Grand Prix 4
Start Windows Calculator, select programmer mode, then BIN mode. Type 100, then a 1 or 0 for F7 through F1 (edit: for correct mapping see my next post). Then read out the DEC or HEX value. E.g. 626 decimal is 1001110010 binary. This has F1 (right most digit), F3, and F4 disabled.by SDI - Grand Prix 4
You can use a hex editor to edit the exe. For GP4 1.02 the offset is 3A8DC0 (hex). Here are 5 WORD (2 bytes) values, one for each difficulty. Change these 6 bytes: from "7F 03 7E 03 7E 02" to "72 02 72 02 72 02". That will make the driving aids mask for the Rookie, Amateur and Semi-Pro the same as Pro.by SDI - Grand Prix 4
Memory corruption. Cockpit seems invalid, perhaps that's the cause.by SDI - Grand Prix 4
I notice from the log that you get this error: "Bump range too high. Wrong slot or no cmagic used or wrong bump table made."by SDI - Grand Prix 3
Thanks, glad you like it With GP2 you used GP2Lap, which I did in collaboration with Frank Ahnert, and this led me to create GPxPatch.by SDI - Grand Prix 3
Sounds like your track is missing something, and the previous track has some leftover that is used instead.by SDI - Grand Prix 3
Ok, this is the same crash. I have no further leads.by SDI - Grand Prix 3
Who has a problem then, elio2012 or quickslick? The crash happens because a pointer to a car is null. Not sure why.by SDI - Grand Prix 3