I had a question today as I was doing a lot of VR work. This is an issue that occurs when I press the "C" key in uhta3d_editor to save it, and it overwrites the existing file.
I wrote the scene as below.
<scene name="scene_0318" title="0318" onstart="select_box_item(scene_0318)" thumburl="panos/0318.tiles/thumb.jpg" lat="37.80992917" lng="128.70023250" alt="0.00" heading="0.0" group="01">
<control bouncinglimits="calc:image.cube ? true : false" />
<view hlookat="0.0" vlookat="0.0" fovtype="MFOV" fov="120" maxpixelzoom="2.0" fovmin="70" fovmax="140" limitview="auto" />
<preview url="panos/0318.tiles/preview.jpg" />
<image>
<cube url="panos/0318.tiles/pano_%s.jpg" />
</image>
<hotspot name="spot_0318_0317" tooltip="0317" style="skin_hotspotstyle" ath="-89.442" atv="31.890" linkedscene="scene_0317" linkedscene_hoffset="387.966" use3dtransition="true" />
<hotspot name="spot_0318_0319" tooltip="0319" style="skin_hotspotstyle" ath="130.064" atv="27.070" linkedscene="scene_0319" linkedscene_hoffset="-46.802" use3dtransition="true" />
</scene>
<scene name="scene_0319" title="0319" onstart="select_box_item(scene_0319)" thumburl="panos/0319.tiles/thumb.jpg" lat="37.81055083" lng="128.70021528" alt="0.00" heading="0.0" group="02">
<control bouncinglimits="calc:image.cube ? true : false" />
<view hlookat="0.0" vlookat="0.0" fovtype="MFOV" fov="120" maxpixelzoom="2.0" fovmin="70" fovmax="140" limitview="auto" />
<preview url="panos/0319.tiles/preview.jpg" />
<image>
<cube url="panos/0319.tiles/pano_%s.jpg" />
</image>
<hotspot name="spot_0319_0318" tooltip="0318" style="skin_hotspotstyle" ath="-96.739" atv="26.009" linkedscene="scene_0318" linkedscene_hoffset="406.802" use3dtransition="true" />
<hotspot name="spot_0319_0320" tooltip="0320" style="skin_hotspotstyle" ath="72.165" atv="26.872" linkedscene="scene_0320" linkedscene_hoffset="10.939" use3dtransition="true" />
</scene>I try to save as much time as possible when I work on a tour with a large number of VR files using various plug-ins. So I put some different properties in the scene. Like this.
group="01" title2="name"
Title2 is not often used, so there is no big inconvenience even if you enter it manually.
However, the group option used to divide groups in hundreds of scenes disappears when the file is overwritten.
When overwriting a file, can't I keep the property values created by the user? Various variables occur while working, but if the property disappears while overwriting the file, it takes a lot of time to rework hundreds of scenes.