Hello, I need expert advice on how I should structure my code.
I am creating a very big interactive property inspector, which has a range of floor plans ranging from 3 to 6 separate floor plans for each property. The goal is to make a seamless transition from one floor plan to another without compromising performance for each property.
Each floor plan is different, so they have different sets of:
-different types of customizations (swappable models)
-different custom-made scene optimization’s
All floor plans will share same;
-swappable models (furnishing items/room decor)
-Use a single Babylon.js engine
-Floor plans will import without textures or materials pre-assigned (meaning just as plane mesh)
-Create reusable function that can handle all the floorplans
-Functions will handle:
-Applying Material (babylon material or blender exported material if possible)
-Setting up animations based on each floor plan
-Setting up mesh optimizations based on each floor plan
GUI/Buttons will stay the same, only changing names to accommodate for each floorplans
-Create separate babylon.js engine for each floorplan
-Engines don’t run simultaneously
I have already set up most of Option 1, outside of material and texture assignment, which i haven’t touched yet. Please, no chatGPT response. I want people who have done lots of experiments with using a single engine and separate engines configurations and have a good understanding of the pros and cons. I am not sure if the engine is faster with a single engine setup or separate engine calls (separate codebase).