ThreeDimensionalConfigurations/MeetsCOLLADAandOculusRiftS - Revision history

Jet53man: /* Khronos Group's COLLADA2GLTF Converter */

2024-07-02T23:08:45Z

Khronos Group's COLLADA2GLTF Converter

← Older revision		Revision as of 19:08, 2 July 2024
Line 16,206:		Line 16,206:


	<font color="red">CAUTION!</font> While we found this COLLADA2GLTF converter to be a very useful tool, we also discovered that porting a model from one visualization environment to another can be a challenging and frustrating endeavor. It is difficult enough to build a (error-free) COLLADA-formatted model that will properly display a desired animated scene in the Mac's Preview app. But it is naive to expect that that same COLLADA code will survive a translation to glTF and seamlessly construct the identical animated scene within the Oculus Rift S environment. In a pair of accompanying chapters — [[Appendix/Ramblings/~~OculusRift_S~~\|this one]], followed by [[Appendix/Ramblings/RiemannMeetsOculus#Rebuild_Riemann_S-Type_Ellipsoid_Inside_Oculus_Rift_S_Environment\|another one]] — we have chronicled the steps that we have taken to generate our first few (error-free) COLLADA-based models that display properly in both environments. Experience has taught us that … (1) When interpreting COLLADA's <xml>-formatted instructions, the Mac's Preview app is considerably more forgiving than is the Oculus system; (2) almost any code that display's properly in the Mac's Preview app will survive the translation to glTF, in the sense that the COLLADA2GLTF converter seldom complains; but, (3) nevertheless, frequently the Oculus system won't display the model because it detects an error(s), but it almost never suggests what the error(s) might be. When embarking on the development of a new interactive and animated 3D visual scene, the best strategy is a time-consuming one: Start with a COLLADA code that works in both environments — we provide two such codes herein; make only incremental changes and ensure that the model displays properly in the Mac's Preview app; convert the COLLADA-based code to glTF (.glb); don the Oculus Rift S headset & hand controllers, and attempt to import this new model into your "Oculus Home".		<font color="red">CAUTION!</font> While we found this COLLADA2GLTF converter to be a very useful tool, we also discovered that porting a model from one visualization environment to another can be a challenging and frustrating endeavor. It is difficult enough to build a (error-free) COLLADA-formatted model that will properly display a desired animated scene in the Mac's Preview app. But it is naive to expect that that same COLLADA code will survive a translation to glTF and seamlessly construct the identical animated scene within the Oculus Rift S environment. In a pair of accompanying chapters — [[Appendix/Ramblings/OculusRiftS\|this one]], followed by [[Appendix/Ramblings/RiemannMeetsOculus#Rebuild_Riemann_S-Type_Ellipsoid_Inside_Oculus_Rift_S_Environment\|another one]] — we have chronicled the steps that we have taken to generate our first few (error-free) COLLADA-based models that display properly in both environments. Experience has taught us that … (1) When interpreting COLLADA's <xml>-formatted instructions, the Mac's Preview app is considerably more forgiving than is the Oculus system; (2) almost any code that display's properly in the Mac's Preview app will survive the translation to glTF, in the sense that the COLLADA2GLTF converter seldom complains; but, (3) nevertheless, frequently the Oculus system won't display the model because it detects an error(s), but it almost never suggests what the error(s) might be. When embarking on the development of a new interactive and animated 3D visual scene, the best strategy is a time-consuming one: Start with a COLLADA code that works in both environments — we provide two such codes herein; make only incremental changes and ensure that the model displays properly in the Mac's Preview app; convert the COLLADA-based code to glTF (.glb); don the Oculus Rift S headset & hand controllers, and attempt to import this new model into your "Oculus Home".

	===Import to Oculus Rift S Environment===		===Import to Oculus Rift S Environment===

Jet53man at 16:01, 2 October 2021

2021-10-02T16:01:32Z

Jet53man: /* Riemann Meets COLLADA & Oculus Rift S */

2021-10-02T15:55:04Z

Riemann Meets COLLADA & Oculus Rift S

← Older revision		Revision as of 11:55, 2 October 2021
Line 3:		Line 3:

	=Riemann Meets COLLADA & Oculus Rift S=		=Riemann Meets COLLADA & Oculus Rift S=
			{\| class="RiemannMeetsCOLLADA" style="float:left; margin-right: 20px; border-style: solid; border-width: 3px border-color: black"
			\|-
			! style="height: 125px; width: 125px; background-color:white;" \|[[H_BookTiledMenu#Equilibrium_Structures_2\|<b>Riemann<br />meets<br />COLLADA<br />&<br />Oculus Rift S</b>]]
			\|}

	If you want to jump straight to the fun part, copy the ASCII text file that is contained below within the [[#Scroll1\|scrollable box]] named, <b>Inertial17.dae</b>, and read the accompanying instructions regarding how to view this example model on a Mac. A second file — presenting the same example model, but as viewed from a rotating frame of reference — can be extracted from a separate [[#Scroll2\|scrollable box]] named, <b>MultiLagrange18.dae</b>.		If you want to jump straight to the fun part, copy the ASCII text file that is contained below within the [[#Scroll1\|scrollable box]] named, <b>Inertial17.dae</b>, and read the accompanying instructions regarding how to view this example model on a Mac. A second file — presenting the same example model, but as viewed from a rotating frame of reference — can be extracted from a separate [[#Scroll2\|scrollable box]] named, <b>MultiLagrange18.dae</b>.
			<br />
			<br />
			<br />
			<br />

	==Example Model==		==Example Model==

Jet53man: Created page with "FORCETOC =Riemann Meets COLLADA & Oculus Rift S= If you want to jump straight to the fun part, copy the ASCII text file that is..."

2021-07-24T21:12:07Z

Created page with "__FORCETOC__  =Riemann Meets COLLADA & Oculus Rift S= If you want to jump straight to the fun part, copy the ASCII text file that is..."

Show changes

← Older revision		Revision as of 12:01, 2 October 2021
Line 18:		Line 18:
	===Key Physical Parameters===		===Key Physical Parameters===

	The model that we have chosen to use in our first successful construction of a COLLADA-based, 3D and interactive animation has the following properties; this model has been selected from [[~~User:Tohline/~~ThreeDimensionalConfigurations/RiemannStype#Table2\|Table 2 of our accompanying discussion of Riemann S-type ellipsoids]]:		The model that we have chosen to use in our first successful construction of a COLLADA-based, 3D and interactive animation has the following properties; this model has been selected from [[ThreeDimensionalConfigurations/RiemannStype#Table2\|Table 2 of our accompanying discussion of Riemann S-type ellipsoids]]:

	<table border="0" cellpadding="5" align="center">		<table border="0" cellpadding="5" align="center">
Line 88:		Line 88:
	</table>		</table>

	The subscript "EFE" on Ω and λ means that the relevant frequency is given in units that have been adopted in [<b>[[~~User:Tohline/~~Appendix/References#EFE\|<font color="red">EFE</font>]]</b>], that is, in units of <math>~[\pi G\rho]^{1 / 2}</math>. In Figure 1a, the yellow circular marker, that has been placed where the pair of purple dashed lines cross, identifies the location of this model in the "c/a versus b/a" ''[[~~User:Tohline/~~ThreeDimensionalConfigurations/RiemannStype#Fig2\|EFE Diagram]]'' that appears as Figure 2 on p. 902 of [http://adsabs.harvard.edu/abs/1965ApJ...142..890C S. Chandrasekhar (1965)]; essentially the same diagram appears in §49 (p. 147) of [<b>[[~~User:Tohline/~~Appendix/References#EFE\|<font color="red">EFE</font>]]</b>].		The subscript "EFE" on Ω and λ means that the relevant frequency is given in units that have been adopted in [<b>[[Appendix/References#EFE\|<font color="red">EFE</font>]]</b>], that is, in units of <math>~[\pi G\rho]^{1 / 2}</math>. In Figure 1a, the yellow circular marker, that has been placed where the pair of purple dashed lines cross, identifies the location of this model in the "c/a versus b/a" ''[[ThreeDimensionalConfigurations/RiemannStype#Fig2\|EFE Diagram]]'' that appears as Figure 2 on p. 902 of [http://adsabs.harvard.edu/abs/1965ApJ...142..890C S. Chandrasekhar (1965)]; essentially the same diagram appears in §49 (p. 147) of [<b>[[Appendix/References#EFE\|<font color="red">EFE</font>]]</b>].

	In a [[~~User:Tohline/~~ThreeDimensionalConfigurations/JacobiEllipsoids#Jacobi_Ellipsoids\|separate chapter]] we have discussed various properties of uniformly rotating, ''Jacobi'' ellipsoids; they are equilibrium configurations that lie along the sequence that runs from "M<sub>2</sub>" (on the b/a = 1, Maclaurin sequence) to the origin of this diagram. Our chosen model lies off of — just above — the Jacobi-ellipsoid sequence, which means that it is not rotating as a solid body. Instead, as we focus first on the ''direct'' (as opposed to the ''adjoint'') configuration, we appreciate that while the ellipsoid is spinning prograde (counter-clockwise) with a frequency given by \|Ω<sub>EFE</sub>\|, each Lagrangian fluid element inside as well as on the surface of the ellipsoid is traveling retrograde (clockwise) along an elliptical path with a frequency given by \|λ<sub>EFE</sub>\|.		In a [[ThreeDimensionalConfigurations/JacobiEllipsoids#Jacobi_Ellipsoids\|separate chapter]] we have discussed various properties of uniformly rotating, ''Jacobi'' ellipsoids; they are equilibrium configurations that lie along the sequence that runs from "M<sub>2</sub>" (on the b/a = 1, Maclaurin sequence) to the origin of this diagram. Our chosen model lies off of — just above — the Jacobi-ellipsoid sequence, which means that it is not rotating as a solid body. Instead, as we focus first on the ''direct'' (as opposed to the ''adjoint'') configuration, we appreciate that while the ellipsoid is spinning prograde (counter-clockwise) with a frequency given by \|Ω<sub>EFE</sub>\|, each Lagrangian fluid element inside as well as on the surface of the ellipsoid is traveling retrograde (clockwise) along an elliptical path with a frequency given by \|λ<sub>EFE</sub>\|.

	===The COLLADA Code & Initial 3D Scene===		===The COLLADA Code & Initial 3D Scene===
Line 16,206:		Line 16,206:


	<font color="red">CAUTION!</font> While we found this COLLADA2GLTF converter to be a very useful tool, we also discovered that porting a model from one visualization environment to another can be a challenging and frustrating endeavor. It is difficult enough to build a (error-free) COLLADA-formatted model that will properly display a desired animated scene in the Mac's Preview app. But it is naive to expect that that same COLLADA code will survive a translation to glTF and seamlessly construct the identical animated scene within the Oculus Rift S environment. In a pair of accompanying chapters — [[~~User:Tohline/~~Appendix/Ramblings/OculusRift_S\|this one]], followed by [[~~User:Tohline/~~Appendix/Ramblings/RiemannMeetsOculus#Rebuild_Riemann_S-Type_Ellipsoid_Inside_Oculus_Rift_S_Environment\|another one]] — we have chronicled the steps that we have taken to generate our first few (error-free) COLLADA-based models that display properly in both environments. Experience has taught us that … (1) When interpreting COLLADA's <xml>-formatted instructions, the Mac's Preview app is considerably more forgiving than is the Oculus system; (2) almost any code that display's properly in the Mac's Preview app will survive the translation to glTF, in the sense that the COLLADA2GLTF converter seldom complains; but, (3) nevertheless, frequently the Oculus system won't display the model because it detects an error(s), but it almost never suggests what the error(s) might be. When embarking on the development of a new interactive and animated 3D visual scene, the best strategy is a time-consuming one: Start with a COLLADA code that works in both environments — we provide two such codes herein; make only incremental changes and ensure that the model displays properly in the Mac's Preview app; convert the COLLADA-based code to glTF (.glb); don the Oculus Rift S headset & hand controllers, and attempt to import this new model into your "Oculus Home".		<font color="red">CAUTION!</font> While we found this COLLADA2GLTF converter to be a very useful tool, we also discovered that porting a model from one visualization environment to another can be a challenging and frustrating endeavor. It is difficult enough to build a (error-free) COLLADA-formatted model that will properly display a desired animated scene in the Mac's Preview app. But it is naive to expect that that same COLLADA code will survive a translation to glTF and seamlessly construct the identical animated scene within the Oculus Rift S environment. In a pair of accompanying chapters — [[Appendix/Ramblings/OculusRift_S\|this one]], followed by [[Appendix/Ramblings/RiemannMeetsOculus#Rebuild_Riemann_S-Type_Ellipsoid_Inside_Oculus_Rift_S_Environment\|another one]] — we have chronicled the steps that we have taken to generate our first few (error-free) COLLADA-based models that display properly in both environments. Experience has taught us that … (1) When interpreting COLLADA's <xml>-formatted instructions, the Mac's Preview app is considerably more forgiving than is the Oculus system; (2) almost any code that display's properly in the Mac's Preview app will survive the translation to glTF, in the sense that the COLLADA2GLTF converter seldom complains; but, (3) nevertheless, frequently the Oculus system won't display the model because it detects an error(s), but it almost never suggests what the error(s) might be. When embarking on the development of a new interactive and animated 3D visual scene, the best strategy is a time-consuming one: Start with a COLLADA code that works in both environments — we provide two such codes herein; make only incremental changes and ensure that the model displays properly in the Mac's Preview app; convert the COLLADA-based code to glTF (.glb); don the Oculus Rift S headset & hand controllers, and attempt to import this new model into your "Oculus Home".

	===Import to Oculus Rift S Environment===		===Import to Oculus Rift S Environment===
Line 16,323:		Line 16,323:
	==Footnotes==		==Footnotes==

	<sup>&Dagger;</sup>Adopting the characteristic mass <math>~(M_\mathrm{Ch} = \mu_e^{-2} \cdot 1.14205 \times 10^{34} ~\mathrm{g})</math> and characteristic length <math>~(\ell_1 = \mu_e^{-1} \cdot 7.71395 \times 10^{8} ~\mathrm{cm})</math> that are associated with a [[~~User:Tohline/~~SSC/Structure/WhiteDwarfs#White_Dwarfs\|white dwarf]] equation of state, we can reasonably state that the characteristic mean density of a spherically symmetric white dwarf is,		<sup>&Dagger;</sup>Adopting the characteristic mass <math>~(M_\mathrm{Ch} = \mu_e^{-2} \cdot 1.14205 \times 10^{34} ~\mathrm{g})</math> and characteristic length <math>~(\ell_1 = \mu_e^{-1} \cdot 7.71395 \times 10^{8} ~\mathrm{cm})</math> that are associated with a [[SSC/Structure/WhiteDwarfs#White_Dwarfs\|white dwarf]] equation of state, we can reasonably state that the characteristic mean density of a spherically symmetric white dwarf is,
	<table border="0" cellpadding="5" align="center">		<table border="0" cellpadding="5" align="center">

Line 16,363:		Line 16,363:
	=See Also=		=See Also=

	* Discussion of [[~~User:Tohline/~~ThreeDimensionalConfigurations/RiemannStype\|Ou's Riemann-Like Ellipsoids]]		* Discussion of [[ThreeDimensionalConfigurations/RiemannStype\|Ou's Riemann-Like Ellipsoids]]

	* [[~~User:Tohline/~~ThreeDimensionalConfigurations/MeetsCOLLADAandOculusRiftS\|Riemann Meets COLLADA & Oculus Rift S]]: Example <b>(b/a, c/a) = (0.41, 0.385)</b>		* [[ThreeDimensionalConfigurations/MeetsCOLLADAandOculusRiftS\|Riemann Meets COLLADA & Oculus Rift S]]: Example <b>(b/a, c/a) = (0.41, 0.385)</b>
	** [[~~User:Tohline/~~Appendix/Ramblings/VirtualReality#Virtual_Reality_and_3D_Printing\|Virtual Reality and 3D Printing]]		** [[Appendix/Ramblings/VirtualReality#Virtual_Reality_and_3D_Printing\|Virtual Reality and 3D Printing]]
	** [[~~User:Tohline/~~Appendix/Ramblings/~~OculusRift_S~~\|Success Importing Animated Scene into Oculus Rift S]]		** [[Appendix/Ramblings/OculusRiftS\|Success Importing Animated Scene into Oculus Rift S]]
	** [[~~User:Tohline/~~Appendix/Ramblings/RiemannMeetsOculus\|Carefully (Re)Build Riemann Type S Ellipsoids Inside Oculus Rift Environment]]		** [[Appendix/Ramblings/RiemannMeetsOculus\|Carefully (Re)Build Riemann Type S Ellipsoids Inside Oculus Rift Environment]]
	** Other Example S-type Riemann Ellipsoids:		** Other Example S-type Riemann Ellipsoids:
	*** <b>[[~~User:Tohline/~~Appendix/Ramblings/RiemannB90C333\|(b/a, c/a) = (0.90, 0.333)]]</b>		*** <b>[[Appendix/Ramblings/RiemannB90C333\|(b/a, c/a) = (0.90, 0.333)]]</b>
	*** <b>[[~~User:Tohline/~~Appendix/Ramblings/RiemannB74C692\|(b/a, c/a) = (0.74, 0.692)]]</b>		*** <b>[[Appendix/Ramblings/RiemannB74C692\|(b/a, c/a) = (0.74, 0.692)]]</b>
	*** <b>[[~~User:Tohline/~~Appendix/Ramblings/RiemannB28C256\|(b/a, c/a) = (0.28, 0.256)]]</b>		*** <b>[[Appendix/Ramblings/RiemannB28C256\|(b/a, c/a) = (0.28, 0.256)]]</b>

	{{ SGFfooter }}		{{ SGFfooter }}

ThreeDimensionalConfigurations/MeetsCOLLADAandOculusRiftS - Revision history

Jet53man: /* Khronos Group's COLLADA2GLTF Converter */

Jet53man at 16:01, 2 October 2021

Jet53man: /* Riemann Meets COLLADA & Oculus Rift S */

Jet53man: Created page with "__FORCETOC__ =Riemann Meets COLLADA & Oculus Rift S= If you want to jump straight to the fun part, copy the ASCII text file that is..."

Jet53man: Created page with "FORCETOC =Riemann Meets COLLADA & Oculus Rift S= If you want to jump straight to the fun part, copy the ASCII text file that is..."