Support overload. We are currently seeing 65% more demand for support then we normally see. We can only assume this is because more people are at home due to the corona crises. Our complete support staff is online and they are working flat out, but it will take some days before we can scale up resources. Please be patient.

Jump to content
Welmux

Issue with the Regiobus i200

Recommended Posts

Hi,

 

I have a strange issue with the Regiobus i200 addon. After some time when i insert the bus in Omsi,  the grass textures start to blink. The blinking texture is actually

one of the buses own main textures. It looks like some kind of a memory leak. I noticed that taking the light frame out out of the main frame (scripting)

does fix the issue, but on the other hand the issue is not in that script. I took the light script from the Citybus i280 and got the same issue. The Citybus works fine.

So my conclusion is that it has to be the "co-operation" of the scripts of the Regiobus, which causes the issue.

And no, it donesn't happen with any other bus, not with the Citybyus i280 or something else like the SD200.

Has someone else had this same issue? Unfortunately these "disco lights" make this really good addon unplayable. :(

-Welmux

Share this post


Link to post
Share on other sites

Geforce GTX 1080 Ti, 11Gb

Core i7 8700k
32 Gb DDR4
 

Share this post


Link to post
Share on other sites

Thanks, ManuelNorge.

Did yout test with the Regiobus? I haven't got these issues with any other bus, not even with the Citybus.

 

I have the 4GB patch installed. Normally that causes issues only with really big maps and then the symptoms are usually white textures.

I did test with your settings. I got the issue again.

 

I also made some more tests:
-i ran memory tests for both GPU and main memory, although i didn't very much think that this would be caused by faulty memory, the symptoms are usually different - > all tests passed

-i tested running Task Manager at the same time with Omsi and killed programs running at the background and some processes as well to make sure that no background processes cause the issue -> nothing found this far

 

-Welmux

 

Share this post


Link to post
Share on other sites

Ok, i continue with this a little bit.
First of all, i found a small bug (one variable didn't get value 0 when it should have) in the ligts script of this bus and fixed it but it didn't fix the issue.


I had a short discussion with Nikita Lipunov, the main programmer of Bustrainz in VK:
"Nikita Lipunov:
this is due to the use of lightmaps in interior lighting. it consumes a lot of memory, it overloads, which leads to such a result"


I tested to convert the light map textures to smaller format, 15 files from 14,3 Mb to 466 kb. That didn't fix the issue.

 

And sorry, i wasn't able to tell before, what exactly causes this issue to happen. Now i know it. It is the cabin lights.
If you turn on only 2 of the 3 cabin lights, everything works fine, but if you turn them all on, you get this issue in 30 seconds normally.

 

Unfortunately i wasn't able to fix this issue, but a good workaround is only to use 2 of the 3 cabin lights.
Despite of that i really hope that Bustrainz would be able to fix this. This bus is pay-ware.

 

-Welmux

 

 

Share this post


Link to post
Share on other sites

Thanks for updating on this!

Now I know why I couldn't reproduce it at first.

 

If the devs know about it I'm sure they will try to provide a solution as soon as possible.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...