Just get Jack's files. Saves major headaches.
Just get Jack's files. Saves major headaches.
FFB feels exactly like the first game to me. And just as in the first game you can get ok ffb in some cars then go into another & its rubbish. I'm have to tune the ffb every car i sit in & sometimes it just feels vague no matter. One car clips at 35 another similar car clips at 75. Even when you get it decent you still get nothing to indicate grip when braking or turning just as in the first game. Turning up tone will add some weight on turn in but grip lose does nothing. Just like the first game it loads up the tyres into hill & crests as well as rfactor2 but that's about it. In fact this time round there is way more deadzone.
Edit:
OK tried a few of the JS files.This was a big improvement for me. standard low.
What im still finding i have to adjust volume & tone in every car, sometimes i will drop volume from 50 to 40 or tone from 40 to 50 & it makes a huge difference once you have the sweet spot. IMO its an odd decision not to let us save the Tone & volume setting per car. Please please SMS let us do this.
Last edited by rosko; 23-09-2017 at 16:42.
Win 10 64//4.5g i7 Kaby Lake//gtx Titan x pascal//16gb 3200ram//Asus Maximux Hero IX//Oculus Rift//T300rs//TH8A
The following user likes this Post: EsxPaul
It's not the first time I see t300 user complaining. I'm sure devs are on it already.
In any case, deadzone can be adjust in the custom file. Sorry, I can't recall the line but I think it's an obvious one. The first value I think is the one to change.
Example, 2%deadzone? 0.02 is the value.
---
My feedback is always on default setup unless stated otherwise. Auto-Clutch is OFF
Still hoping for Estoril one day
| CPU: i5 8600K@5GHz | GPU: MSI GTX1080 Gaming X 8GB (397.31) (OC: +70/+450) | Mobo: Asus Prime Z370-p
| RAM: 2x8GB DDR4 GoodRam Iridium 2400Mhz | PSU: Corsair TX850M | OS: Win10 x64 | Sound: Onboard Realtek ACL887 | C:\>: Samsung 840 EVO 250GB
[B]| Monitor:[/B] 3x IPS LG23EA63 @5760x1080 (Bezel Corrected) -- HTC VIVE
| Wheel: CSWv2 + CSPv3(usb) + CSS SQv1.5 - (driver v310 - fw 455) | Damping: 100 | 900š
| In game: Deadzones: 0 |Sensitivity: 50 | Damping: 0
| Wheel Profile: Sens: Aut | FF: 100 | SHo: 100 | ABS: 0 | Dri: OFF | For: 100 | Spr: 100 | Dpr: 100
| FFB: RAW|Gain: 100 | Volume: 50 | Tone: 50 | FX: 50 [B]
| Visual FX: Default except Interion Flare: Off
| Performance - Aniso: 16x | MSAA: Medium | Vsync: Off | Grass: Low | Envmap/Reflections/Shadows: Low/medium/low | Car/Track: High | Blur: Off
| E. Mirrors: Yes | Particles: High/High | SS: 1.2 | Sharpening Strength/Clamp: 0.6/0.045
| Driving assists: ABS/TC, maybe - SC always OFF
| CmdLine: -ffb600 -skipcrowds
It's the "tighten output" line towards the end.
Windows 10-64bit, Intel i2500, AMD R9 380 4GB, 8GB RAM, 40'' TV, Accuforce V2, Fanatec V3i pedals.
The following user likes this Post: rosko
see above i've updated my comment, i think there is deadzone removal in the JS files & it has helped, also the compression has helped with the huge differences between the cars but im still having to fine tune them but generally only a value of +-10. I just wish they would allow to save per car for us PC users.
Win 10 64//4.5g i7 Kaby Lake//gtx Titan x pascal//16gb 3200ram//Asus Maximux Hero IX//Oculus Rift//T300rs//TH8A
System: Win 10 Pro , i7 8700k, MSI Z 370 Pro, 16 GB ram Gigabyte GTX 1080,, Fanatec CSW V2.5 (FW 317, Driver 292), CSP V2, Buttkicker/SimVibe
PC 2 - Custom Files here: http://forum.projectcarsgame.com/sho...=1#post1358152
PC 1 - V3.1.1 - FFB Tweaker Files here: http://forum.projectcarsgame.com/sho...l=1#post891198
Was the Speed Sensitivity default at 50? I feel I am turning the wheel too much with that value? Maybe i got used to 0 or something.
Windows 10-64bit, Intel i2500, AMD R9 380 4GB, 8GB RAM, 40'' TV, Accuforce V2, Fanatec V3i pedals.
I would set at 0, but I am not having any T300 issues. My feedback settings may feel light to some at first. But, I would suspect, if its like my wheel. The oh ****, will hit some of the guys. I think, over doing the ffb is another reason for the high failure rate. Pushing beyond, what the motor is capable of doing is not so good.
PC Win 10 Home 64bit ASUS Prime Z270-A/i7 7700K 4.5 GHz, 32 GB GSKILL Trident White 3200, EVGA SC GTX 1070 (MSI AfterBurner 109/89/124/425) Oculus Rift CV1 (VR Cover for eyewear)
Samsung Odyssey G5 27"
Steam, Origin, Uplay, and Epic (GTsimms)
Primary Fanatec: CSW 2.5, V3 Pedals w/performance kit, R300 w/CSL hub & QR1, McLaren GT3 w/QR1, R330 w/Xbox hub & APMs and Formula V2 w/APMs, Handbrake v.1.5, ClubSport Shifter 1.5 and button caps
Secondary Wheels: T300 w/T3PA Pro (Sparco Rally and F1), T150 (2x), CSR, & GT3 RS V2 w/CSR pedals
Other wheels used in the past Logitech G25, DFGT (3x), MOMO, and Driving Force (GT3 A-Spec).
No offense, but the purpose of Jack's files and this video/spreadsheet is different. They aren't alternatives but complement each other:
- video.
---Explains how the FFB compares to pcars1's
---explains all parameters related to FFB and what they do
---shows recommended controller and FFB settings, including device settings and control settings in game
---Explains also how the FFB widget works and tips and tricks about how the FFB
- spreadsheet.
---Contains recommended device settings in the OS, device settings in game and FFB settings in game
---contains the overall FFB quality score for all cars & tracks in Pcars2
---recommended FFB settings for all cars
---custom FFB flavor file (optimized for t300). This file contains explanations about the parameters included
-Jack's files. Contains a bunch of different custom FFB flavors. All seem to have compression enabled and certain parameters that may have sense for Fanatec wheels but not for others (antidrag).
In my opinion is better trying to understand how the FFB works. A general custom file may provide a different FFB experience but in the end nothing beats a custom file configured for your specific device model. No need to say for your actual steering wheel unit. And on top of that you have to add your specific FFB taste.
Kindest regards
Last edited by Rantam; 29-09-2017 at 17:59.
Intel Core i5-2500K 3.30GHz - 8 GB RAM (1600Mhz) - NVIDIA GeForce GTX 970 - 3 x 19" TFT monitors (playing resolution 3840x1024) + Samsung 40" LED TV (1920x1080) - Thrustmaster T300 Ferrari Integral Racing Wheel Alcantara Ed.-Fanatec Clubsport Pedals v3 - Thrustmaster TH8A Add-On Shifter - TrackIR 5 - SimXperience SimVibe (4 bass transducers) - Thrustmaster Warthog HOTAS - Sounblaster Xfi - Windows 10 - 250GB Samsung 850 EVO SSD Drive - 4 x 1.5 TB Seagate Barracuda 7200 RPM Hard disks
PCars2 Force Feedback explained. includes recommended settings and tips.
PCars2 Force Feedback spreadsheet. Includes recommended device settings and FFB parameters for all cars and tracks. Also custom FFB flavor file.
PCars1 Force Feedback Guide
PCars1 Force Feedback spreadsheet. Includes recommended device settings and FFB parameters for all cars.
Member of HistorX Modding Team
is immersive ffb even working, it just feels heavy and the volume does nothing, doesn't seem like autotune is working on it either