Blender to POF Conversions - Revision history

Talon1024: /* Multi-part (rotating) Turrets: */ The new way of setting up multi-part turrets in PCS2

2015-07-08T04:20:12Z

Multi-part (rotating) Turrets:: The new way of setting up multi-part turrets in PCS2

← Older revision		Revision as of 04:20, 8 July 2015
Line 214:		Line 214:
	As with single part turrets, the naming must include ''''turret'''' or ''''gun'''' in it somewhere so FS knows to treat it differently, and standard practice is to call the base ''''Turret01-base'''' and the arm ''''Turret01-arm''''. Also again it is easier to set up turret data in PCS2 after conversion (Setting the turret axis rotation MUST be done in PCS2 in the subobjects field after conversion or else your turrets won't work at all)<br>		As with single part turrets, the naming must include ''''turret'''' or ''''gun'''' in it somewhere so FS knows to treat it differently, and standard practice is to call the base ''''Turret01-base'''' and the arm ''''Turret01-arm''''. Also again it is easier to set up turret data in PCS2 after conversion (Setting the turret axis rotation MUST be done in PCS2 in the subobjects field after conversion or else your turrets won't work at all)<br>

	Setting up firepoints, paths and properties ~~in Blender~~ is the same as for single part turrets.~~.<br><br>~~		Setting up firepoints, paths and properties for multi-part turrets is mostly the same as it is for setting up single part turrets, except the helper object should be parented to the turret arm object instead of the turret base object, and the object which is the parent of the firepoints should be named '''multifirepoints'''.

	<br>[[Image:BlenderMultiPartTurretSetup.jpg]]<br>		<br>[[Image:BlenderMultiPartTurretSetup.jpg]]<br>
Line 221:		Line 221:
	detail0		detail0
	\|		\|
	\|-Turret01 ~~(single part turret)~~		\|-Turret01
	\|		\|
	\|-Turret02-base		\|-Turret02-base (multi-part turret)
	\|		\|
	\|-Turret02-arm		\|-Turret02-arm
	\|		\|
	\|-helper02		\|-helper02
	\|		\|
	\|-~~firepoints02~~		\|-multifirepoints02
	\| \|		\| \|
	\| \|-firepoint02-01		\| \|-firepoint02-01
	\| \|-firepoint02-02		\| \|-firepoint02-02
	\|		\|
	\|-path07		\|-path07
	\| \|		\| \|
	\| \|-path07-01		\| \|-path07-01
	\| \|-path07-02		\| \|-path07-02
	\|		\|
	\|-properties02		\|-properties02
	\|		\|
	\|-$fov=180		\|-$fov=180
	\|-$name=main%turret (The % will be converted to a space automatically)		\|-$name=main%turret (The % will be converted to a space automatically)
	\|-$special=subsystem		\|-$special=subsystem


	===Subobjects/Modeled Subsystems:===		===Subobjects/Modeled Subsystems:===

Esarai: Added hierarchy demonstration for live debris

2013-10-01T12:23:16Z

Added hierarchy demonstration for live debris

@@ Line 133: / Line 133: @@
 But that's not all!  What if you want parts of the ship to peel away as lasers pierce into its vulnerable subsystems?  Cue Live Debris.  Just like normal debris, but with a different naming convention: ''''debris-<subsystem>XX'''' where <subsystem> is the exact name of the specified system, and XX is a number starting at 01 and going to 99.  Useful if you want radar dishes, armor plates, bulkheads and whatever else you can think of to float off into space after too much high-energy love.
+Example:
 ===Single-part Turrets:===

Esarai: Added blurb about live debris.

2013-10-01T04:47:21Z

Added blurb about live debris.

← Older revision		Revision as of 04:47, 1 October 2013
Line 130:		Line 130:
	debris02		debris02
	debris03 etc		debris03 etc

			But that's not all! What if you want parts of the ship to peel away as lasers pierce into its vulnerable subsystems? Cue Live Debris. Just like normal debris, but with a different naming convention: ''''debris-<subsystem>XX'''' where <subsystem> is the exact name of the specified system, and XX is a number starting at 01 and going to 99. Useful if you want radar dishes, armor plates, bulkheads and whatever else you can think of to float off into space after too much high-energy love.



	===Single-part Turrets:===		===Single-part Turrets:===

Esarai: /* Gun/Missile ports: */

2011-06-12T05:22:15Z

Gun/Missile ports:

← Older revision		Revision as of 05:22, 12 June 2011
Line 276:		Line 276:
	Example:		Example:
	detail0		detail0
	\|		gunbank01 (This will create a gunbank with two firepoints on it)
	\|-gunbank01 (This will create a gunbank with two firepoints on it)
	\|		\|
	\|-gunbank01-01		\|-gunbank01-01

Talon1024: /* Bay Paths: */

2011-05-29T21:07:25Z

Bay Paths:

← Older revision		Revision as of 21:07, 29 May 2011
Line 316:		Line 316:
	===Bay Paths:===		===Bay Paths:===

	Bay paths are special paths that fighters follow when they launch or land from a capital ship. They usually consist of 5 points ~~with varying radii~~.		Bay paths are special paths that fighters follow when they launch or land from a capital ship. They usually consist of 5 points. The first point on the bay path is the outermost point, and the last point on the bay path is the innermost point. The first point usually has a very large radius, and the radius of the points usually decrease from one point to the next.

	To set up bay paths in Blender, create a helper object as a child of detail0, create an empty named 'bay01' as a child of the detail0 helper object, and create the bay path vertices as children of the bay path parent object.		To set up bay paths in Blender, create a helper object as a child of detail0, create an empty named 'bay01' as a child of the detail0 helper object, and create the bay path vertices as children of the bay path parent object.

Talon1024: Added Bay paths

2011-05-29T04:00:33Z

Added Bay paths

@@ Line 296: / Line 296: @@
 ===Insignia:===
-Squadren Insignia should be treated similarly to nameplates in terms of making them on a set of faces that floats just above the hull.<br>
+Squadron Insignia should be treated similarly to nameplates in terms of making them on a set of faces that floats just above the hull.<br>
 UV map them and apply a texture called 'insignia' (it's a good idea to use an actual insignia texture here, but the NAME is important because the Collada importer in PCS2 will know to ignore it and not put it on the texture list for the ship), and call them: ''''insigLODXX-YY'''', where XX is the LOD number and YY is the number of this particular insignia (for if you have more than one). As the XX indicates, you can create insignia that will appear on LODs too, which is a good idea or else in-game your insignia will suddenly vanish when the ship moves away and the LOD clicks over.<br>
@@ Line 313: / Line 313: @@
   insigLOD02-01
   insigLOD02-02
 ===Docking Points:===

VA: Oops.

2011-03-10T07:54:30Z

Oops.

← Older revision		Revision as of 07:54, 10 March 2011
Line 1:		Line 1:
	==Important Links:==		==Important Links & Video Tutorials:==
	[[~~POF to~~ Blender ~~Conversions~~]], [[~~Blender~~]], [[POF ~~Constructor Suite 2~~]], [[Collada Importer]]		[[Blender]]<br>[[POF Constructor Suite 2]]<br>[[POF to Blender Conversions]]<br>[[Collada Importer]]<br>
	Rga_Noris has started creating video tutorials on the Blender -> POF conversion process which explains it step by step: [http://www.hard-light.net/forums/index.php?topic=75005.0 Thread link]		Rga_Noris has started creating video tutorials on the Blender -> POF conversion process which explains it step by step: [http://www.hard-light.net/forums/index.php?topic=75005.0 Thread link]

VA: Link to Rga's video tutorial thread. Hopefully these will eventually explain everything this document does! :)

2011-03-10T07:51:49Z

Link to Rga's video tutorial thread. Hopefully these will eventually explain everything this document does! :)

← Older revision		Revision as of 07:51, 10 March 2011
Line 1:		Line 1:
	==Important ~~Wiki Page~~ Links:==		==Important Links:==
	[[POF to Blender Conversions]], [[Blender]], [[POF Constructor Suite 2]], [[Collada Importer]]		[[POF to Blender Conversions]], [[Blender]], [[POF Constructor Suite 2]], [[Collada Importer]]
			Rga_Noris has started creating video tutorials on the Blender -> POF conversion process which explains it step by step: [http://www.hard-light.net/forums/index.php?topic=75005.0 Thread link]

	==Getting a Collada-capable PCS2 version:==		==Getting a Collada-capable PCS2 version:==
	# [http://www.cse.unsw.edu.au/~samm/pcs2.7z ~~download The~~ main PCS2 installer package] Install this first so you have the correct DLLs in place in your PCS2 directory.		# [http://www.cse.unsw.edu.au/~samm/pcs2.7z Download the main PCS2 installer package] Install this first so you have the correct DLLs in place in your PCS2 directory.
	# [http://www.cse.unsw.edu.au/~samm/dlls.7z Dependency 1: The libcollada DLL file] Place this in your PCS2 directory.		# [http://www.cse.unsw.edu.au/~samm/dlls.7z Dependency 1: The libcollada DLL file] Place this in your PCS2 directory.
	# [http://scoobydoo.freespacemods.net/Completed/Misc/pcs2.exe The DAE capable PCS2 EXE itself] Place this in your PCS2 directory, backing up the previous one if you like. (Old link, Optional)		# [http://scoobydoo.freespacemods.net/Completed/Misc/pcs2.exe The DAE capable PCS2 EXE itself] Place this in your PCS2 directory, backing up the previous one if you like. (Old link, Optional)

SpaceFreak: /* Geometry: */ Updatey

2011-03-03T18:54:38Z

Geometry:: Updatey

← Older revision		Revision as of 18:54, 3 March 2011
Line 41:		Line 41:

	===Geometry:===		===Geometry:===
	As far as I have been able to tell, all geometry the PCS2 Collada importer will accept must be fully triangulated. (Ctrl+T to triangulate selected ~~object)~~<br>		As far as I have been able to tell, all geometry the PCS2 Collada importer will accept must be fully triangulated. However, you can set Blender's Collada exporter to do this for you on exporting - that way, you can keep your blendfile in quads.<br>
	<br>[[Image:BlenderTriangulatingSelectedFaces.jpg]]<br>		If you do want to triangulate something manually, use Ctrl+T to triangulate selected.<br>
	~~All mirror or edgesplit~~ modifiers ~~must be applied before~~ exporting or ~~they won't work and~~ you'll end up with half your model or something. ;)<br>		<br>[[Image:BlenderTriangulatingSelectedFaces.jpg]]<br><br>
			With the bottom-most button "Apply modifiers", you can apply all modifiers on exporting - if you're on an older version of Blender, you have to do this by hand, or you'll end up with half your model or something. Do consider updating in that case.<br><br>
	Messy geometry will ''usually'' convert correctly anyway, but I would suggest making it a point of pride to produce clean meshes that will ''definitely'' convert. That is, avoid:<br>		Messy geometry will ''usually'' convert correctly anyway, but I would suggest making it a point of pride to produce clean meshes that will ''definitely'' convert. That is, avoid:<br>
	Faces that occupy the same plane in 3d space, as this will cause bad Z-fighting in-game<br>		Faces that occupy the same plane in 3d space, as this will cause bad Z-fighting in-game.<br>
	<br>[[Image:BlenderErrorSamePlane.jpg]]<br><br>		<br>[[Image:BlenderErrorSamePlane.jpg]]<br><br>
	Faces that exactly overlap onto each other<br>		Faces that exactly overlap onto each other<br>

VA: /* Insignia: */ Note on pic.

2011-02-17T16:26:48Z

Insignia:: Note on pic.

← Older revision		Revision as of 16:26, 17 February 2011
Line 300:		Line 300:
	Insignia should not be children of anything.<br><br>		Insignia should not be children of anything.<br><br>

			(Note: The following image was taken when the key phrase was 'insg' rather than 'insig' as it is now. Use 'insig' not 'insg'!)
	<br>[[Image:BlenderInsigniaSetup.jpg]]<br>		<br>[[Image:BlenderInsigniaSetup.jpg]]<br>