Working with Omsi Script

I have a question about Omsi Script.

Because I'm scripting now in Unity's C# Script. How is this compared to the OMSI Language, and can you give some more information on the scripting language.
For example : Is it object based? Etc.

Thanks again

BlackSpider

OMSI uses a non-object-orientated, line-based, RPN-style scripting language.
Here is a screenshot of a typical OMSI script file:

Rüdiger Hülsmann schrieb:

OMSI uses a non-object-orientated, line-based, RPN-style scripting language.
Here is a screenshot of a typical OMSI script file:
Image

Thank you for your quick answer. It looks difficult because of the German Language.
But i get a little bit whats going on in the script.

BlackSpider

Well, you can name your variables in any language you want ;-)

Rüdiger Hülsmann schrieb:

Well, you can name your variables in any language you want ;-)

So what does this mean for instance.
S.L.antrieb_neutral_Requested.
S = variable.
L = variable.
antrieb_neutral_Requested = variable.

Something like this.

We will create a full documentated SDK for you! But we will need some time!

Ok, just one big basic for our script:

if you want to do "1 + 1", you have to type "1 1 +" !

So you set the first operator, then the next and then the operation.

The result is again the first operator: 1 1 + (S.L.Var) means, that he will store 1+1, that means 2 in the variable Var.

(L.L.Var) 1 + is now the opposite: he loads Var (L!) and then adds 1!

Subtract or divide: 50 2 / is the same like 25! Or 10 4 - is the same like 6!



That was a VERY VERY VERY short description of the basic concept of the OMSI script language. As I said above: There will come more later! But first we just have to translate the main and the editor manual!

Thank you so much. for the explanation

I get it and Ii will wait for the SDK documentation.

Marcel Kuhnt schrieb:

if you want to do "1 + 1", you have to type "1 1 +" !

Couldn't do any wierder? OK, I prefer C++ operations (z is an integer variable, it's right now 6, and I want to add on 1 - I do that: z++. Done :p )

EOT.

I really, really can understand you! But I was really a greenhorn in such things like parsing etc.! And that way we did it, it is now a little bit confusing but was much easier for me to implement in OMSI!

Marcel Kuhnt schrieb:

I really, really can understand you! But I was really a greenhorn in such things like parsing etc.! And that way we did it, it is now a little bit confusing but was much easier for me to implement in OMSI!

It's done like this and called reverse polish notation

I know from my very very limited knewledge with Marcel script and correct me if I am wrong,

Code:

(L.L.n_Wheel) (C.L.antrieb_i_achse) * (S.L.antrieb_getr_n_ab) (L.L.engine_n) / (S.L.antrieb_wandler_ny)

The S.L.antrieb_wandler_ny is the end result variable which that variable could be used somewhere else... I guess

(C.L.antrieb_i_achse), the C is the constant value that can be find in any of the consist.txt files that is linked to the bus...

Yes, that's correct.

In clear words:

1) Load n_Wheel, multiply it with the constant antrieb_i_achse and save the result into antrieb_getr_n_ab
2) Divide this result by engine_n and save the new result into antrieb_wandler_ny.

I feel my brain twisting

That was going to be my second half of the post but was not going to go into details on something which may or may not be (at that time) correct. It is good to know I am starting to understand the basic markup of the script...

I'm programmer, with java, php, javascript, lua knowledge and pascal from school, but i can't understand these weird variable naming(maybe mostly because i don't speak german), and where these variables come from. No any call to game engine, just there is a variable from nowhere.
Why didn't you just plugged in a lua script engine? It's free, and it's pretty usable, i've programmed a some complex things for railworks which using lua script (engine simulation, cab and body sway, warning system, etc) . And the limits of it are only the things what can be called from lua script (which is depends only on game programmers).

"Just plug in a script engine" sounds a bit optimistic. As we were unfamiliar with external script engines, we have developed our own.

The variables and constants used in our script files are defined for each vehicle. So a usual script set includes the following three files:
script_varlist.txt => list of variables for this vehicle
script_constfile.txt => list of constants and their values for this vehicle
script.osc => script file where the real programming happens.

As we've said, the OMSI script engine uses RPN (reverse polish notation), like some older pocket calculators do. This notation is faster and easier to implement, though it's a bit confusing at first sight.

When you're working with a variable, you'll need to add a prefix to tell OMSI what to do with the variable.
"L.L." means: load value of the given local variable (local means: for that particular vehicle)
"S.L." means: save value into given local variable
"C.L." means: load value of the given local constant.

Basic example: We want to multiply the local variable "test" by 2, add the constant "summand" and save the result into the variable "result":

(L.L.test) 2 * (C.L.summand) + (S.L.result)

Rüdiger Hülsmann schrieb:

"Just plug in a script engine" sounds a bit optimistic. As we were unfamiliar with external script engines, we have developed our own.

I don't think it's easier to develop a script engine than learn about external engines, and use it. Moreover it was surely harder(because you've worked with something that is already made by others).
This script engine makes a lot of addon developers to stop/ or don't even try to develop for omsi. The RPN is just a little problem, that's easy to get used to it, but the syntax and other formalitlies of the script needs too much time and fatigue to get used to it.
There are very few games that have own script engine (i know just ofp and it's successors (arma,arma2) but those also using a c++ like script language because that time when OFP released there wasn other script engines, which is is easy to use), but now there is lua, which is used in huge amount of games.

I don't think that our script language will prevent people from making addons. In fact, there are some already, despite the lack of an SDK. Once the complete SDK is out, there will be a profound explanation of the script engine and thus more comprehension and thus again, more developers and addons. After all, these differences, apart from the RPN style, only concern the notation, just like in other programming languages. BEGIN...END in Delphi, {...} in C. Every programming language needs some time getting used to it and so does OMSI script too, of course. The only real difference I see (yet again apart from the RPN style) is that the variables and constants are defined in an external file and that the prefix types must match when using them. Nothing that cannot be taken in within a few days working with it.

Rüdiger Hülsmann schrieb:

I don't think that our script language will prevent people from making addons. In fact, there are some already, despite the lack of an SDK. Once the complete SDK is out, there will be a profound explanation of the script engine and thus more comprehension and thus again, more developers and addons. After all, these differences, apart from the RPN style, only concern the notation, just like in other programming languages. BEGIN...END in Delphi, {...} in C. Every programming language needs some time getting used to it and so does OMSI script too, of course. The only real difference I see (yet again apart from the RPN style) is that the variables and constants are defined in an external file and that the prefix types must match when using them. Nothing that cannot be taken in within a few days working with it.

Vbus helped kicked off my very beginnings in programming in Delphi, have not used Borland Delphi since 2005! These days it is mainly PHP since I run a website which I have made using php scripting routines. This scripting engine (MR script) is interesting to say the least with the reverse polish notation. I have seen scripts in MR scripts with two "++", no idea what the double "++" means.

On one of my working add ons for the ZF transmsision I did managed to expanded torque converter coverage to gear 3, sans 2C. It seems all that is required is || to be placed after the script. Apparently || is used as "OR". In my case, " (L.L.antrieb_getr_aktugang) 1 = || (L.L.antrieb_getr_aktugang) 3 = || ". I think the script is actually easy, yet between the German and Reverse Notation of the script, it can look complicated at first.

Still have no idea how to script out a turbocharger though...

It seems as if MR script uses the same operators as found in PHP though.

http://www.w3schools.com/PHP/php_operators.asp

krtz07 schrieb:

It seems as if MR script uses the same operators as found in PHP though.

Not always, look for example at the "equal" comparision operator, in OMSI script it's "=", but in PHP it's "==", because "=" would set a new value to the variable and thus return true

But I see your point, in some parts it seems quite similar.

Rüdiger Hülsmann schrieb:

I don't think that our script language will prevent people from making addons. In fact, there are some already, despite the lack of an SDK. Once the complete SDK is out, there will be a profound explanation of the script engine and thus more comprehension and thus again, more developers and addons. After all, these differences, apart from the RPN style, only concern the notation, just like in other programming languages. BEGIN...END in Delphi, {...} in C. Every programming language needs some time getting used to it and so does OMSI script too, of course. The only real difference I see (yet again apart from the RPN style) is that the variables and constants are defined in an external file and that the prefix types must match when using them. Nothing that cannot be taken in within a few days working with it.

I know about 2 projects that are stalled because of scripting. Everything is ready including the 3d model.
Not just the rpn style is the difference. There are no languages that needing those {} and () at the instructions, these symbols make the code hard to understand, since in other languages these have different meanings. Also these load constant/variable, save variable things are confusing, that syntax looks like to access an object's variable who worked with object oriented programming, and also on other languages, the operators say what is needed to do with the variables, constants, and no needed to seperately tell that you want to load or save the variable.A lua language script is more easier to understand(even if the code not formatted well like this), since it's very similar to other popular languages. And have a parser to quickly check your script syntax. omsi script needs much time to get used to it(more than other languages), which isn't too inviting.