Thanks for the suggestion guys but unfortunately it was too late. I wouldn't have time to do the necessary tests and checks for our competition without delaying the start of the round by a day or two. Plus, I had already announced we'd be using the F1virtual version a couple pages back.by Prblanco - Grand Prix 4
by Prblanco - Grand Prix 4
Question to everyone: Jordhy's 1:24.812 lap arrived on the server 2h24min after the deadline. The lap is otherwise valid, and its log says it was driven Saturday morning. I did not ask Jordhy what caused the delay. He did not send any other laps. Should we accept his lap?by Prblanco - Grand Prix 4
@Hinyaldee: please use the .dat and .ini files sent by e-mail, your laps sent so far do not match track checksum.by Prblanco - Grand Prix 4
This year's .dat file has revised magic data, so lap times aren't comparable. Don't stress too much over it Also everyone, make sure you use the .dat and .ini sent by email. Look at the example checksums!by Prblanco - Grand Prix 4
Jordhy's lap was slightly above average 100% PO which would be against the rules but, since he classified last, I'm willing to validate his lap unless another driver protests against it. Be warned Mexico is a heavy track on CPU, so please check your graphic settings to avoid trouble. I'm very sad I missed this round as I built the original .dat file which was the base foby Prblanco - Grand Prix 4
Thanks for the great work kerleyf1 and everyone involved. Here's a small gameplay video:by Prblanco - Grand Prix 4
There will be no .dat adjustments to next week's track. Those who wish to start practicing early can download Austin 2019 from Jorge's thread. Install on slot 2by Prblanco - Grand Prix 4
Sorry to unearth this thread without any new content, but I've seen *things* so there's a bit of info I must reinforce: Files shared here are free for anyone to use, modify or update on whatever manner, without need to ask for my permission. Tracks released at the F1virtual website involve the work of more people than just myself, so the rules above don't apply. Do not modifyby Prblanco - Grand Prix 4
by Prblanco - Grand Prix 4
If the problem is only with restoring, you could try disabling CSM's Auto Restore option. That error message is from CSM, the mod itself doesn't give that kind of warning. I don't think these error codes were ever documented though so we're all as clueless as you are.by Prblanco - Grand Prix 4
by Prblanco - Grand Prix 4
Hi everyone, a quick rundown on the track versions we'll use in the last rounds: Singapore, Suzuka and Austin will be the latest updates from JCaranti. Suzuka and Austin from 2019, and Singapore from the 2014 trackpack. All available in his work thread here. Mexico will be the 2017 update from gezere, available here. Interlagos will be the 2008 version available at F1virtual. Andby Prblanco - Grand Prix 4
Monza results! We had two series running this round, one comprised of Jorge and the other of everyone else. Jorge made the most of manual shifting and steering wheel to nail an impressive lap, 1.5 clear of the field. The midfield is a different story though with 6 drivers covered by less than 4 tenths! gildoorf and ksezen once more reach the podium, while Jordhy gets a season-best 4th pby Prblanco - Grand Prix 4
Before the results, two things: 1) The initial Monza email had a mistake, track should be installed in slot 16, meaning saved hotlap should have extension *.hlq. 2) Suggestions for Singapore track? Zandvoort results! After the nearly empty field at Spa, the boys are back at it and for the first time in the season we have 10 classified drivers! The track seemed to favour the analogby Prblanco - Grand Prix 4
Zandvoort Provisional Results 1 JCaranti 1:13.017 2 deokastyler 1:13.366 +0.349 3 Prblanco 1:13.534 +0.517 4 fongu 1:13.761 +0.744 5 ksezen 1:14.039 +1.022 6 gildoorf 1:14.084 +1.067 7 Hinyaldee 1:14.898 +1.881 8 Jordhy 1:15.197 +2.180 9 Carl_gpgames 1:15.734 +2.717 10 Maverick1968 1:19.489 +6.472 Official results will be published here and sent by email once replay checking is comby Prblanco - Grand Prix 4
@deokastyler your 6th and 7th sent files have empty logs, so they're not valid.by Prblanco - Grand Prix 4
Regarding save/restore, I explained why it can't be used (or rather, why it doesn't give any advantage) during the hotlap back when we were discussing the rule changes a month ago, there's no contradiction here.by Prblanco - Grand Prix 4
This particular crash was caused by CSM's fastwad feature; some tracks are not compatible with it for unknown reasons. So, in this case, the track works after disabling fastwads and then redownloading the track.by Prblanco - Grand Prix 4
This track is very unforgiving, I'm breaking a suspension every 5 minutes @Maverick1968 if you use save/restore during your hotlap, your laptime will not be valid. Use this feature for practicing only.by Prblanco - Grand Prix 4
3DEditor is now GP4Builder, which you can get the latest version here: It has changed a lot since the old days of 3DEditor but the basics in building a track are the same, so I think you'll still be able to follow the tutorial with the latest software.by Prblanco - Grand Prix 4
What a great achievement, congratulations for all the hard workby Prblanco - Grand Prix 4
It was a very marginal call on whether ksezen's best lap (1:47.602) was on or off track at turn 9, it was ultimately deemed off track, but I'm open to reviewing it again if there is interest. It won't change the final result though. I'll do my best to find some time to submit a lap this week, hopefully more people return as wellby Prblanco - Grand Prix 4
Quotejimbob1CTD for me Do you have a crash log Jim? Does it crash after clicking "DRIVE" or during the loading screen?by Prblanco - Grand Prix 4
Summary of received laps, checks still pending: 1 JCaranti 1:46.144 2 gildoorf 1:46.960 +0.816 3 ksezen 1:47.602 +1.458 4 Hinyaldee 1:48.544 +2.400 It seems not everyone returned from the season break Zandvoort for this week's round is available at the F1virtual website.by Prblanco - Grand Prix 4
A slightly upgraded version of Zandvoort is now available for download at the F1virtual website. I still don't know what's causing the banked corners to be so bumpy, hopefully I won't need to rebuild the .dat to fix thatby Prblanco - Grand Prix 4
Absolutely marvelous job, thank you very muchby Prblanco - Grand Prix 4
I finally managed to reproduce your crash on my PC, and it happened after I used CSM to convert the track's .wad file to a fastwad file. So please try these steps: In CSM, go to File -> Options and deselect "Fastwad check" Select File -> Convert all wads -> To normal wad Download the track again If this works for you, you'll also need to download Sakhir againby Prblanco - Grand Prix 4
Regarding physics and frame rate: In GP4 (and the whole Geoff Crammond GP series), unlike more recent racing simulators, physics calculations are tied to the graphical frame rate (for example, iRacing's physics run at 360 Hz). In other words, in GP4, every frame on the screen also corresponds to a time step in the physics calculation. I confirmed this during my GP4.exe investigations, whereby Prblanco - Grand Prix 4
by Prblanco - Grand Prix 4