Please help find my shadows...

No problemo

 

Thanks. Another potential cause struck off the list.

 

Sadly no luck with your file. Thank you so much for trying to help though!

I still have the shadow issue with a fresh copy of windows + fresh copy of rFactor 2... so I'm wondering if it's firmware related.

My work computer runs rFactor 2 with perfect shadows, just at 12 fps.

 

Yes, that's exactly what I'm talking about. Blurry shadows and textures.

 

I'm having the same problem. Im playing in VR with a Vive.

 

I have a temporary/terrible solution.

In controls, assign keys to the following:

• Driving cameras
• Cam move slowly
  
• Cam move forward
• Cam move back
• Cam move up
• Cam move down
• Cam move left
• Cam move right
• Toggle Free move

Then, at the start of the race:

1. Tap 'Driving Cameras' once, to switch to Roll-bar camera, where the shadows should render correctly.
   
2. Tap Toggle Free Move once, to free up the camera
   
3. Hold 'Cam Move Slowly', to make the next step easier.
   
4. With no. 3 held, use the up/down/forward/back/left/right keys to move the camera back to the cockpit position.
5. Race from the cockpit camera with long shadows!

Bad things:

• You will have to do this ever time you go from the pit garage to the grid (restarting race from mid-session is OK)
  
• Pausing the game to open the menu to restart the race, your mouse will move the camera! When you're back on the grid, carefully return the mouse to its original position.
• For me, using cam forward/back/up/down seems to add a slight left or right shift in camera position, which is why the left/right camera controls need to be assigned
• There's not quite enough time to do this during a standard stationary start, so elect to do a formation lap (which can be skipped) to give you the extra 5 seconds needed.

Good things:

• Your shadows are back

Of course, I wish it just worked from cockpit view.

 

Those with the issue, would you mind posting your specs and if you use VR?

VR: Yes
CPU: 8600k
GPU: Geforce 1080
Motherboard: Rog Strix Z370-F Gaming
16GB Corrsair @2133mhz

Hopefully we can find some commonality between us and narrow this shadow issue down.

 

VR: Yes HTC Vive
CPU: 8700k @4,8
GPU: Geforce 1080 AMP
Motherboard: Gigabyte Z370 Ultra Gaming
16GB Corsair @2666mhz CMR16GX4M2A266616

 

Thank you. Interesting how three of us are using Z-something-70 Gaming motherboards. Let's wait for more replies before jumping to conclusions. There aren't that many motherboards out there.

 

I have the same problem, and I don't use VR. I'll try changing Player.json.

 

Where you can change shadowning in player.json?, i have look it all, and it hasnt any shadow command.

 

Could you please post your machine specs, inc motherboard?

Sadly I've realised that my solution above doesn't work in VR

 

Don't know if this will help, but following on from @Goanna advice, I tried a new player.json. There's a line in the graphics section entitled 'Shadows'. In my player.json it was set to 1 and the new file it is set at 3. Tried setting of 3 in my file and seemed much better.

 

There has just been a small update where a shadow fix is mentioned. Hopefully this will fix the issue

Pleasantly surprised to see an update with small fixes !!

 

That's just the Shadows setting in game, 0 = Off, 1 = Low, 2 = Medium, etc

 

New update doesn't work, player.json does not work too, deleted /log folder doesn't work.
It's only shadows LOD in cockpit camera, nobody knows where is the parameter?

I have a R9 380, phenom II x6, I don't know the motherboard, but it's an old one.

 

The shadow LOD in cockpit is supposed to be shorter. This is what FPS optimization is about. The non-cockpit cameras are not FPS critical, so they have longer drawing shadows.

I think people in this thread are confusing two issues. The issue of thread starter (at least in the Matsusaka screenshots) is a real bug that I was not able to reproduce on my system. But in general short LODs like the fences around Indy is not a bug, it's just short shadow drawing, which saves FPS.

One thing that could be at play is the individual display setup/config (resolution/triples/FOV). But just guessing here really.

 

Are you sure about this? It doesnt make much sense to optimize by simply lowering the quality of each setting. Isnt FPS optimization about changing the code behind in a clever way so you can run the same visual quality but with more FPS? If its just a question of making the prior setting "medium" to now be the new "high" its not really optimizing is it?

 

Same problem as described, LOD can't be that hard to save FPS, my framerate it's almost the same in both cases, and in cockpit i see everything pop out about 30m in front of the car.
Here are a couple of pics:

 

For those of you with this issue running without VR, you can use Lazza's HeadTilt plugin to move a car's Rollbar camera/Hood camera to the driver position. The camera position is then saved for future use and you don't need to keep adjusting it each race. Doesn't work in VR.

Thank you Lazza!

Thank you for the reply. Sadly though, this means there's no hardware commonality and I'm all out of ideas.