Well, consider it broken already! By the VAB interior structure! As I wrote eariler, not much to do about that. Unless Donamy has some ideas?
see above: Reduce details and use more textures. There is not much more that I see, apart of leaving it away completely. I could reduce the number of polygons rendered in the DLL by some ways like for example having the different bays of the VAB separated and rendered at lower resolution depending on visual distance, but the loading time wouldn't be much affected.
Other than the FPS problems, how is things progressing otherwise?
VAB can be tested stand-alone, have only a bug that the external mesh is sometimes not rendered. Possibly related to the large polycount, I have not yet found the cause in the code.
MDM testing goes forward, will include a simplified serial I/O interface for the subsystems since the SIO connections are purely point to point and not bus structures like the Shuttle Bus. No need to have more powerful connections for these and the whole complex communication involved.
Connections to the I/O modules shall be handled by the MDM acting as facade, this way we don't need to publish the IO module class outside the MDM.
The MDM assembler programming language is still in flux, Decided to change the syntax more towards the IBM High-Level Assembler language (Also used for the AP-101) for having a simpler way to declare labels inside the PROM source code. Is pretty necessary for getting symbol tables into C++ header files or simple tab delimited text files and not having to use fixed addresses for the PROM calls or module address.
When the MDMs are done, I can continue working on the GNC subsystems. Also I can do some work on the various pressure/temperature/voltage/etc sensors in the Shuttle.