Just got a blackscreen in U13.
Started in fullscreen, went to windowed once then connecting, back to full, then after a couple of races, back to windowed, resized the window (top left corner), black.
thx for the hardwork and listening to the communty!! we all apreciate Scavier's hard work and unprecidented dedication and focus. I feel like a few of the changes in the latest patch were made just for me lol... you probably dont want posts like this in this thread
I know this is being very awkward and may not be feasable but could the steering wheel be shown in a static position in the F08/BF1 when wheel draw is turned off, like in GP4. If this is possible would there be anyway to get the shift lights into the virtual clocks?
It'll probably get pruned to another thread during maintenance, and that's fine.. I do agree, tho.. Scawen, your efforts and determination to achieve results are very much appreciated by us all, I'm quite sure!
Okay.. now to make this post worth having around:-
BACK UP YOUR \SCRIPT FOLDER!!
You might not think of it, when a new patch comes, and be as eager as me to download, extract and run the new EXE. I would have you learn from my mistake.. along with the exe file, the new patches come with default scripts for cars and gears. If you edit and save your scripts, with all your button and key assignments, and then download a NEW patch.. your scripts are at risk. Back 'em up!
Yes, it's obvious. I know it's obvious, but if I can help [edit] PREVENT [/edit] someone else making the same dumbass mistake I made, then I've done a good thing
Got no idea if this would be a compatible improvement, but I thought I might let you know Scawen. Might not even be possible to fix. Anyways here goes:
- When I race on a server that is in the same LAN as me, in the present case NAL Long Run (which is a public server of LFS North American League), LFSW doesn't seem to see it. So if I drive 1000km on that server, LFSW will record my pb's and stuff but not on which server I last raced. I'll say I last raced on the server I raced before the one that's on my LAN.
Not sure it's possible to fix tho.
If post is irrelevant, sorry.
I am having an issue with my Hyper Simulator Wheel and pedals, for some reason in these later patches, from maybe patch S onwards, I haven't used the wheel for awhile but my son is getting into it so I set it up for him, but you just can't drive the game the wheel flickers all over the place while accelerating, but stops when I backoff the throttle, I even brought brand new steering pot and throttle pot and put them in, they are perfect in the Hyper Stim Menu system and calibration. If I use an earlier version of the game the wheel is fine, I tried it on Patch P and had no issues with the wheel, but go back into Patch U and it plays up. And also why doesn't LFS keep my settings from my Hyper menu like any deadspots I put in or my range changes???
just a small one Scawen, please could you shorten the /spectate command to /spec ? sometimes it just takes too long to type (and the more letters, the higher the probability of a typo) and this decides wheter a wrecker hits his target or not...
I dislike the idea of a static steering wheel, and can't understand why anyone would want that. Off means off.
But I have added that special new virtual central dashboard, that comes on automatically in the FO8 and BF1 when you turn off the driver and wheel. So I thought I solved the problem of vanishing dashboard.
Have you seen that? If not, that must be a bug. If you have seen it, then please explain what's wrong with it and why you need a stationary steering wheel to be visible. The new virtual dash contains the complete steering wheel dash, so all the info is there.
Have you tried "recalibrate axes", "remove deadzones" and "calibration lock" ?
They are visible down at the bottom when Axes are selected.
Other than that I have no idea, the controller changes are mainly about where the info is stored, nothing changed in the way axes are read and those values are processed.
And what does everybody have a Hyper then do they....man I hate people trying to be a smartarse, when all I want to do is find out why my controller doesnt work now, but does on the earlier patch, which I have just tried because I still have a copy of it on my system....
but for cycling it is already possible (with more "work"), you just need to do 4 lfs scripts let's say you want to use the "+" to cycle one direction, then script 1 has 2 lines: one that press F9 the second that assign script 2 to key "+"; script 2 has 2 lines: one that press F10 the second that assign script 3 to key "+"; etc.
for the rest, it just needs for the arrow key to be pressable
Because you did sound sarcastic, I am sincerly sorry if I took it the wrong way. But you have now helped me after re-reading your post I have deleted the correct file, and now it does work thank you so much, I was looking at the files on the misc folder relating to controllers, and not the main cfg file in the root directory of LFS..... I feel like a complete tosser now for saying that, I really hope you do accept my my utmost sincere apology....
I just want to check with those of you who will be writing scripts, if the idea of removing the slash at the start of every line in scripts is good or could cause problems.
Hehe, yes indeed. This happens if clocks are set to real, either in cockpit or cusom view. If clocks are virtual then its same as before. Driver and wheel always get shown when F is pressed regardless of the option to turn them off (its always been like that I think).
It just struck me.. "/drop", as in to drop from a race. If they're naughty, you can drop, kick and ban them.. which in some strange way would be quite satisfying for some of the nastier ones
Typing "/spectate" is, more often than not, hit and mostly miss for me too.. most especially because when I'm typing it, I'm trying to get it typed in a hurry before the little git that I'm after has cut across the grass and blindsided some other poor driver. I suspect it's not a compatible request, though, because it will probably involve the server side too. If that's the case, my apologies.
Thats what I did last night manually with my MX518, I set the +/- buttons to Right/Left , set the Thumb buttons to up/down, and the App-switch top button to F12, but I think the cycle idea would be the most efficient and effective way to do that. or even just cycling thru F11 and F12, instead of the whole F9 and F10, possibly a seperate button for that?
I know this is not the place to say this, but this is where the developers will read something while they are in the specific mood for fixing bugs and therefore it is the best time for me to say it, in the hope of giving some mental support:
I appreciate your effort so so so much, thank you and keep up the good work! :woohoo: :bowdown: