OMSIWiki - User contributions [en]

Main Page

2012-07-17T11:38:37Z

Marcel Kuhnt: In progress

'''Welcome on the English version of OMSIWiki!'''

Here you can continue directly to one of the main categories:

* [[FAQs - Frequently Asked Questions]]
* [[:Category:Driving the Bus|Driving the Bus]]
* Developing Addons:
** [[:Category:Developing Reference|Reference]]
** [[:Category:Developing Tutorials|Tutorials]]
** [[:Category:Developing Tips and Tricks|Tips and Tricks]]
* [[:Category:Linked Projects|Linked Projects (e.g. Addon-Manager, OAT)]]
* [[:Category:Addon Presentations|Addon Presentations]]
* [[:Category:Background Information|Background Information]]

'''Attention: Before changing and creating articles, please read our rules first!''' You will find a very short wiki manual further down, too.

''In progress:''


* --[[User:Dario|Dario]] 10:19, 17 July 2012 (MEST) Translating some articles

== Idea ==

We (the developers of OMSI) have installed OMSIWiki for getting a better platform for every kind of information dealing with OMSI. At the moment, we plan to have the following topics:

* Presentation of background information about addon design by us (creating of objects and vehicles, sound engine, script engine and so on)
* Tipps and tricks or even entire tutorials written by users, e.g. about creating repaints or maps
* Using of OMSI and especially driving bus could be another topic. Of course there exists a manual, but perhaps there are some things which can be explained a little bit better by other users?
* Also presenting additional projects dealing with OMSI could be another function of this wiki; we think about OAT or the Addon-Manager.
* This wiki could also be the right place presenting high quality and complex addons, e.g. manuals for addon buses or descriptions and schedules for addon maps. But we don't want tiny articles about repaints or something like that! For this you can better use our forum.
* Of course you can also present background information about our maps/buses or addon maps/buses (e.g. stories about the real bus service of Berlin in 1989). But it should be a serious article really dealing with OMSI! Don't write unnecessary tiny articles don't dealing with any addon of OMSI!

== Rules ==

=== Does my new article fit into OMSIWiki? ===

Each article should fit in one of the categories on the top of this page!

=== "Golden Rule" ===

First of all the '''"golden rule"''': Before writing or changing an article, please check out if there are changes in our rules! Mainly in the time of commencement, there could be rule changes more often.

=== Do's ===

* If you find a tiny or big mistake, everybody is invited to correct it (even if it depends one of our articles)! But you should feel confident doing that!
* You think one of our articles is too abstract? Then just add a nice example! E.g. I know that I tend to write too "dusty" and abstract if I have to write long technical texts.
* You find a technical term which is not be explained? If you find it in Wikipedia, just place an external link. If it is an unexplained term of OMSI, you could add a small article about it.
* To avoid double writings while you have not finished your article, please add the line "''Note: This article is still in development!''". This can be also useful if someone likes to translate it.
* If your article has an equivalent in the German language section, please link them together! Otherwise, please add a note like "''Note: This article still has no German equivalent!''" or "''Note: The German equivalent still is not up to date!''".
* If you have fun translating articles, you are very welcome here! If you find one of these notes, feel free to translate the article! (German => English or the other way round!) But you should inform the author of the original article later that he gets the chance to read and check your translation. If you have translated something, please remove the notes and add the links!

=== Don't Do's ===

* '''Very important: Please think well about the title of a new article! It is not possible to correct it easily. If you add dowdy article titles careless, you will get the chop!
* bad style in writing! Ok, my English could be much better - but everyone writing here should take trouble writing good articles! Of course if you will find a mistake, you are invited removing it! ;)
* just advertising unknown, small projects, forums, virtual companies and so on. The idea behind OMSIWiki is not the advertising of projects but being an information platform!

=== Communication ===

* Before starting your work, add a brief description and your signature into the "in progress" section on top of this page.
* If you would like to do larger changes on one of our articles, it would be very kind to inform us and we can keep track of everything.
* Before starting a new article, it could not be bad informing us about your intention via e-mail!
* Don't create new categories without our agreement!

* Please mind the possibility to discuss on the discussion page! Typical source code you will find on Wikipedia discussion pages. And don't forget: the signature can be generated with <nowiki>--~~~~</nowiki>.

=== Multilinguality ===

OMSIWiki was installed in two languages: English and German. Like on the well-known Wikipedia, articles of both languages can be linked together. Of course it would be ideal if both parts of OMSIWiki are on the same state. Of course in practice, this aim cannot be achieved completely...

=== Access ===

In difference to Wikipedia, you have to have an account to make changes. But I don't think that we expect too much... we hope this could be a useful sanction keeping enough control about the wiki.

== Manual ==

Some hints for newbies who do not like to read the complete manual. How do I "build" an OMSIWiki article?

* Signature: Click on the button or write <nowiki>--~~~~</nowiki>.
* Create a new article: After let us know via e-mail or forum, type the well-considered name for the new article into the "search" field and click on "Go". Because this page does not exist, OMSIWiki will ask you if you would like to create a new article with this name. Just click on "yes" and get to the empty editor.
* A sensible structure can be created like this:
== Main Title ==
=== Sub Title ===
==== Sub Sub Title ==== and so on.
* Lists (like this one) can be created like this:
* Point
* Point
** Sub Point
* A # instead of a * will create a numbered list.
* Bold and italic:
<pre>
''Italic''
'''Bold'''
</pre>
* You can add your article to a category (e.g. ''Driving the Bus'') by adding <nowiki>[[Category:Driving the Bus]]</nowiki> at the bottom of your article.

Further information about creating wiki articles:

[http://meta.wikimedia.org/wiki/Help:Contents http://meta.wikimedia.org/wiki/Help:Contents]

== History ==

* Sept. 9th 2011 - Marcel Kuhnt: Creating of the English Main Page of OMSIWiki
* Sept. 13th 2011 - Marcel Kuhnt: OMSIWiki is now public

== Links ==

* [http://www.omnibussimulator.de/english.htm www.omnibussimulator.de] - official website of OMSI]
* [http://omnibussimulator.forumieren.com omnibussimulator.forumieren.com] - official OMSI forum

== Other ==

[[Technical Information about MediaWiki]]

[[de:Hauptseite]]

FAQs - Frequently Asked Questions

2012-07-17T11:38:08Z

Marcel Kuhnt: Gliederung

== Buying OMSI and Functional Range ==

=== Where can I buy OMSI? ===

You can buy OMSI e.g. via [http://www.aerosoft.com Aerosoft] as boxed or download version.

=== How expensive is OMSI? ===

In recommended retail price is 29,99 EUR.

=== Which vehicles are included in OMSI? ===

OMSI includes the famous Berlin doubledeckers SD200 and SD202, each in serveral series with their prototypical differences. The buses can be fitted with about 20 authentic advertising liveries of the 80s. Additionally, OMSI is an open platform for addons, so it is possible to add further buses or liveries made by third party developers.

=== Which Routes are included in OMSI? ===

OMSI contains the old BVG omnibus line 92 which runs from Spandau, Freudstraße to Heerstraße Stadtgrenze (today's name: Hahneberg) in the very west of Berlin. Today this line is called M37/137, but our simulation puts the route back in the 80s, shortly before German reunification.

=== Will there be ticket sale in OMSI? ===

Yes.

=== Will there be blinkers and animated rear-view mirrors? ===

Both are possilbe. And both will be used just like in real life, so you will find the rear-view mirrors just where you would expect them to be, not in an additional window.

=== Can you drive with joystick or steering wheel in OMSI? ===

Yes. There are three ways to drive a bus in OMSI:
* using the keyboard
* using the mouse
* using joystick or wheel. OMSI supports force-feedback effects so you can feel the engine vibrating and you need to put different effort in steering, depending on the current speed. Of course OMSI fully supports wheels with 900° steering angle.

=== Do you operate the handles and buttons by keyboard or mouse? ===

Both is possible. You can freely define key combinations for any function and of course use the mouse to push buttons or move handles.

=== Which views can be selected? ===

You can choose between four different views:
* Driver view: you can select a view from the driver’s seat, e.g. to the front, to the door or looking in the mirror.
* Passenger view: You can take a seat at various positions in the passenger compartment.
* External view: You can watch the bus from outside. The view moves with the bus while driving.
* Free view: You can move freely on the map.
Furthermore there will be view-hotkeys e. g. for a quick glimpse on the timetable. In all views you can pan or zoom as you like.

=== Does OMSI support TrackIR? ===

Yes, TrackIR 5 will be supported.

=== Will there be working matrix displays, passenger information systems and announcements? ===

Matrix displays will be possible, grid matrices as well as full matrices. They can be operated using the keyboard or using the simulated information-device just like the real thing. Manual or automatic announcements will be possible.

=== Will there be a multiplayer mode? ===

No, but we keep that in mind for future releases.

=== Will there be road traffic, pedestrians, passengers and other buses? ===

Yes, there will be road traffic and pedestrians. Passengers get on and off and take their seat in the bus. There will be other AI-buses, too.

=== Will there be lines and timetables? ===

Yes. Lines and routes can be defined in the track editor and can be imposed on the corresponding buses. So the AI buses use the same timetable as you do, making you feel part of the whole thing.

=== What happens at the terminus? ===

The same things that happen in reality. Have a break, look at the beautiful omnibus, walk around, explore the scenery (thermos bottle and cigarette won’t be simulated ;-)) and don’t forget to begin your return journey on time.

=== Is it possible to walk around? ===

No, this is not possible in the current version. Perhaps we will include this later.

=== Will there be an evaluation of your driving at the end? ===

Yes. Several factors like punctuality will be considered.

=== Do you need any additional windows while driving? ===

No, all the information you need can be found where you would find it in reality. Furthermore, some values like speed, odometer, time and script variables can be displayed. But this is intended only for testing purposes.

=== Does OMSI provide any driving aids? ===

In general, you will have to find your way and the correct stops on your own, just like a real bus driver. Of course, this knowledge will be provided previously. For this, OMSI will include a general map. Furthermore, additional direction signs can be activated while driving.

=== Will there be traffic lights in OMSI? ===

Yes. The traffic lights can be controlled via script as well, so you can define phases, time of circulation and more for every intersection. Whether there will be a traffic-dependent control mechanism is still to be discussed.

=== Will there be only a windows version of OMSI? ===

Yes. OMSI is based on DirectX, so we can’t easily adapt it to another OS.

== Setup and Problems ==

=== Who will do the support for all problems depending download, registration, activation or Aerosoft Launcher? ===

If you have problems with these things, please contact the Aerosoft Support!

=== I have the boxed version and I cannot install the Patch 1.01! ===

The boxed version does already contain the patched version 1.01, therefore the installation of this patch is not possible.

=== The file "d3dq28.dll" cannot be found! ===

To solve this problem, please reinstall DirectX 9.

=== Why does OMSI crash while launching/closing or why do I get the error message "File access denied" ("Dateizugriff verweigert") ? ===

If you have Windows Vista or 7, it could be necessary to run OMSI as Administrator. Please click with the right mouse button on the OMSI icon and choose "Run as Administrator".

=== I cannot choose the lines 92E or 13N! ===

You have to check the correct day and time. The 13N can only be selected at night, the 92E can only be selected on weekdays, not on school holidays and only in the late morning or the early evening.

=== The rear-view mirrors are black and show nothing. ===

The "realtime reflections texture size" in the OMSI "Graphics (Advanced)" properties may not be larger then the vertical screen resolution. The value 512 should work in each case.

=== The bus jumps uncontrollable. ===

This happens only if the frame rate is extremely low. You have to reduce the graphics and/or AI settings. Please try "Minimum" or "PC of 2006".

=== Collisions with a larger number of vehicles involved build up while having a bad frame rate until all vehicles are jumping! ===

Please deactivate the option "AI-car-AI-car-Collisions". Switching this option off will deactivate all collisions between AI vehicles which reduces the needed performance power and will make the simulation more stable.

'''STILL UNDER CONSTRUCTION!'''

=== Objects and parked cars sink through the ground after collisions. ===

To avoid this, activate the option "Terrain Collisions".

=== The outlines are pixeled and the textures unsharp. ===

Activate "anti Aliasing" and "anisotropic filtering" in your graphics card driver options (rightclick on desktop).

=== While driving, the screen will become black suddenly. ===

Sometimes (especially with NVIDIA cards) it may happen that the driver crashs. Since OMSI version 1.01, the driver will restore automatically after a short moment.

=== While loading a large map, OMSI do not react anymore and seems to be crashed. ===

Please expect that the loading process of a map like Spandau can take some minutes.

=== While loading a self created map I will get an access error ("Zugriffsverletzung"). ===

Often this happens if the schedules are erroneous. In this case you should create new schedules. Before doing this, you should delete all schedules by deleting the content of the "TTData" directory of your map (make a backup before!).

=== The IBIS unit shows the message "Falsche Route" (wrong route) ===

If line and route number are entered correctly, an incorrect chosen depot (while adding the bus) could be the reason. Please varify choosing the correct depot fitting to the map.

=== Where are the bus stop announcements? ====

Only the D92 is fitted with an audio bus stop announcement system. You have to program the IBIS (choose line/course and route). The Grundorf map has no announcements.

=== The indicator lights on the dash board on newer buses and/or the matrix illumination are not working. ===

Please verify that you have activate the options "Night Map" and "Light Map" on the enhanced graphics options.

=== I cannot install my hardware steering wheel in OMSI. ===

Since version 1.01 you get a small wizard (AutoConfig) which will help you setting up your steering wheel automatically. Attention: Please follow the instructions exactly!

=== While using my PC steering wheel, the brake and the steering are highly sensitive. ===

Use the characteristics "bi-progressive" for the steering and "progressive" for the brake. If you use a combined throttle/brake axis, use also "bi-progressive" here.

=== How can I play OMSI in fullscreen mode / how can I find the Map Editor? ===

You will find both icons in the Windows start menue.

=== Which function have *.ams files? ===

These files are installation files of the [[OMSI Addon Manager]].

== Possibilities for creating Addons ==

=== Can you create your own sceneries and vehicles? ===

Basically, OMSI is designed as an open system and a platform for any kind of add-ons. There will be a graphic track editor, so everyone can build their own landscapes, streets and bus lines. Of course you can create your own vehicles, too. We recommend Blender as a construction tool. The driving characteristics can be manipulated using the included scripting language.

=== Does OMSI support articulated buses? ===

This feature will become available once we have published our first articulated bus.

=== Can you import existing models? ===

If the models use the x-format, that shouldn’t be a problem.

=== Can you edit the existing textures? ===

Yes. OMSI textures are stored as bmp, tga or dds files.

=== Are the model files in OMSI readable or encrypted? ===

Both is possible. OMSI can process normal x-files and secured binary files in the “o3d”-format that can’t be read externally. There will be a converter so you can change x-files to o3d-files.

=== Which vehicle functions are possible in OMSI? ===

Generally spoken, there is no limit. Nearly any function a real omnibus provides can be simulated in OMSI.

=== What does the script engine offer? ===

The script engine enables the user in a simple way to alter the driving characteristics and functions of a vehicle. Every vehicle in OMSI is originally just a wagon with a certain number of axes that can be influenced by traction or braking forces. The scripts then tell OMSI how this should be done. That means you can create every kind of gearboxes (gear change, torque converter, retarder, kickdown, etc.), air brakes (spring-loaded brakes, parking brake, compressor, protection valve, etc.) or any other functions like door operation, wipers, heating, lighting and so on in a realistic way. There are no internal limits, thus even nonstandard things like a hybrid drive can be simulated.

=== Do I need programming skills for scripting? ===

Programming skills are a great advantage even though the scripting language differs from the programming syntax you might be used to. Anyway, due to its logical design, it is very easy to learn. Of course there will be a comprehensive documentation.

=== What does the graphics engine offer? ===

* realistic day / night effects
* realistic weather conditions
* extensive lighting functions with overlapping effects
* mirror and reflection textures as well as bumpmapping
* different types of transparency
* freely editable spline-roads with slopes and banks
* any number of terrain tiles of 300m*300m each
* meshterrain with many modelling possibilities for creating hills, etc.

=== What does the sound engine offer? ===

* authentic simulation of the original vehicle sound, controlled via script
* freely definable values and curves for pitch, volume and playing conditions
* ambient sounds like rain or church bells
* different sounds for inside and outside
* stereo and doppler effect

=== What kind of model animation will be possible? ===

Basically, any animation can be controlled via script. Wheels, doors and any operation handles or buttons are animated of course and can be controlled by the user’s input.

== Questions about the developers and the future ==

=== Will you create articulated buses, single deck buses and/or modern buses or buses from other countries?

We are still planning making OMSI ready for articulated buses. In case of creating an articulated bus, we will surely also create the appropriate single bus. But there is no mandatory time planing. Modern buses or buses from other countries are not planned.

=== Will there be a demo version later? ===

No, there is no planning for that.

=== You have been well-known for years in the Flight Simulator, BVE and TRS scene. How did you get the idea of developing an omnibus simulator? ===

Well, after our subway projects, OMSI fulfils another of our childhood dreams. Both of us had always longed for a decent omnibus simulator, so with our subway programming experience, we finally started to put the idea into practice. That was in February 2007 by the way, just to let you know how much effort has to be put in such a simulator.

[[de:FAQs - Häufig gestellte Fragen]]

File:Beispiel-Plugin.jpg

2011-11-18T17:15:09Z

Marcel Kuhnt: User Interface of Example Plug-In

User Interface of Example Plug-In

Plug-In Interface

2011-11-18T17:11:14Z

Marcel Kuhnt: Translated from German OMSIWiki

= Main Principle =

You can program plug-in DLLs which have reading and writing access to the vehicle variables and which can activate triggers.

Each plugin consists of a [[Configuration File]] with the extension *.opl and a corresponding DLL. Both files have to be in the directory "OMSI\plugins".

= Description of the Example Plug-In =

OMSI contains already an example plug-in. You can activate it in renaming the file "test.txt" into "test.opl" (you will find it in the directory "OMSI\plugins").

== Functional Range ==

This plug-in has three functions: A speedometer (analog and digital) on top, a track bar to set the red heater handle (even if it calls it "Rollband-Sollwert") and a door button named "Button1" (with the same function like the [Num /] key).

[[File:Beispiel-Plugin.jpg|600px|thumb|right|User interface of the example plug-in]]

== Format of the *.opt File ==

<pre>
To activate, rename this file to "test.opl"

[dll]
Test.dll

[varlist]
2
Velocity
cockpit_heizregler_temp

[triggers]
1
bus_doorfront0
</pre>

The first line is just a comment line. The command [dll] indicates the file name of the corresponding DLL.

The [varlist] command starts with the expected number of (only local!) vehicle variables. You can also use user variables of a special bus type. Of course this won't have any effect, if the driven bus has not these user variables.

In this example, the variable with index 0 is "Velocity", the variable with index 1 is "cockpit_heizregler_temp".

The [triggers] command starts with the number of the expected triggers. In this case, there is only one trigger: "bus_doorfront0" with index 0.

== Format of the DLL ==

With the shown example, I give you the corresponding Delphi Code. In general it should be possible to create DLLs with other programming languages, but I never tested that.

The DLL contains of two units, but I present you only the main unit (the second unit does not contain any important implementations):

<pre>
library Test;

uses
SysUtils,
Dialogs,
Classes,
TestU in 'TestU.pas' {Form1};

{$R *.res}

procedure Start( AOwner: TComponent ); stdcall;
begin
form1 := TForm1.Create( AOwner );
form1.Show;
end;

procedure Finalize; stdcall;
begin
form1.Free;
end;

procedure AccessVariable( varindex: word; var value: single; var write: boolean ); stdcall;
begin
case varindex of
0:
begin
form1.Label2.Caption := floattostrF( value, ffFixed, 5, 1 ) + ' km/h';
form1.Gauge1.Progress := round( value );
write := false;
end;
1:
begin
value := form1.TrackBar1.Position / 30;
write := true;
end;
end;
end;

procedure AccessTrigger( triggerindex: word; var active: boolean ); stdcall;
begin
case triggerindex of
0:
begin
active := form1.button1_pressed;
end;
end;
end;

exports
AccessVariable,
AccessTrigger,
Start,
Finalize;

begin
end.
</pre>

First of all note the last section "exports": It contains the four needed procedures of the DLL: ''AccessVariable'', ''AccessTrigger'', ''Start'' und ''Finalize''.

These four procedures have the following functions:

=== ''Start'' ===

''Start( AOwner: TComponent )'' will be called at the beginning and allows the DLL to initialize itself. In this example, it creates ''Form1'' and puts it to the same named variable (which is part of the second Unit). The second step is calling the ''Show'' command to make ''Form1'' visible. ''Start'' hands the parameter "AOwner" over, the Handler of the main form of OMSI.

=== ''Finalize'' ===

''Finalize'' will be called while closing OMSI. In the example, ''Form1'' will be destroyed and freed.

=== ''AccessVariable'' ===

While running OMSI, this procedure will be called for all variables listed in the *.opl file. The index of the variable will be handed over via the variable ''varindex''. The procedure can write now ''value'' and ''write''.

If you just would like to read a vehicle variable, you just have to read ''value'' like in the case "0:". But it is also possible (like in "1:") to give a new value to ''value''. In this case you have to set ''write'' to ''true'' to advise OMSI to use the new value. In the example, the position of the track bar will be used as new value of the variable with index 1 ("bus_doorfront0").

=== ''AccessTrigger'' ===

This procedure is very similar to ''AccessVariable'', but OMSI will use the trigger list of the *.opl file. The DLL can set ''active'' to ''true'' and can trigger the event.

[[Category:Developing Reference]]

[[de:Plug-in-Schnittstelle]]

Category:Developing Reference

2011-11-16T17:57:40Z

Marcel Kuhnt: Created page with "Here you will find all articles which an help as reference while developing addons."

Here you will find all articles which an help as reference while developing addons.

Configuration File

2011-11-16T17:56:43Z

Marcel Kuhnt: Translated from German version

== Definition ==

Configuration Files (or shorter: config files) are all files which supply OMSI with external data and constants and which do not include executable code like the files of the [[script system|Scripts]]. They are plain text files and are following a special syntax developed for OMSI. There are lots of config files:

* options.cfg, envir.cfg, gamectrl.cfg and keyboard.cfg for global OMSI parameters

* global.cfg and all associated *.map files of the maps

* *.sco-, *.sli-, *.bus-, *.ovh- and *.hum-files, which contain the general and physical data of scenery objects, splines, vehicles and humans

* Model, sound, texture change, cabin and path files with the ending *.cfg, which contains further information about 3D objects

== Syntax ==

The syntax of config files follow a scheme which is quite simple but not very common. The basic rules is:

'''OMSI reads only lines which are following a key word!'''

=== Examples ===

In the following examples, we imply that ''[keyword]'' is a key word of this config file and that OMSI expects three values following:

<pre>
This is a comment, because there is no key word leading.
So OMSI do not care about this lines until there is no key word.
</pre>

In the upper example, nothing will happen.

<pre>
[keyword]
1
2
3

This was a valid command which was introduced by [keyword].
After the three parameters were read, OMSI again searchs for key words and ignores everything else (like these two lines).
</pre>

Now we had a command which allot the values 1, 2 and 3 to the three parameters. '''In front of and behind the key word there must not stay any other character, even no tab or space!'''

Wrong:

<pre>
[keyword]
1
2
3
</pre>

Wrong:

<pre>
[keyword] Comment
1
2
3
</pre>

With this knowledge, it is very simple to comment commands out - you just have to add at least one character:

Not commented out:

<pre>
[keyword]
1
2
3
</pre>

Commented out:

<pre>
[keyword]
1
2
3
</pre>

... or ...

<pre>
[keyword]##
1
2
3
</pre>

'''Attention!''' Not every command follows the convention "[...]"! Also these which are not bracked, follow the convention explained.

Some commands / key words expect a quantity of parameters first, so that the count of read lines by OMSI depends of this number. One example of this behaviour is the command to include scripts in a scenery object or vehicle:

<pre>
[script]
3
script\script1.sco
script\script2.sco
script\script3.sco
</pre>

Finally, there are some key words which expect an ''[end]'' command like e.g. the command ''[description]'':

<pre>

[description]
Der MAN SD 200 ...

-Technische Daten-

Länge: 11.490 mm
Breite: 2500 mm
Höhe 4060 mm

Motor: MAN D2566MUH, 141 kW bei 2100 U/min
Getriebe: Voith D851
Höchstgeschwindigkeit: 75 km/h

Leergewicht: 10700 kg
Zulässiges Gesamtgewicht: 16.000 kg

Sitzplätze Oberdeck: 53
Sitzplätze Unterdeck: 35
Stehplätze: 8
[end]

</pre>

[[Category:Developing Reference]]

[[de:Configuration File]]

Suggestions For Setting Up Steering Wheels

2011-11-16T17:33:28Z

Marcel Kuhnt:

== Logitech G25 ==

=== Axis ===

{| class="wikitable" style="font-size:95%;"
|- class="hintergrundfarbe5"
| align="left" |X
| align="left" |Steering (not reverse, linear)
|-
| align="left" |Y
| align="left" |Throttle (reverse, degressive)
|-
| align="left" |Rz
| align="left" |Brake (reverse, progressive)
|-
| align="left" |Slider 2
| align="left" |Clutch (reverse, narrowed, linear)
|}

=== Buttons ===

{| class="wikitable" style="font-size:95%;"
|- class="hintergrundfarbe5"
|-
| align="left" |1
| align="left" |Automatic Gearbox: 1
|-
| align="left" |2
| align="left" |Automatic Gearbox: D
|-
| align="left" |3
| align="left" |Automatic Gearbox: N
|-
| align="left" |4
| align="left" |Automatic Gearbox: Reverse
|-
| align="left" |5
| align="left" |View - Scroll Interior Perspectives
|-
| align="left" |6
| align="left" |View - Scroll Interior Perspectives (reverse)
|-
| align="left" |7
| align="left" |Blinker Right via Off <== IMPORTANT "VIA OFF"!!! At the very end of the list.
|-
| align="left" |8
| align="left" |Blinker Left via Off
|-
| align="left" |9
| align="left" |Manual Gearbox: 1st Gear
|-
| align="left" |10
| align="left" |Manual Gearbox: 2nd Gear
|-
| align="left" |11
| align="left" |Manual Gearbox: 3rd Gear
|-
| align="left" |12
| align="left" |Manual Gearbox: 4th Gear
|-
| align="left" |13
| align="left" |Manual Gearbox: 5th Gear
|-
| align="left" |14
| align="left" |Manual Gearbox: 6th Gear
|-
| align="left" |15
| align="left" |Manual Gearbox: Reverse Gear
|-
| align="left" |16
| align="left" |any
|-
| align="left" |17
| align="left" |any
|-
| align="left" |18
| align="left" |any
|-
| align="left" |19
| align="left" |any
|}

== Logitech MOMO ==

=== Axis ===

{| class="wikitable" style="font-size:95%;"
|- class="hintergrundfarbe5"
| align="left" |X
| align="left" |Steering (not reverse, linear)
|-
| align="left" |Y
| align="left" |Throttle (reverse, degressive)
|-
| align="left" |Rz
| align="left" |Brake (reverse, progressive)
|}

=== Buttons ===

{| class="wikitable" style="font-size:95%;"
|- class="hintergrundfarbe5"
|-
| align="left" |1
| align="left" |View - Scroll Interior Perspectives
|-
| align="left" |2
| align="left" |View - Scroll Interior Perspectives (reverse)
|-
| align="left" |3
| align="left" |Set Blinker Right <== the other Command!! This works "direct", not "via off"
|-
| align="left" |4
| align="left" |Horn
|-
| align="left" |5
| align="left" |Set Blinker Off
|-
| align="left" |6
| align="left" |Full Beam On/Off / Flash Light
|-
| align="left" |7
| align="left" |Set Blinker Left
|-
| align="left" |8
| align="left" |Microphone Switch (Announcements)
|-
| align="left" |9
| align="left" |Parking Brake Set <== At the very end of the list again!
|-
| align="left" |10
| align="left" |Parking Brake Release <== At the very end of the list again!
|}

[[Category:Driving the Bus]]

[[de:Lenkrad-Konfigurationsvorschläge]]

Suggestions For Setting Up Steering Wheels

2011-11-16T17:32:16Z

Marcel Kuhnt: Translated from German version

2011-09-12T21:19:17Z

Marcel Kuhnt: Moved text about OAT into a new article

== Foundation and Aims ==

The OMSI Addon Testers (or just "OAT") have been founded on April 30 2011 by Yufa, Felix01 and Janniboy - members of the official OMSI forum ([http://omnibussimulator.forumieren.com/t4415p60-prufung-neuer-maps link to the thread]).
''
Please mind that the founders of the OAT are German, so the website and the test reports are in German as well. There are currently no plans about a multi-lingual website, so please translate the website using any translating software.''

The OAT ([http://www.oat-online.de www.oat-online.de]) wants to rate free OMSI add-ons built by private persons factually and fair. Therewith users get the possibility to inform themselves about an add-on before downloading it; additionally the quality of OMSI add-ons should constantly improve.

The OAT summarizes these aims in one statement:
''"Wir möchten die Autoren aktiv dabei unterstützen, ihre Addons zu perfektionieren."'' (which means: "We actively want to help the authors to perfect their add-ons.").

All members of the OAT do their work voluntarily, everyone is welcome to make an application. You can read more about the demands an add-on tester should meet and about the things that are expected from him [http://oat-online.de/info_bewerben.php here].
''As you might have read above, the OAT is currently completely in German, so please understand that applications of English testers wouldn't make sense at the moment.''

== Testing Procedure and Rating ==

Interested add-on developers can submit their add-on directly using the [http://oat-online.de/einsenden.php onine form].
''Although the OAT is German, English submissions are still welcome! The only thing you should remember: The test report will be in German as well.''

[[Datei:OATIconExplanation.jpg‎|right|Explanation about the OAT icon]] After the testing procedure, The OAT publishes the test report on the official website [http://www.oat-online.de www.oat-online.de]. It contains the single ratings as well as the most important facts (positive and negative lists) and the total credits of the add-on. Transparency is one of the big aims. Thus, the OAT also releases guidelines and recommendations on the website. From the OAT's point of view, the mentioned criteria are elementary for "the perfect add-on"; at the same time they are the scale for the rating.

An add-on can achieve at last 100 credits, this is the same for all submissions; but the criteria vary and are differently weighted depending on the type of the add-on to fit the manifold requirements. The total credits are visualized in the OAT icon (see example image on the right). With this icon, the developer can advertise for his add-on (e.g. in forums or on websites). By doing this, he also shows that he exerts himself on quality.

[[Category:Linked Projects]]

File:2011 0204 04 Falkenseer.jpg

2011-09-12T12:04:56Z

Marcel Kuhnt: Test

Test

Main Page

2011-09-11T09:08:29Z

Marcel Kuhnt:

'''Welcome on the English version of OMSIWiki!'''

Here you can continue directly to one of the main categories:

* [[:Category:Driving the Bus|Driving the Bus]]
* Developing Addons:
** [[:Category:Developing Reference|Reference]]
** [[:Category:Developing Tutorials|Tutorials]]
** [[:Category:Developing Tips and Tricks|Tips and Tricks]]
* [[:Category:Linked Projects|Linked Projects (e.g. Addon-Manager, OAT)]]
* [[:Category:Addon Presentations|Addon Presentations]]
* [[:Category:Background Information|Background Information]]


== Idea ==

We (the developers of OMSI) have installed OMSIWiki for getting a better platform for every kind of information dealing with OMSI. At the moment, we plan to have the following topics:

* Presentation of background information about addon design by us (creating of objects and vehicles, sound engine, script engine and so on)
* Tipps and tricks or even entire tutorials written by users, e.g. about creating repaints or maps
* Using of OMSI and especially driving bus could be another topic. Of course there exists a manual, but perhaps there are some things which can be explained a little bit better by other users?
* Also presenting additional projects dealing with OMSI could be another function of this wiki; we think about OAT or the Addon-Manager.
* This wiki could also be the right place presenting high quality and complex addons, e.g. manuals for addon buses or descriptions and schedules for addon maps. But we don't want tiny articles about repaints or something like that! For this you can better use our forum.
* Of course you can also present background information about our maps/buses or addon maps/buses (e.g. stories about the real bus service of Berlin in 1989). But it should be a serious article really dealing with OMSI! Don't write unnecessary tiny articles don't dealing with any addon of OMSI!

== Manual ==

[http://meta.wikimedia.org/wiki/Help:Contents http://meta.wikimedia.org/wiki/Help:Contents]

== Rules ==

=== Does my new article fit into OMSIWiki? ===

Each article should fit in one of the categories on the top of this page!

=== "Golden Rule" ===

First of all the '''"golden rule"''': Before writing or changing an article, please check out if there are changes in our rules! Mainly in the time of commencement, there could be rule changes more often.

=== Do's ===

* If you find a tiny or big mistake, everybody is invited to correct it (even if it depends one of our articles)! But you should feel confident doing that!
* You think one of our articles is too abstract? Then just add a nice example! E.g. I know that I tend to write too "dusty" and abstract if I have to write long technical texts.
* You find a technical term which is not be explained? If you find it in Wikipedia, just place an external link. If it is an unexplained term of OMSI, you could add a small article about it.
* To avoid double writings while you have not finished your article, please add the line "''Note: This article is still in development!''". This can be also useful if someone likes to translate it.
* If your article has an equivalent in the German language section, please link them together! Otherwise, please add a note like "''Note: This article still has no German equivalent!''" or "''Note: The German equivalent still is not up to date!''".
* If you have fun translating articles, you are very welcome here! If you find one of these notes, feel free to translate the article! (German => English or the other way round!) But you should inform the author of the original article later that he gets the chance to read and check your translation. If you have translated something, please remove the notes and add the links!

=== Don't Do's ===

* '''Very important: Please think well about the title of a new article! It is not possible to correct it easily. If you add dowdy article titles careless, you will get the chop!
* bad style in writing! Ok, my English could be much better - but everyone writing here should take trouble writing good articles! Of course if you will find a mistake, you are invited removing it! ;)
* just advertising unknown, small projects, forums, virtual companies and so on. The idea behind OMSIWiki is not the advertising of projects but being an information platform!

=== Communication with Administrators ===

* If you would like to do larger changes on one of our articles, it would be very kind to inform us and we can keep track of everything.
* Before starting a new article, it could not be bad informing us about your intention via e-mail!
* Don't create new categories without our agreement!

=== Multilinguality ===

OMSIWiki was installed in two languages: English and German. Like on the well-known Wikipedia, articles of both languages can be linked together. Of course it would be ideal if both parts of OMSIWiki are on the same state. Of course in practice, this aim cannot be achieved completely...

=== Access ===

In difference to Wikipedia, you have to have an account to make changes. But I don't think that we expect too much... we hope this could be a useful sanction keeping enough control about the wiki.

== History ==

* Sept. 9th 2011 - Marcel Kuhnt: Creating of the English Main Page of OMSIWiki

== Links ==

* [http://www.omnibussimulator.de/english.htm www.omnibussimulator.de] - official website of OMSI]
* [http://omnibussimulator.forumieren.com omnibussimulator.forumieren.com] - official OMSI forum

== Other ==

[[Technical Information about MediaWiki]]

[[de:Hauptseite]]

Main Page

2011-09-10T14:24:37Z

Marcel Kuhnt: /* Rules */

Welcome on the English version of OMSIWiki!

== Idea ==

We (the developers of OMSI) have installed OMSIWiki for getting a better platform for every kind of information dealing with OMSI. At the moment, we plan to have the following topics:

* Presentation of background information about addon design by us (creating of objects and vehicles, sound engine, script engine and so on)
* Tipps and tricks or even entire tutorials written by users, e.g. about creating repaints or maps
* Using of OMSI and especially driving bus could be another topic. Of course there exists a manual, but perhaps there are some things which can be explained a little bit better by other users?
* Also presenting additional projects dealing with OMSI could be another function of this wiki; we think about OAT or the Addon-Manager.
* This wiki could also be the right place presenting high quality and complex addons, e.g. manuals for addon buses or descriptions and schedules for addon maps. But we don't want tiny articles about repaints or something like that! For this you can better use our forum.
* Of course you can also present background information about our maps/buses or addon maps/buses (e.g. stories about the real bus service of Berlin in 1989). But it should be a serious article really dealing with OMSI! Don't write unnecessary tiny articles don't dealing with any addon of OMSI!

== Rules ==

=== Does my new article fit into OMSIWiki? ===

Each article should fit in one of these categories:

* [[:Category:Driving the Bus|Driving the Bus]]
* Developing Addons:
** Reference
** Tutorials
** Tips and Tricks
* Addon-Manager
* OAT
* Presentation of Addons
* Background Information

=== "Golden Rule" ===

First of all the '''"golden rule"''': Before writing or changing an article, please check out if there are changes in our rules! Mainly in the time of commencement, there could be rule changes more often.

=== Do's ===

* If you find a tiny or big mistake, everybody is invited to correct it (even if it depends one of our articles)! But you should feel confident doing that!
* You think one of our articles is too abstract? Then just add a nice example! E.g. I know that I tend to write too "dusty" and abstract if I have to write long technical texts.
* You find a technical term which is not be explained? If you find it in Wikipedia, just place an external link. If it is an unexplained term of OMSI, you could add a small article about it.
* To avoid double writings while you have not finished your article, please add the line "''Note: This article is still in development!''". This can be also useful if someone likes to translate it.
* If your article has an equivalent in the German language section, please link them together! Otherwise, please add a note like "''Note: This article still has no German equivalent!''" or "''Note: The German equivalent still is not up to date!''".
* If you have fun translating articles, you are very welcome here! If you find one of these notes, feel free to translate the article! (German => English or the other way round!) But you should inform the author of the original article later that he gets the chance to read and check your translation. If you have translated something, please remove the notes and add the links!

=== Don't Do's ===

* '''Very important: Please think well about the title of a new article! It is not possible to correct it easily. If you add dowdy article titles careless, you will get the chop!
* bad style in writing! Ok, my English could be much better - but everyone writing here should take trouble writing good articles! Of course if you will find a mistake, you are invited removing it! ;)
* just advertising unknown, small projects, forums, virtual companies and so on. The idea behind OMSIWiki is not the advertising of projects but being an information platform!

=== Communication with Administrators ===

* If you would like to do larger changes on one of our articles, it would be very kind to inform us and we can keep track of everything.
* Before starting a new article, it could not be bad informing us about your intention via e-mail!
* Don't create new categories without our agreement!

=== Multilinguality ===

OMSIWiki was installed in two languages: English and German. Like on the well-known Wikipedia, articles of both languages can be linked together. Of course it would be ideal if both parts of OMSIWiki are on the same state. Of course in practice, this aim cannot be achieved completely...

=== Access ===

In difference to Wikipedia, you have to have an account to make changes. But I don't think that we expect too much... we hope this could be a useful sanction keeping enough control about the wiki.

== History ==

* Sept. 9th 2011 - Marcel Kuhnt: Creating of the English Main Page of OMSIWiki

== Links ==

* [http://www.omnibussimulator.de/english.htm www.omnibussimulator.de] - official website of OMSI]
* [http://omnibussimulator.forumieren.com omnibussimulator.forumieren.com] - official OMSI forum

== Other ==

[[Technical Information about MediaWiki]]

[[de:Hauptseite]]

Main Page

2011-09-10T07:12:16Z

Marcel Kuhnt: /* Does my new article fit into OMSIWiki? */

Main Page

2011-09-10T07:11:11Z

Marcel Kuhnt: /* Does my new article fits into OMSIWiki? */

2011-09-07T18:47:27Z

Marcel Kuhnt:

Kategorie:Testseiten

2011-09-07T18:44:53Z

Marcel Kuhnt: Anlegen der Kategorieseite

Erste Testseite

2011-09-07T18:43:34Z

Marcel Kuhnt: Anlegen der Testseite

Dies ist die '''Erste Testseite'''! Sie dient zum Testen von Funktionen.

[[Kategorie:Testseiten]]