Welmux 4 Posted January 1, 2020 Share Posted January 1, 2020 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 Please login to view this video. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted January 2, 2020 Aerosoft Share Posted January 2, 2020 Can you tell us about your hardware configuration? Link to comment Share on other sites More sharing options...
Welmux 4 Posted January 2, 2020 Author Share Posted January 2, 2020 Geforce GTX 1080 Ti, 11Gb Core i7 8700k 32 Gb DDR4 Link to comment Share on other sites More sharing options...
Manuel Bragard 0 Posted January 3, 2020 Share Posted January 3, 2020 I just tried for 30min or so but could not reproduce this. Do you have the 4GB Patch installed already? And could you once try these settings? https://www.dropbox.com/s/z1erfyuu9oxkrys/custom1.oop Link to comment Share on other sites More sharing options...
Welmux 4 Posted January 3, 2020 Author Share Posted January 3, 2020 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 Link to comment Share on other sites More sharing options...
Welmux 4 Posted January 5, 2020 Author Share Posted January 5, 2020 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 Link to comment Share on other sites More sharing options...
Manuel Bragard 0 Posted January 6, 2020 Share Posted January 6, 2020 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. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.