falcon409
September 11th, 2016, 03:03
Let me begin this by saying. . .if you have a problem with any scenery of mine, don't post questions about it in the "Discussion Thread" in the downloads area. I supply my e-mail address in every readme for every scenery I produce. Also, a PM or a new thread in the FSX forum would get quicker results. I never read the discussion threads because I rarely if ever have anything posted there. This apparently was a rare instance where folks were discussing a problem and I had no knowledge of it.
Ok, on to the problem.
Due to a missing window on the FBO, which was correctly noted by a member, I fixed it the only way I know how. . . .start up ModelConverterX open the 3D file and go through the process of compiling the bgl, making sure that the problem window has it's correct night texture attached. Because the FBO was recompiled, MCX makes a new GUID number to attach to that scenery object. When that object file and the corresponding texture files are added back into their respective folder and the scenery is loaded into the Sim, Instant Scenery, in all its wisdom, no longer sees the FBO because that GUID number doesn't match the one in its placement bgl (KIWI_Objects.bgl). Wonderful!
So I have to load up the scenery, load Instant Scenery 3, load the KIWI Objects file, select the new FBO with the correct window fix and place it back in it's correct position on the tarmac and then close IS3 which then saves the new FBO information. . . . .and now the FBO is there with all it's windows. Still think you might want to be a scenery designer? lol
Finally, after about 100+ downloads of that scenery, all of them missing a window, I'll have to hit Rami up again to trash the last two uploads I sent him and replace those with a "Newer" upload. Sometimes some of us would just rather stay in bed, lol. I apologize for this screwup and the ensuing mess. . .it points up the reason I don't normally release any of my scenery. . .things happen in the process of building sceneries like this and when I'm the only one using it I rarely bother fixing them. Once it's released, people expect, and rightly so, that everything is as it should be and correcting something after it gets released is not an easy task because now there are a hundred folks with a problem instead of just one.
I'll get this corrected ASAP.
Ok, on to the problem.
Due to a missing window on the FBO, which was correctly noted by a member, I fixed it the only way I know how. . . .start up ModelConverterX open the 3D file and go through the process of compiling the bgl, making sure that the problem window has it's correct night texture attached. Because the FBO was recompiled, MCX makes a new GUID number to attach to that scenery object. When that object file and the corresponding texture files are added back into their respective folder and the scenery is loaded into the Sim, Instant Scenery, in all its wisdom, no longer sees the FBO because that GUID number doesn't match the one in its placement bgl (KIWI_Objects.bgl). Wonderful!
So I have to load up the scenery, load Instant Scenery 3, load the KIWI Objects file, select the new FBO with the correct window fix and place it back in it's correct position on the tarmac and then close IS3 which then saves the new FBO information. . . . .and now the FBO is there with all it's windows. Still think you might want to be a scenery designer? lol
Finally, after about 100+ downloads of that scenery, all of them missing a window, I'll have to hit Rami up again to trash the last two uploads I sent him and replace those with a "Newer" upload. Sometimes some of us would just rather stay in bed, lol. I apologize for this screwup and the ensuing mess. . .it points up the reason I don't normally release any of my scenery. . .things happen in the process of building sceneries like this and when I'm the only one using it I rarely bother fixing them. Once it's released, people expect, and rightly so, that everything is as it should be and correcting something after it gets released is not an easy task because now there are a hundred folks with a problem instead of just one.
I'll get this corrected ASAP.