Bus priority, lights, driving assistance system

AgoraS-114 · 13. Februar 2017

Hello,

Although I understood the fire detection system. I encounter some difficulties in programming, indeed, my goal is quite complex, but I will really want to apply it.

In France, we have a driving aid system that is positioned below the traffic light. This box detects the bus and informs the situation of when it can pass or not, these are security measures.

I would like to put it on OMSI.
This is how it works:

Here, no bus is present, but when the fire is red, the orange diamond is considered a red light :

[IMG: http://www.amsaa.fr/wp-content/uploads/2013/05/ferme.gif]

Here, the orange diamond flashes, indicating that it detected my bus :

[IMG: http://www.amsaa.fr/wp-content/uploads/2013/05/detection.gif]

Here, when the light turns green (error in the image), the orange diamond and blue exclamation point flashes throughout the "Green" :

[IMG: http://www.amsaa.fr/wp-content/uploads/2013/05/prise_en_compte.gif]

And finally, when the light changes to orange, the orange diamond appears in a fixed manner:

[IMG: http://www.amsaa.fr/wp-content/uploads/2013/05/fermeture.gif]

Those are the steps.
A friend of mine has to model all this, no problem with each form per .o3d file!

A file for orange diamond
A file for orange diamond and exclamation point blue
A file for blue exclamation point

Same, no worries for my objects published with OmsiObjEdit, I programmed them without any worries.

But where I block, it's on the scripts, I tried to fiddle as it should, but I still can not, here's where I am:
SAC.osc :

Spoiler anzeigen

Code

'###########################
'Traffic Light Bus Priority
'###########################
'Traffic Light Bus Priority type TCSP
'Phase 12: off
'Else: flashing Green
'(c) 01.6.2010 Marcel Kuhnt
'Script Version: 1.2
'Omsi release: 1.0
'Needs:
'- none
{init}
0 (S.L.Timer)
1 (S.L.Green)
{end}
{frame}
(L.L.TrafficLightPhase) 12 =
{if}
0 (S.L.Timer)
0 (S.L.Green)
{else}
(L.L.Timer) (L.S.Timegap) + (S.L.Timer) s0
1 >
{if}
0 (S.L.Timer)
1 (S.L.Green)
{else}
l0 0.5 >
{if}
0 (S.L.Green)
{endif}
{endif}
{endif}
{end}
{frame}
(L.L.TrafficLightPhase) s0
l0 0 >= l0 5 <= && (S.L.Red)
l0 9 >= l0 11 <= && (S.L.Yellow)
{end}

Alles anzeigen

SAC_varlist.txt :

Spoiler anzeigen

and .sco file :

Spoiler anzeigen

Code

[groups]
3
St-Servan
Mobilier Urbain
Variante noire
[friendlyname]
Sagem Aluxe SAC
[trafficlight]
[mesh]
Sagem_Aluxe_SAC.o3d
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Red
1
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Yellow
1
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
TrafficLightApproach
1
[mesh]
Sagem_Aluxe_SAC_losange-exclamation.o3d
[visible]
Green
1
[script]
1
script\SAC.osc
[varnamelist]
1
script\SAC_varlist.txt
Detail-Faktor: hiermit kann eingestellt werden, ob das Objekt als größer oder kleiner angenommen wird.
Der Wert wird einfach mit dem in den Graphik-Optionen eingestellten Wert multipliziert, d.h.:
* 0.5 = Objekt wird bereits dargestellt, wenn es nur halb so groß ist, wie der eingestellte Wert
* 1.0 = Objekt erscheint genau dann, wenn es so groß ist wie eingestellt
* 2.0 = Objekt erscheint erst dann, wenn es schon doppelt so groß ist wie eingestellt.
[detail_factor]
0.1

Alles anzeigen

Do you have any idea how it works?

Thanks

Unorthodox Paradox · 13. Februar 2017

Hi,

the following implementation should satisfy your requirements--if I interpreted them correctly. Note that, since I have no convenient means of testing it, it may be erroneous.

.osc

Code

{frame}
' increment timer only during red or green phase; otherwise ignore
(L.L.TrafficLightPhase) 0 max 12 min s0 9 <
{if}
(L.L.Timer) 1 <
{if}
(L.L.Timer) (L.S.Timegap) + 1 min (S.L.Timer)
{else}
0 (S.L.Timer)
{endif}
{else}
0 (S.L.Timer)
{endif}
' red
l0 6 <
{if}
1 (S.L.Red)
0 (S.L.Yellow) (S.L.Green)
(L.L.TrafficLightApproach)
{if}
(L.L.Timer) 1 =
{if}
(L.L.Diamond) ! (S.L.Diamond)
{endif}
{else}
1 (S.L.Diamond)
{endif}
0 (S.L.ExclamationPoint)
{else}
' green
l0 9 <
{if}
1 (S.L.Green)
0 (S.L.Red) (S.L.Yellow)
(L.L.Timer) 1 =
{if}
(L.L.Diamond) ! (S.L.Diamond) (S.L.ExclamationPoint)
{endif}
{else}
' yellow
l0 12 <
{if}
1 (S.L.Yellow) (S.L.Diamond)
0 (S.L.Red) (S.L.Green) (S.L.ExclamationPoint)
{else}
' off
0 (S.L.Red) (S.L.Yellow) (S.L.Green) (S.L.Diamond) (S.L.ExclamationPoint)
{endif}
{endif}
{endif}
{end}

Alles anzeigen

Naturally, you will also have to declare the new variables (Diamond, ExclamationPoint) in your var-list file, as well as reference them from your .sco as usual.

AgoraS-114 · 14. Februar 2017

Hello,

First of all, thank you very much for your response, it is very nice of you !!

I conducted multiple tests last night and this morning, but unfortunately, I have reached the orange diamond is affaiche without blinking as TrafficLightApproach only. No blinking, no exclamation point either.

I put my file var and sco:

Spoiler anzeigen

Code

[groups]
3
St-Servan
Mobilier Urbain
Variante noire
[friendlyname]
Sagem Aluxe SAC
[trafficlight]
[mesh]
Sagem_Aluxe_SAC.o3d
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Red
1
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
TrafficLightApproach
1
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Yellow
1
[mesh]
Sagem_Aluxe_SAC_losange-exclamation.o3d
[visible]
Green
1
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Diamond
1
[mesh]
Sagem_Aluxe_SAC_exclamation.o3d
[visible]
ExclamationPoint
1
[script]
1
script\SAC.osc
[varnamelist]
1
script\SAC_varlist.txt
Detail-Faktor: hiermit kann eingestellt werden, ob das Objekt als größer oder kleiner angenommen wird.
Der Wert wird einfach mit dem in den Graphik-Optionen eingestellten Wert multipliziert, d.h.:
* 0.5 = Objekt wird bereits dargestellt, wenn es nur halb so groß ist, wie der eingestellte Wert
* 1.0 = Objekt erscheint genau dann, wenn es so groß ist wie eingestellt
* 2.0 = Objekt erscheint erst dann, wenn es schon doppelt so groß ist wie eingestellt.
[detail_factor]
0.1

Alles anzeigen

I made a mistake by accident?

Thank you

Unorthodox Paradox · 14. Februar 2017

Hi,

according to the script logic, in your scenery object file, the "exclamation point" [mesh] should only be coupled with the ExclamationPoint variable, and, likewise, the "diamond" [mesh] should only be associated with the Diamond variable--not with TrafficLightApproach or any other variable.

Now, I don't know what the 7 mesh entries in your .sco actually represent, thus I can only show you how my (hypothetical) .sco would look like (assuming all 5 light components--the 3 standard plus the 2 special ones--are individual objects):

.sco

Try modifying your .sco file so that it matches the example. If it still doesn't help, my .osc is probably bugged, and I will have to test it in-game to find out what's wrong.

By the way, just to ensure that we're both on the same page, here's the "truth table" that the aforementioned .osc implements:

truth table

Code

+-----------------------------------------------------------------------+
| Legend: |
| 0 : off |
| 1 : on |
| 2 : blinking |
| * : any (input) |
+------------------------------------------+----------------------------+
| Inputs | Outputs |
+-------------------+----------------------+---------+------------------+
| TrafficLightPhase | TrafficLightApproach | Diamond | ExclamationPoint |
+-------------------+----------------------+---------+------------------+
| [0, 6) (red) | 0 | 1 | 0 |
+-------------------+----------------------+---------+------------------+
| [0, 6) (red) | 1 | 2 | 0 |
+-------------------+----------------------+---------+------------------+
| [6, 9) (green) | * | 2 | 2 |
+-------------------+----------------------+---------+------------------+
| [9, 12) (yellow) | * | 1 | 0 |
+-------------------+----------------------+---------+------------------+
| 12 (off) | * | 0 | 0 |
+-------------------+----------------------+---------+------------------+

Alles anzeigen

Would that be correct?

faaabiiii · 14. Februar 2017

What I understood is the following truth table:

Spoiler anzeigen

Which would then lead to a script like this:

Spoiler anzeigen

With this sco file:

Spoiler anzeigen

Code

[groups]
3
St-Servan
Mobilier Urbain
Variante noire
[friendlyname]
Sagem Aluxe SAC
[trafficlight]
[mesh]
Sagem_Aluxe_SAC.o3d
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Losange
1
[mesh]
Sagem_Aluxe_SAC_exclamation.o3d
[visible]
Exclamation
1
[script]
1
script\SAC.osc
[varnamelist]
1
script\SAC_varlist.txt
Detail-Faktor: hiermit kann eingestellt werden, ob das Objekt als größer oder kleiner angenommen wird.
Der Wert wird einfach mit dem in den Graphik-Optionen eingestellten Wert multipliziert, d.h.:
* 0.5 = Objekt wird bereits dargestellt, wenn es nur halb so groß ist, wie der eingestellte Wert
* 1.0 = Objekt erscheint genau dann, wenn es so groß ist wie eingestellt
* 2.0 = Objekt erscheint erst dann, wenn es schon doppelt so groß ist wie eingestellt.
[detail_factor]
0.1

Alles anzeigen

AgoraS-114 · 14. Februar 2017

Hello,

Thank you for your very informative answers, I am grateful!

I tested both methods.

That of Unorthodox Paradox suddenly renders the fire inactive. No sign appears, it remains "off" even when the bus is approaching.
The faaabiiii method simply crashed my map, I see only the sky of the map, there is surely a problem of script.

To clarify the situation, here is the picture I want:

Code

+-----------------------------------------------------------------------+
| Legend: |
| 0 : off |
| 1 : on |
| 2 : blinking |
+------------------------------------------+----------------------------+
| Inputs | Outputs |
+-------------------+----------------------+---------+------------------+
| TrafficLightPhase | TrafficLightApproach | Diamond | ExclamationPoint |
+-------------------+----------------------+---------+------------------+
| [0, 6) (red) | 0 | 1 | 0 |
+-------------------+----------------------+---------+------------------+
| [0, 6) (red) | 1 | 2 | 0 |
+-------------------+----------------------+---------+------------------+
| [6, 9) (green) | - | 2 | 2 |
+-------------------+----------------------+---------+------------------+
| [9, 12) (yellow) | - | 1 | 0 |
+-------------------+----------------------+---------+------------------+
| 12 (off) | - | 0 | 0 |
+-------------------+----------------------+---------+------------------+

Alles anzeigen

This is what I want.

After the tests, here is what my .sco file looks like:

.sco file

Code

[groups]
3
St-Servan
Mobilier Urbain
Variante noire
[friendlyname]
Sagem Aluxe SAC
[trafficlight]
[mesh]
Sagem_Aluxe_SAC.o3d
[mesh]
Sagem_Aluxe_SAC_losange.o3d
[visible]
Diamond
1
[mesh]
Sagem_Aluxe_SAC_exclamation.o3d
[visible]
ExclamationPoint
1
[script]
1
script\SAC.osc
[varnamelist]
1
script\SAC_varlist.txt
Detail-Faktor: hiermit kann eingestellt werden, ob das Objekt als größer oder kleiner angenommen wird.
Der Wert wird einfach mit dem in den Graphik-Optionen eingestellten Wert multipliziert, d.h.:
* 0.5 = Objekt wird bereits dargestellt, wenn es nur halb so groß ist, wie der eingestellte Wert
* 1.0 = Objekt erscheint genau dann, wenn es so groß ist wie eingestellt
* 2.0 = Objekt erscheint erst dann, wenn es schon doppelt so groß ist wie eingestellt.
[detail_factor]
0.1

Alles anzeigen

Do you have an idea ?

Unorthodox Paradox · 14. Februar 2017

Hi,

I just noticed that the Timer variable is absent from your var-list. Other than that, I am fairly sure that the script works, as I just tested it (using a conventional M+R object).

As an aside, if you don't care about the "standard" 3 lights, I can simplify the script so as to not record their respective states (although it shouldn't really matter, performance-wise...).

AgoraS-114 · 14. Februar 2017

After adding Timer, same problem, the fire remains inactive, it's really weird.

I make clear that my fire modeled on Blender is a fire apart, which resembles that one

[IMG: http://img110.xooimage.com/files/d/9/2/feu-sac-519ca03.png]

There is no classical fire, I add them myself using those of Helferlein. There is only the fire with the diamond and exclamation mark that was created by me.

Unorthodox Paradox · 14. Februar 2017

This is curious indeed, I'm running out of ideas.

Are there any errors recorded in your logfile? Additionally, ensure that the script file only contains the {frame} block I posted initially (since your script in the opening post contained 2 {frame}s, which is incorrect), and no {init} block.

AgoraS-114 · 14. Februar 2017

MIRACLE! It works !!!!
My 3d files had some texture worries, which impacted the blow!

Everything works, but a single and small enough annoying flaw, during the step below:

Code

+-----------------------------------------------------------------------+
| Legend: |
| 0 : off |
| 1 : on |
| 2 : blinking |
+------------------------------------------+----------------------------+
| Inputs | Outputs |
+-------------------+----------------------+---------+------------------+
| TrafficLightPhase | TrafficLightApproach | Diamond | ExclamationPoint |
+-------------------+----------------------+---------+------------------+
| [0, 6) (red) | 1 | 2 | 0 |
+-------------------+----------------------+---------+------------------+

Alles anzeigen

The diamond begins to blink, but you really have to approach the fire, limit it beyond it so that it detects me, as if the detection distance was 1 meters. I find it a pity. Yet on my cube object linked to fire, I left a distance of 50m of detection.

Would you have any idea how to increase this detection distance?

Thank you for your many helpers, I am sincerely grateful!

Unorthodox Paradox · 14. Februar 2017

You are welcome.

With regard to the minimum required bus detection distance, I cannot provide a comprehensive answer, as I lack any editor experience whatsoever. I searched a bit around the forum and found that said distance is affected by a

Code

[approachdist]
numeric value, e.g., 50

directive, which must be appended below a [traffic_light]'s pertinent (red) [phase]s, within a crossing's .sco.

If you can read, or don't mind translating from, German, try searching the forums using terms such as "Ampel+Anforderung" (traffic light request). A plethora of useful information on the subject is available out there.

AgoraS-114 · 14. Februar 2017

Many thanks to you! It was just enough to change the value 0 to the desired number!

I do not know how to thank you, you helped me a lot! Thanks to you, the realism is pushed to the maximum for my project! I am really grateful !!!

Teilen