Also last question
Is it possible to have multiple DollHouses for example for two bedrooom type appartements and another for Three bedrooms appartements. which bluprint will let me connect a POI to one type and another appartement to the other type ?
Thanks
Taha
Hello Dennis,
Thank you for the clarification. That helps a lot.
I have another suggestion that I think would be very useful for real estate and architectural presentations.
Would it be possible to add a floor-click navigation mode in a future update?
For example, instead of only navigating by POI buttons or menu items, the user could click directly on the floor in the scene, and the camera / pawn would smoothly move to that selected position or to a predefined nearby viewpoint.
This would be very helpful for real estate presentations because many clients naturally want to explore the space by clicking on the floor, similar to a virtual tour or walk-through experience.
Ideally, the feature could support:
Clicking on the floor to move the camera / pawn smoothly
Optional predefined floor hotspots
Smooth camera transition or walk-to movement
The ability to enable / disable this mode
Compatibility with POI navigation, so clicking a floor area could also trigger a related POI or Info Panel
I think this would make AVE II feel much more interactive, especially for touch screens, sales galleries, iPads, and real estate presentation rooms.
In addition, I would also like to suggest better Chinese localization support.
Since we mainly use AVE II for real estate presentations in Taiwan and other Chinese-speaking markets, it would be extremely helpful if the UI system could support Traditional Chinese more easily.
Some useful improvements could include:
A centralized language / localization table for all UI text
Easier replacement of menu labels, POI labels, button text, tooltips, and Info Panel text
Better support for Traditional Chinese fonts and CJK font fallback
Avoiding hardcoded English text inside widgets or Blueprints
Support for longer Chinese text without UI layout breaking
A simple example showing how to create an English / Traditional Chinese language switch
Clear guidance on which widgets or data tables should be edited for localization
For real estate presentations, localization is very important because the sales team and clients usually need fully localized UI, including POI names, project information, room descriptions, gallery labels, navigation buttons, and instruction text.
Is something like this already supported in AVE II, or would you recommend that we manually build a localization layer on top of the current widget system?
If you have any guidance, example Blueprint setup, or recommended workflow for adding Traditional Chinese localization, I would really appreciate it.
Best regards,
Lester
Hello Taha,
The current template only features a single, hardcoded Dollhouse level, which is honestly not very useful. 
Thank you for pointing it out! 
To make this dynamic and allow a different level for each unit, you will need to do the following changes:
Open BP_POI_Unit. Add a new variable of the type Name and name it Level_Dollhouse.
Inside BPI_CoreAPI, locate the RequestDollhouseMode function. Under the Inputs section, add a new variable of the type Name in the same way we did before.
Open WBP_Info_Content_Unit and locate the On Clicked event for Button_Dollhouse. You will notice that a new input pin has appeared on the RequestDollhouseMode Blueprint Interface call. Pass the level name into this new input.
Finally, open the Game Instance BP_AVE_GI. Locate the Load Stream Level node for the Dollhouse and connect your new level name variable to the Level Name input pin. Also, save the level name in a variable in order to unload it once you leave the Dollhouse Mode.
I hope this helps. The next update for AVE II will include this setup by default.
Greetings,
For the past month, we have been unable to work on the project due to health issues. Once fully recovered, we will finally give the documentation page the care it deserves. Until then, we will continue to answer questions and emails. (However, we will not be able to provide screenshots)
@ISUther & @sony12324311
I read your posts a couple of times and want to thank you for the time you invested in them. They are very detailed. All of this will be on our roadmap in June.
Unfortunately, we never tried localization for Chinese. However, we saw multiple projects using the legacy ArchViz Explorer with Chinese characters and we love the idea. The template currently allows switching between English, French, and German.
Best regards,
Dennis
Hope you are feeling better and look forward to where this goes.
