Doppelnull
Members
-
Joined
-
Last visited
Everything posted by Doppelnull
-
No problem 🙂 Its indeed same error which happened to me. Its because ScriptHookVDotNet can't interpret values like .3 or .18 which means 0.3 or 0.18 for us. But after changing this values to fix this error, you can't drive anymore atm.- 329 comments
- 24 reviews
-
-
This is explicity what i mean. We can't use values like .3 (which should work...) We have to use 0.3 (not lspdfr version 😄 - i mean the steering value) but even than it wont work. I can steer my car to right but when I want to accelerate I just hear the motor sound. @Elemir Could u try to press the insert key when using the mod? If then shows the upper error, we have the same problem and u can ensure that its loaded. My actual config (steering works but can't drive and no errors anymore) <settings> <steering stiffness="0.08" stiffnessSpeedGain="0" responsiveness="0.08" recovery="0.2" centering="0.12" centeringSpeedGain="0.06"> <!--stiffness: general stiffness of the steering--> <!--stiffnessSpeedGain: how much stiffness shall increase with speed--> <!--responsiveness: how long steering key(s) must be held for full steering input (helps smooth steering)--> <!--recovery: how long steering key(s) must be let go of until steering input speed is back to 0--> <!--centering: how stiff the centering is for the steering (no centering applied when stopped)--> <!--centeringSpeedGain: how much centering stiffness shall increase with speed--> <!--realistic preset: .08, 0, .18, .2, .12, .06--> <!--arcade preset: .1, 0, 1, 1, .2, .06--> </steering> <throttle stiffness="0.0075" standardThrottle="0.1" fullThrottleModifier="ControlKey"> <!--stiffness: general stiffness of the throttle--> <!--standardThrottle: what is the maximum throttle achieved when the fullThrottleModifier is not pressed--> <!--fullThrottleModifier: key that must be held for throttle to behave as normal (without this mod)--> <!--LIST OF VALID KEYS: "https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.keys?view=netframework-4.7.2" (without quotes)--> </throttle> <autoBrake enabled="true" speed="0.0004" maximum="0.3"> <!--autobrake comes on once throttle is released--> <!--enabled: enable the autobraking system--> <!--speed: how fast does autobraking come on after throttle release--> <!--maximum: maximum braking amount (1 does NOT mean full braking)--> </autoBrake> <keys steerLeft="A" steerRight="D"> <!--for a smoother experience, set in game steering keys to ones you don't use, such as print screen or scroll lock (because my mod overrides them but GTA can try to "fight back")--> </keys> </settings>
- 329 comments
- 24 reviews
-
same. Its because the values in the settings file dont have a prefix. stiffness is .08 which throws ingame an error on reload - like anyother values. But adding a zero before all this values just fix the errors, but then u cant drive anymore.
- 329 comments
- 24 reviews
-
In my view, this makes sense especially when you want to boost pre-sales. Particularly since you could do a little better than the rest of the industry. I just wanted to point out that I guess from my point of view that from the staff's point of view it was already obvious that the beginning of February could not be achieved and therefore unrealistic. If that were the case, we might say the end of February. This date would perhaps be more targeted. Nor do I want to start a discussion about it or condemn anything. I personally simply wish for more transparency in the future, as there is no reason for me to handle it the way it is done at the moment. The fact remains that LSPDFR should take the time they need. But maybe they could minimize the release range so that you don't hyped yourself months before. Nevertheless, I would like to apologize for any inconvenience I may cause. Let's get back to why we're all here. Support the LSPDFR team and mentally prepare for the release.
-
I think it's pretty annoying to make unrealistic and inaccurate announcements about the possible release more than a month before. You could also announce the end of February if any other release date seems unrealistic, so as not to let your community stand in obscurity. Many people have been hyping for weeks, although every staff member is more or less aware that February 2019 means only the end of February. You wouldn't have had to announce a specific release date, but at least a realistic period as short as possible. Again, it's just my point of view and I don't know tactical backgrounds. For me personally, it always seems disappointing, as it subconsciously feels like it's shifted every weekend. Nonetheless, I thank you for your work and hope for a timely release by, as announced, the 28th of February.
