[REL] Pays de La Loire (FRA) - The Bugatti Circuit - v1.00

Just in case you want to replace the water depth related pic`s, i attached all meteo files, wich where changed by me.

Where to replaced: \rfactor2\Plugins\TrackMap\Images\HUD\

View attachment 20288

 

I'm going to check today. I remember that was common in rF1. Funny thing is this sort of issue occurs more often to cars without windshield (paradoxically, with one less transparency to engine deal with).

 

Hi,
Thank you ECAR_Tracks for this wonderfull job. This is an amazing track u've done. For me probably the best 've try.
As i know this track for being marshall and fan of 24h of Le Mans race since 1988 (and all other race in the Bugatti circuit), i've some little details information to send to you :

- The pit exit used is only used by motorcycle. Racingcar used the first pitexit just at the end of the pit wall.
- Just left before the Dunlop bridge, no vehicule can really be place here. It's a little mount just use for spectators.
- It's the same for the vehicule place between the "Chemin aux boeufs" and the "S bleus"
- For the loading circuit picture, you can find the good "Region Pays de la LOire" logo here : http://www.paysdelaloire.fr/services-en-ligne/logos/

As you see, it's just little details ;-)
Sorry for my bad english

 

Le Mans Bugatti keeps freezing computer. Is anyone else experiencing this ?

Running the ISI Corvette C6R GT2 mod with the track only. The game gets a graphic glitch for myself before freezing the whole computer (happened 3 times). Power off is the only way to fix it. I'm running full screen mode.

A friend last night crashed 4 times however he was running in window mode so was able to close the game and try again.

It's only this track that crashes, we ended up repackaging the Corvette mod with the ISI Indy track and had our small race.

Hardware and settings. Settings on high-max. I'm running a EVGA 980ti card on triples. I have no problems with other mods or tracks, just putting it out there that this causes the game to crash, could be related to the textures issues outlined above, I'm hoping so because the time on the track I found it to be a great track.

 

900-series issue, unfortunately...

 

Yes unfortunately to my dismay I found this out after moving from 680's to 980ti. Have a read of THIS thread, Whiteshadow offers a couple of pointers but the fact of the matter is that with the GPU running at a high usage rate for a period causes windows to trigger TDR, crashing the Nvidia drivers. Dropping some details or AA so that the GPU isn't at a constant high rate, increasing power usage of the GPU & adding some extra voltage all help too. But seems like running the 353.30 drivers (best driver performance of rf2) along with Wanguards TDR Manipulator is the most effective solution. Unfortunately running 353.30 drivers for me isn't an option as causes problems on other games, so I've resorted to bringing down Shadows and reflection in-game and staying away from certain tracks. The worst being the AC-Spa rip.

 

Recently finished installing my new PC, fitted with a ZOTAC GTX 1080 AMP! I succesfully ran some laps on this track yesterday, will set up a stress test to see if this problem has been carried over *fingers crossed* :/

But my 780ti begged for a replacement, solid card though! Also from ZOTAC.

 

Hi guys,

I would recommend you don't use my track in your leagues for a while until I make v1.00 available, which will not take much longer from now. Nvidia 900 series is a very common hardware and it's very probable some racers will have driver crashes producing biased race results.

Just FYI I'm reviewing deeply all track geometry and I'm finding out a lot of "garbage" left behind by some 3ds Max plugin I used and some bad practices from myself. Those are:

• Zero area faces
• Isolated vertices from some models polygons
• Forced anisotropic levels in some textures
• Overlapping faces and some edges

In addition, I'm creating shadow objects for complexes meshes like tyre barriers which have 1/4 of vertices and also converting all objects to GMotor normals.

I'm doing this cleaning up based in a track that my GTX 980 can run for hours and hours whitout a glitch: Bathrust - 3PA. That track has more points and textures than mine and doesn't crash. So, even considering the issue is showing off in GTX 9** users, the source of the crash must be something with the track.

I'am making an inventory of Bathurst and comparing to my track on following regards:

• Shaders used
• Texture compression
• Parameters of materials
• Number of vertices of shadow caster objects

What would be a reasonable explanation for the same GPU card run a demanding track like Bathrust or Toban and crash with others? A hardware related issue should be occurring in any track, randomly. So, my conclusion is: there's some bad objects, textures or materials that should be not in the track but, for some reason, GTX 600* and 700* series are able to surpass that with the existent Nvidia drivers whereas 900* series don't.

I performed a run yesterday with my private partially cleaned up Le Bugatti for 2 hours without a driver crash. It used to crash in few less than half hour, so it's encouraging. As I finish this geometry review I'll publish v1.00 for you guys test.

Thanks for the feedback.

 

Radar, do you have VLM Le Mans 1991 - 1996 in your computer? If so, maybe you want to do a test because that is other track which presents the same symptom than mine. So, please have a look in my post above this.

 

Thanks for your effort!

 

Would it be wise to do tests with the minimum amount of detail then feeding in objects bit by bit into the SCN to see if there is a rogue set of objects?

 

I created a test-upgrade at VEC with the VLM Le Mans track used for the season finale, even with ONLY road surfaces people had driver crashes. I have very little hope that this 'fix' will ever be found, also the issue is not isolated to RF2, but several other games in certain scenarios.

 

Nice effort, for a great track !!

 

Maybe the problem be exactly in the road objects and/or material used. In addition, if you remove all objects, the REFLECTEDENV reflection set start to miss objects which are not in the scene anymore what can lead to a crash, mainly if the track creator didn't take care of cubemap percentage of real-road material, which forces reflection even in dry weather.

So, to isolate object per object and start adding few of them per attempt can be more tricky than it sounds since it may require a full scene rebuild including reflections. That would be the last resort after my cleaning job was not effective, but I'm confident.

 

We appreciate your efforts, for sure.

 

I truly do hope that you find the recipe, you are doing a spendid job so far

 

+1

 

+1 [emoji4] [emoji106] thank you

 

Did you just exclude the .gmt files from the .scn file or did you also delete the .gmt files from the .mas files?

 

Since it was made as an update .rfcmp there was no deleting of .gmt files. And since this is not an rf2 issue, but a driver/hardware issue, it would make sense that only what gets rendered is important.