In case of any change in VT, what method should we implement to perform the updating of the menu titles related to the models, regardless of the store, when the application is opened by the user? Would JSON files be OK?ģ. Is it more convenient to download the relevant zip file and use the files in it when I click on the menu?Ģ. Is it right or wrong to call the model and model add-on (video, audio, pdf) files to the application using the method we use? Is there a more accurate and convenient method? Can the Addressable Asset method be used, or using an asset like TRILIB to store the model and plugin files (in plain form such as fbx, mp3, mp4, pdf) together with a JSON file containing all the parameters related to the model as a zip in the VT and use it in runtime. The issues that we have problems and want to get information about are as follows:ġ. And we included them in runtime from remote vt to application.
We created the model, video and sound separately as AssetBundle. For this, we tried the AssetBundel structure and we succeeded. But what we want is to keep these models and all the files and data related to these models, as well as the menu titles, in a remote DB and add these models to the scene at runtime. We do various interactions with this model: disassemble, make parts transparent, video, audio playback.įirst, we built these models as prefabs embedded in the application. When you click on these subheadings, the relevant 3D model comes to the scene. In our application, there is a menu and subheadings under the main headings of this menu.
0 kommentar(er)
