AlienArt - Revision history

Fire-hound: rephrased and tried to explain better the scope and intent of this article

2023-12-11T09:15:57Z

rephrased and tried to explain better the scope and intent of this article

Fire-hound: Added stub

2023-03-08T12:12:39Z

Added stub

Fire-hound: /* Importing into engine on Linux */

2023-03-05T14:49:50Z

‎Importing into engine on Linux

Fire-hound: /* Point the ColladaCGF to the .dae file */

2023-03-05T14:43:55Z

‎Point the ColladaCGF to the .dae file

Fire-hound: /* Prepare your Linux */

2023-03-05T14:42:29Z

‎Prepare your Linux

Fire-hound: /* Export settings */ clarifications and typos

2023-03-05T14:26:06Z

‎Export settings: clarifications and typos

Fire-hound: /* Get it ready */ emphasis and clarification

2023-03-05T14:22:59Z

‎Get it ready: emphasis and clarification

Fire-hound: /* now with blender 3.x */

2023-03-05T14:18:15Z

‎now with blender 3.x

Fire-hound: /* Get it ready */

2023-03-05T14:17:24Z

‎Get it ready

Fire-hound: /* Run the editor */

2023-02-14T21:42:19Z

‎Run the editor

@@ Line 1: / Line 1: @@
 {{ Stub }}
-By Alien it's meant as totally new, possibly even strange art in respect of what's present in the Asset Pool.<br>
+"Art" can be a rock, a building or even a working factory.<br>
-In effect successfully following this procedure will hopefully lead to gradual expansion and enrichment of the aforementioned Asset pool.<br>
+This article documents each step of art import from recent 3.x blender into Cryengine 2. This will cover non animated objects and game assets only.<br>

← Older revision		Revision as of 12:12, 8 March 2023
Line 1:		Line 1:
		+	{{ Stub }}
	By Alien it's meant as totally new, possibly even strange art in respect of what's present in the Asset Pool.<br>		By Alien it's meant as totally new, possibly even strange art in respect of what's present in the Asset Pool.<br>
	In effect successfully following this procedure will hopefully lead to gradual expansion and enrichment of the aforementioned Asset pool.<br>		In effect successfully following this procedure will hopefully lead to gradual expansion and enrichment of the aforementioned Asset pool.<br>

@@ Line 125: / Line 125: @@
 You want to build a not only custom version of wine (as if that wasn't intimidating enough!).
-No sir, you want a higly customized, overly patched VERY recent version wine-staging that has support for child-window our Sandbox2 editor uses to render the game withing it's app window.
+No sir, you want a highly customized, overly patched VERY recent version wine-staging that has support for child-window our '''Sandbox2''' editor uses to render the game within it's app window.
 No configuration files need to be modified in the [wine-tkg-git] directory, You merely cd to it and run [./non-makepkg-build.sh]
@@ Line 162: / Line 162: @@
-And once saved, rerun the above command. Install the new wine and make MWLL run in it's prefix.
+And once saved, re-run the above command. Install the new '''wine''' and make MWLL run in it's prefix.
-to run the editor you will need few more winetricks...
+to run the editor you will need few more '''winetricks'''...<br>
-Fended off yet? no? Good, because that isn't nearly the end of the desert :D.
+Fended off yet? no? Good, because that isn't nearly the end of the desert :D.<br>
-add (via winetricks) the following:
+add (via winetricks) the following:<br>
 #d3dcompiler_43
 #d3dcompiler_47
@@ Line 173: / Line 173: @@
 #vcrun2005 (MWLL needs it won't run w/o)
 #(add the two redists from the MWLL package, 32bit ones)
-Now on the editor should launch:
+Now on the editor should launch:<br>
 (note there is no newline at the top of the file)

@@ Line 106: / Line 106: @@
 === Point the ColladaCGF to the .dae file ===
-The '''dae''' file is to be selected, '''rightclick > ColladaCGF''' and voila! by ''automagic'' a bunch of murr-murr and computer speak will fill a dark frame, once you notice the computer has stopped spewing insults and dark magic, there might be a blinking cursor waiting no you to press [enter] key and close the window. You might have just converted your first '''CGF''' file on Linux. Or you will be in due time. Conversions often fail due to not adhering to the convention mentioned above.
+The '''.dae''' file is to be selected, '''rightclick > ColladaCGF''' and voila! by ''automagic'' a bunch of murr-murr and computer speak will fill a dark frame, once you notice the computer has stopped spewing insults and dark magic, there might be a blinking cursor waiting no you to press ['''enter'''] key and close the window. You might have just converted your first '''CGF''' file on Linux. Or you will be in due time. Conversions often fail due to not adhering to the ''convention'' mentioned earlier.
 === Find the cgf file ===

@@ Line 64: / Line 64: @@
 For this to work at all some prerequisites are to be met. You didn't think you'll get off
 the hook as easy, didn't you?<br>
-# We need working ColladaCGF in wine, for this we need working PyFFI in wine, and for this we need working Python in wine in the first place. For this all to work at all certain versions are to be downloaded and fed to wine:<br>
+ We need working '''ColladaCGF''' in '''wine''', for this we need working '''PyFFI''' in '''wine''', and for this we need working '''Python''' in '''wine''' in the first place.
-* Python 2.6.6 (or ealrier, but idealy exactly 2.6.6 (32bit release only)
+For this all to work at all certain versions are to be downloaded and fed to '''wine''':<br>
-* PyFFI 2.1.11 (the last one that works with 2.x python, newer require python 3.x)
+* Python 2.6.6 (or earlier, but ideally ''exactly'' 2.6.6 (32bit release only)
 * ColladaCGF 0.3.9 (the last one available)
-For this to work you will need your linux to be either "multilib" (more likely applies to you) or 32bit (less likely but possible)
+For this to work you will need your '''Linux''' to be either "''multilib''" (more likely applies to you) or 32bit (less likely but possible)
-Install In that order (Python, PyFFI, Collada) and see it is in the right wine prefix:
+Install In that exact order (Python, PyFFI, Collada).<br>
+The very installation process:
-both files:<br>
+# Locate the repositories
-"C:\Python26\python.exe"
+# Download the corresponding versions and to what place locally
 and
-Now if you are not using XFCE4 as your GUI too bad you're just out of luck. Otherwise open the Custom Actions chooser via the Edit menu of Thunar and make a new custom action:
+Now if you are not using '''XFCE4''' as your GUI, ''too bad you're just out of luck''. Otherwise open the Custom Actions chooser via the Edit menu of '''Thunar''' and make a new custom action:
 [[File:Step04.png|200px|thumb|center|Custom Actions setup with Thunar and XFCE4]]
-I named the action [ ColladaCGF ] and gave it the usual python icon. The description should be obvious: [ Convert a dae file into cgf ]. The command that worked for me was:
+I named the action [ ColladaCGF ] and gave it the default python icon. The description should be obvious: [ Convert a dae file into cgf ]. The command that worked for me was:
 [ wineconsole "C:\Python26\python.exe" "C:\Python26\Scripts\colladacgf.py" %F --pause ]
@@ Line 95: / Line 99: @@
 [ *.dae;*.DAE ]
-mind the semicolon. And the affected files are the text files (.dae files look like XML files) and other files, just in case. Never mind this crazy screenshot - it is CGI - so you have it all on one place.
+mind the semicolon. And the affected files are the ''text files'' (since '''.dae''' files look like '''XML''' files) and ''other files'', just in case. Never mind this impossible screenshot - it is CGI - so you have it all on one place for '''''maximum convenience'''''.
-Apply close and restart Thunar. Now on You should have a context option for each dae file:
+Apply, close and restart '''Thunar'''. Now on You should have a context option for each '''.dae''' file:
 [[File:Step05.png|200px|thumb|center|ColladaCGF usage in XFCE on Linux]]

@@ Line 49: / Line 49: @@
 | Triangulate || leave no uncertain surfaces unresolved by blender.
 |-
-| Apply Transforms || Viewport (it is usually save to assume this is true)
+| Apply Transforms || Viewport (it is usually safe to assume this is true)
 |-
-| Selection Only || we rarely need everything from the file - watch for proper parenting!
+| Selection Only || we rarely need everything from the file - watch for proper parent-children chains!
 |-
 | Include children || if parenting is properly laid out - this works miracles!
 |-
-| Use Object Instances || don't use this - i tried it once and it was ugly
+| Use Object Instances || don't use this - i tried it once and it was ''ugly''
 |-
-| Use Blender Profile || this is best left off - always leave it off for cryengine export.
+| Use Blender Profile || this is best left off - always leave it off for Cryengine export.
 |}

@@ Line 13: / Line 13: @@
 [[File:Step01.png|200px|thumb|center|Prepare Collection]]
-For a Mesh to be fit for cryengine it has to fulfill several criteria due to how compromises were made.<br>
+For a Mesh to be fit for cryengine it has to fulfill several criteria due to how some compromises were made.<br>
-It is a convention and if one sticks to it good results won't fail to materialize.<br>
+It is a ''convention'' and if one sticks to it good results will ensue.<br>
 # No more than two triangles should share same edge.
-# There should be nothing but triangles (or quads) as the final result - remove all and any nodes and or lines (primitives)...
+# There should be nothing but triangles (or quads) as the final result - remove all and any nodes and or lines (''primitives'')...
-# There shoudl be no triangles of surface size zero (degenerate faces).
+# There should be no triangles of surfaces of size zero (degenerate faces).
 # It is desirable for the mesh be airtight, but there are valid exceptions.
@@ Line 25: / Line 25: @@
-The Object is to be assigned To a Collection (no more Groups in blender 3.x) that has the same name<br>
+The Object is to be assigned To a ''Collection'' (no more ''Groups'' in blender 3.x) that shares the same name<br>
-The .blend file is to be saved with the same name as the object and collection.<br>
+The '''.blend''' file is to be saved with the same name, so that it shares (again) the same name as the object and collection.<br>
-We should now be ready for the export to collada (.dae file)<br>
+We should now be ready for the export to collada ('''.dae''' file)<br>

@@ Line 7: / Line 7: @@
 == Preparing The geometry ==
 === now with blender 3.x ===
-This is a procedure covering the ever growing technology gap between the free and ever livid
+This is a procedure covering the ever growing technology gap between the free and ever livid blender and the aging cryengine2.<br>
-blender and the aging cryengine2. Just get any blender past 3.x release.
+Just get any blender past 3.x release.
 === Get it ready ===

@@ Line 288: / Line 288: @@
 === Run the editor ===
 You can now start the file by typing ['''MWLLeditor.sh'''] in a command prompt and pressing enter.
-Pick a map ([TC_Reference] comes to mind) and try add an brush. Here on is uncharted territory, keep me posted!
+Pick a map (['''TC_Reference'''] comes to mind) and try add an ''brush''. Here on is uncharted territory, keep me posted!
 === What breaks in the editor and how to work around it ===
 ''TODO''