Hi!
First of all: Do you know the script testing function?
Hey!
Yes i do know of it, however like you said it does lack driving physics & sounds. (It will be a really welcome addition if you end up adding them!)
I do hope you will add the possibility to preview dynamic interior lights in the CT as well.
If all of these features end up added into the Content-Tool, then i can do pretty much everything in it and do less of this "going back and forth" with the programs. 
Hello!
What i have learned during this time of trying to develop vehicle(s) for LOTUS, is how time-consuming it is. This shows especially when getting into fine-tuning later on. (Lights, small changes in scripts etc. etc.)
I have tried asking if it would be possible to run both Content-Tool and the Simulator at the same time, saving time from the constant opening & closing of the programs when checking out minuscule changes. The answer i got to that, however, was a resounding "No".
I do understand the possible obstacles of running them both at the same time, so i thought of an alternative way to speed up development.
Please let us start up a quick instance of LOTUS with fewer features, directly from Content-Tool. It would do what the Save & Pack option does already, but also close the Content-Tool and open up a LOTUS instance without further user input.
It could only be the Diorama-map, and you could only select spawn point & time/date. Also script debug-values could be shown by default. Exiting the quick instance would take you back to the project you opened the instance from.
This would save a lot of time & clicking around. I counted it takes ~1min to go from Content-Tool into the Simulator itself with vehicle loaded up, and around 20-25 seconds to go back into Content-Tool and continue where you left off.
I made a little mock-up how it could look like in the menus. It could also be an additional button in the bottom-right corner.
Could this be doable in the future? Tell me what you think
Maybe you could upload the bus for OMSI 2 first so we can see if there are any bugs and then import it to LOTUS?
Like gt670dn said, what for? I've spent last 4-5 years developing the bus in OMSI, and it works quite fine in it apart from some missing features. But, due to personal reasons and some inherent limitations of what OMSI can do & handle, the project is now coming to LOTUS.
There are some 'bugs', such as the flickering shadows, but that's a LOTUS-specific thing.
To clarify: You will have the ability to choose between the presets or your own settings, depending on your personal intention.
That sounds good. Only thing which i want to know is, can i have fleetnumber/registration plate-specific repaints if i have predefined a list? OMSI did not have this, you could select any repaint regardless of number.
Hello!
After a long time trying to work around the vehicle selection/spawn menu in OMSI, i'd like to make a suggestion while Lotus is still in development.
Please allow us to have plate number/fleet number-specific repaints/configurations. The selection workflow should be as follows:
1. Select vehicle itself (For example some certain model of Citaro)
2. Select either fleet number or number plate from dropdown lists, both selections should 'follow' eachother (e.g I select a certain fleet number, the number plate changes as well).
I believe LOTUS supports Fleet number and Registration plate lists like OMSI does? (.org files)
3. After selecting a fleet number/number plate, only then allow to select a repaint. The repaint-dropdown could even be grayed out if there is only a single repaint available.
And lastly, ability to restrict certain (multiple!) repaints & 'setvars' to only specific number plates/fleet numbers.
Of course this system i'm suggesting would only work if there are defined lists of fleet numbers & registration plates. If not, it would work like it currently does. (enter any number you want, select any repaint you want)
The reason i'm asking for this feature, is because it isn't uncommon at all for buses (applies to other vehicle types as well) to be sold/brought to different operators over their lifetime. With the menu working the way i've suggested, i could recreate history of vehicles and for example, how a batch of buses has split to different operators over time.
Feel free to correct me if i don't know something or there are features like this already planned.
Hello.
Where is it possible for me to contact you ViMaX ?
With a direct message, right on this forum. 
1. Please describe as detailed as possible what you did and which problem that leads to.
Loaded up my bus with shadows enabled in game settings. Now i have flickering shadows at random spots.
Examples:
Hello!
I did read the wiki about lighting and i noticed you say this:
QuoteNote: The lighting of the car body can not be tested in the ContentTool! That must be done in LOTUS itself
Is this really the final version, or is the light editing going to be updated at some point? Currently this will just cause unnecessary, time-consuming steps in vehicle creation.
Is this not the reason the entire 3D preview in Content-tool was created? To adjust things ready before exporting to the game?
P.S
Please let us somehow "confirm changes" without the need to always close & reopen the properties menu in Content-tool.
P.S
Fluorescent tube-type light source does not seem to work? If i change it to point-light without touching any other settings, the light works.
A little progress update, slowly importing more parts. 
Hi!
Thanks, by your encouragement i tested out importing parts of this thing into LOTUS. Apart from a few errors/oddities in the Content Tool, i got it working.
The only bad things i see right now are the non-existent anti-aliasing for some reason, and a strange 'shadow Z-fighting' graphical error in some spots of the mesh. (I checked the meshes thoroughly and there should not be any duplicate faces, otherwise it would have affected Shadow/AO baking in Blender already.)
I'll post the rest of errors i've encountered in Bug list forum, or should i post them in here?
Hello!
After years of development of this project on OMSI and feeling that OMSI is approaching it's end-of-life, i've decided to transfer it onto LOTUS when it's possible.
At the moment i do not have much to show LOTUS-wise, as the Streets module is not yet available. (I hope it will be soon)
What i'm hoping to achieve in future is several variations of the 8700, as well as a map of BRT bus line in Helsinki, to accompany the buses.
Below are some current pictures & video from OMSI:
