User Tools

Site Tools


v2tov3

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
v2tov3 [2018/01/24 13:03]
jgravett Updates table and fixes errors in description
v2tov3 [2018/04/01 14:41] (current)
Line 5: Line 5:
 To convert an OpenVSP v2 model to a v3 model, begin by selecting File->​Import...->​OpenVSP v2 (.vsp) and selecting the desired v2 file. After clicking "​Accept"​ the v2 file will be loaded in OpenVSP and automatically converted into a v3 file (*.vsp3) once the model is saved.  ​ To convert an OpenVSP v2 model to a v3 model, begin by selecting File->​Import...->​OpenVSP v2 (.vsp) and selecting the desired v2 file. After clicking "​Accept"​ the v2 file will be loaded in OpenVSP and automatically converted into a v3 file (*.vsp3) once the model is saved.  ​
  
-The current status of features in OpenVSP v2 files supported in OpenVSP v3 is listed in the table below. The two columns filled with yes/no indicators report whether each v2 feature has a counterpart in v3 and whether conversion can ever be possible given the information stored in the data files. In most cases, a yes in the first column leads to a yes in the second column. Notable exceptions are v2’s user parameters ​and parameter links. Similarly, in most cases, a no in the first column usually means a no in the second column. ​Some exceptions are v2’s Hybrid Wing Body and Propeller componentand the Bezier curve cross-section type. These correspond to features planned for v3 that have not yet been implemented. While it is impossible to implement a conversion capability at this time, it will make sense to expand the converter as these features are implemented. Finally, some features such as Textures and Labels were deemed to be of insufficient priority, such that a conversion capability for those features is not planned. The final column reports the status of each part of the converter, and most of the features are marked in green as complete. ​The Prop component is marked in red because it has not yet been completed. Three features are marked in orange as they are waiting on the corresponding feature to be implemented in v3 before a converter can be developed. Finally, all tasks marked in grey cannot or will not be supported by the converter. ​+The current status of features in OpenVSP v2 files supported in OpenVSP v3 is listed in the table below. The two columns filled with yes/no indicators report whether each v2 feature has a counterpart in v3 and whether conversion can ever be possible given the information stored in the data files. In most cases, a yes in the first column leads to a yes in the second column. Notable exceptions are v2’s user parametersparameter links, and WingStructure components. Similarly, in most cases, a no in the first column usually means a no in the second column. ​One exception is v2’s Hybrid Wing Body, which has essentially ​been replaced by blendable wings. Finally, some features such as Textures and Labels were deemed to be of insufficient priority, such that a conversion capability for those features is not planned. The final column reports the status of each part of the converter, and most of the features are marked in green as complete. ​All tasks marked in grey cannot or will not be supported by the converter. ​
  
 {{ :​v2tov3table.png?​nolink%650 |}} {{ :​v2tov3table.png?​nolink%650 |}}
v2tov3.txt · Last modified: 2018/04/01 14:41 (external edit)