I sent you an email. Not that it's a big issue, I'd rather call it some "finding" if so. 3440x1440 the script handled just fine in the past. Browser didn't make any difference, at least not between Chrome and Internet Explorer
@Reiche Just to confirm: unfortunately too big Sceenshots exceed the Possibilities of the free bplaced Webspace.
For everyone else: 5160 x 2160 px the script took just fine. With 4K resolution being 3840 x 2160 px the script should run just fine for every 'common' resolution. (If you just don't go over the top with supersampled resolutions like I tried to )
Inspired by some Post here in the Forum and also because i wanted to make it since a longer While, i have added a new Tool, with that you can transfer your Mirror and Seat and a few other Settings, that are stored in the all_vehicles.ini, from one Car, to all other Cars of the same Class. That File is stored in the Folder ..\rFactor 2\UserData\player. I have not tested it excessivly, also because i only have 4850 Cars in 202 Classes installed. Maybe, due to the free Webspace Limitations, Problems can appear, when bigger Files get used. If you find something not working properly, please report here. The Tool is called Transfer Mirror, Seat etc Settings from one Car, to all other Cars of the same Class
big thanks for your work, been using your icons creator and just now tried your new tool for transferring settings, seems to work a treat. thank you
Just as an Information: @yoss has reported (thank you for reporting) a Malfunction of the Engine Conversion Tool, that lets the DevMode crash, when the Tool generated Engine gets loaded. I have deactivated the Tool, to try to fix the Problem. I say "try", because it is one of the very complexe Tools, with a lot of Calculations, that i have made Years ago. And sometimes i find Script Entries, where i ask myself why i have done them in that Way, because i can not remember it anymore (i'm just too old). I hope i can fix the Problem and will keep you informed. And to all Users PLEASE always inform me, if from the Tools generated Files don't work properly. If i'm not aware of Problems, i can not (try to) fix them.
The Engine Converter Tool is online again and should work properly now. The Problem was an uploaded rF1 Engine File, that did have "Tabs" in front and behind of the RpM Values, so that the Numbers couldn't be read/extracted properly, which caused wrong Calculations and missing Numbers in the generated Engine File, that caused the DevMode crashing. Please, if you have Problems with a converted Engine, report it here. Thank you
Thanks Chris, i hadnt noticed a problem, but i dont do engines every week.Good that you have fixed it.
When i did write the Conversion Scripts, i always did use original ISI rF1 Files for Testing them. But there are a lot of edited Files in the hundred of rF1 Mods, that it is impossible to include automized Fixes for wrong edited/formatted rF1 Files into the Scripts. So i need Reports for Problems from all Users that work with the Tools, to be able to fix something. In most Cases, the Problems are caused by Uploads of "wrong formatted" rF1 Files. And if that's the Case, i add some Code to the Script that fixes that. But because there are soooooo many Things that can be "wrong", Problems can appear ever again, caused by another Reason.
Due to a Request from @Nicola59 i have added a new Line to the Tool, with that you can "convert" Tire Size Designations (this one), where you can enter Sizes of Tires from the ~ 1960s. And you also can upload TGM Files now, to check their Sizes, that get calculated by the Nodes Positions and if they use the integrated SizeMultiplier.
I'm soooo glad I burned out after the SCC project for GTR2. Man, the math in rF2 is WAAAAYY over my head.
I have added a new Site to the Tools, that includes all available "Explanations" for Values, that can be found in the DevMode Skip Barber Files. It's called Get File Entry Explanations from the DevMode Skip Barber In that Way these Explanations are always available and, at least in my Opinion, faster and easier to find, than to search for them in the Files directly.