Welmux

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

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

Geforce GTX 1080 Ti, 11Gb Core i7 8700k 32 Gb DDR4

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 Regiobus_i200_issue.mp4

Thanks for this scenery, it really looks awsome. I'm definetely going to buy it. Btw, i somehow remember that i would have once given you a suggestion to build a scenery of Niagara Falls... I have now a new little suggestion for the future. This scenery and ManhattanX are real helicopter sceneries because of very detailed scenery and because helicopter sightseeings are done in real life in both locations. It's just really hard to find suitable paints for FSX choppers. It would be a really good addition to this kind of scenery to get a local paintscheme for some chopper to be used in the scenery. I would even pay a couple of euros more to get that paint with the scenery. In this case the paint could be for instance Rainbow Copters and for NY Helicopter Flight Service. Even it would be ok to me if the paints would be for the default FSX Bell 206 instead of Bell 407 (i think there is no Bell 407 for FSX). Regards Ville

Now when Flight1 is finishing their BN Islander, it grows my interest to fly again in nothern Germany. I have already Helgoland X and Island Hopping. But how well does VFR Germany 2 work with them - especially Island Hopping? I remember that at least at the beginning there were some problems. Do newer versions of the sceneries fix those issues, have any patches been released? Welmux