rFactor 2 Online Tools by Chris “redapg”

Hello Dave, the Power Output is american HP.

 

Thanks!!!!

 

I have noticed, that there still seem to be some Problems in some Scripts, caused by the Switch from php 5 to 7.
So please, if you generate a File with one of the Tools and it doesn't work properly, inform me here or by sending a Mail (Mail Adress from the Tools main Site).
You can also make a kind of a "quick Check", when you search for N/A in that File.
That is one of the Indicators, that something went wrong.
My Problem is, that it sometimes seem to work and sometimes not and i can not test all possible Configurations of uploaded Files.
And i also can not write the Scripts in a Way, that they detect all wrong Entries in uploaded Files automatically.
So a Misfunction can be caused by wrong formatted uploaded Files and also by a php Problem in a Script.
Merry Christmas to all of you!
Chris

 

Have a great Christmas you too Chris.

 

I think that everybody who uses the DevMode knows it.
You get an Error Message, when VisGroups Entries are in Conflict with CollTarget=True and/or HatTarget=True.
That can be very annoying, even if you only have to hit Enter to continue.
So i did write a small php Script that removes the VisGroups Entries.
Now i thought that it maybe could be useful for others too and did add it to my Online Tools.
It's called
Remove VisGroups Entries from SCN Files, that cause a Conflict with CollTarget or HATTarget=True Entries
and it currently removes VisGroups Entries with the Numbers 36 and 38.
If you find more Numbers that cause that Conflict, please inform me here.

 

Thant you very much
I suppose that only removes the visgroups of the instances that have CollTarget=True and/or HatTarget=True
Right?

 

great idea Chris, they really are annoying .
so thank you
phil

 

Yes and you get the affected Instances displayed, before you can press the Button to remove them.

 

Fantastic, as always

 

Coming from THIS Thread, i did add a new pdf Tutorial to my Online Tools Website, that describes, how a DLC Vehicle can be updated.
It is linked at the Bottom of the Tools Site and the Name is :
Update_a_DLC_Vehicle (<- direct Download Link)

If you find something wrong in it, inform me here please.
Thank you.

 

Thanks for sharing this. Now I only have to find out how to put a potato inside Detroit´s exhaust to slow it a little bit

 

Thanks Chris another great Tutorial, very much appreciated.

 

Lol, American technology to the rescue

 

Important Information:
@Juergen-BY did report (thanks for that ), that he got a Problem with the Tire Editor Tool, where the Values from a commented/deactivated Line have been used, instead of the active Values.
With commented/deactivated, i mean Lines, that start with // (i never know what is the best Term for that in english).
I have checked the Script and have seen that i neither had included a Routine, that automatically removes such Lines from an uploaded File, that i had already implemented in some Scripts, nor a Hint on the first Site, that you have to remove all these Lines, in Files that you want to upload.
I will recheck all Scripts in the next Days (/weeks), to at least ensure, that they all have the Hint included.

So please, remove all commented out Lines, from the Files that you want to upload in one of the Tools.

For the ones, that are interested into the Way how the Values are taken from a File and what leads to the Problem, here is a short Explanation:
In the most of the Cases, the Values in the Files have unique Names, like
CGRightRange=(0.499,0.001,4)
for Example.
So i let the Script search for everything that is between CGRightRange=( and ).
In that Way, i get the 3 Values that are inside of the Brackets, that i can separate by the Commas then.
The Problem, when there are more Lines with the same Name, that are commented, it can happen, that the wrong Values are taken, when the commented Line is in front of the correct Line, because the first found Match gets taken from the Script.

 

Thanks, Chris, for the explanation. I call // two forward slashes.

 

Thank you Rob, but it have meant how a Line gets called, that starts with 2 Slashes.
I mean to remember, that there was a Discussion about it in the Past, where a User did say it is called
a "commented" Line.
But when i translate how i would call it in my Language (German), it would be "outcommented".
So i'm not sure which Term is the correct one.

It's a bit like with what you have written.
As a German, i would call // only Slashes, not forward Slashes and \\, i would call Backslashes.

 

Similar in English for the slashes, 'forward' is an optional specifier used in contexts it may not be clear (ie not anywhere outside of computing, basically)

As a hobbyist programmer for ~20 years a line starting with // is 'commented', or 'commented out' especially when several options are available and you comment the ones you don't want to use. And as I just used 'comment' is kind of a verb, but very much only in this specific context (programming or .ini editing)


I think I've spent too much time over the years fiddling with custom parsing of files and not enough building impressive things on top.

 

Chris, i guess Commented out is the most used, at least in English.
Phil

 

Thanks @Lazza and @philrob
So i guess i will use "commented out" or maybe "commented out/ deactivated" from now on, then.