ModelView - Revision history

TopAce: minor edits

2021-05-17T06:56:14Z

minor edits

Jr2: Clarified how old ModViw is a bit

2017-11-25T15:23:32Z

Clarified how old ModViw is a bit

← Older revision		Revision as of 15:23, 25 November 2017
Line 1:		Line 1:
	Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, and no longer actively maintained, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.		Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, and no longer actively maintained (the latest High Limits version dates from ''2007''), many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.

	The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly version (the community standard) are below.		The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly version (the community standard) are below.

Jr2: added 'no longer actively maintained'

2017-11-25T01:54:06Z

added 'no longer actively maintained'

← Older revision		Revision as of 01:54, 25 November 2017
Line 1:		Line 1:
	Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.		Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, and no longer actively maintained, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.

	The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly version (the community standard) are below.		The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly version (the community standard) are below.

Jr2 at 23:32, 24 November 2017

2017-11-24T23:32:58Z

← Older revision		Revision as of 23:32, 24 November 2017
Line 1:		Line 1:
	Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.		Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.

	The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly ~~vrsion~~ (the community standard) are below.		The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly version (the community standard) are below.

Jr2 at 23:31, 24 November 2017

2017-11-24T23:31:36Z

← Older revision		Revision as of 23:31, 24 November 2017
Line 15:		Line 15:
	Newer versions of Modelview include a POF editor, as well as a simple POF viewer. To begin editing, click the "POF-Editor" button on the far-right of your toolbar. If it's not there, you don't have the latest version. (see above)		Newer versions of Modelview include a POF editor, as well as a simple POF viewer. To begin editing, click the "POF-Editor" button on the far-right of your toolbar. If it's not there, you don't have the latest version. (see above)

	Some features like Dockpoint and Path editing are not implemented. You have to use the [[POF Constructor Suite\|PCS]] to set these. Also note that thrusters in Modview are only partially ~~implimented~~ - you can edit existing ones, but you can't delete them or create new ones.		Some features like Dockpoint and Path editing are not implemented. You have to use the [[POF Constructor Suite\|PCS]] to set these. Also note that thrusters in Modview are only partially implemented - you can edit existing ones, but you can't delete them or create new ones.

Ngld: Fixed download link

2017-11-21T22:44:28Z

Fixed download link

← Older revision		Revision as of 22:44, 21 November 2017
Line 8:		Line 8:
	== Installing Modview ==		== Installing Modview ==

	~~# Make sure you have the latest Modview: beta 05 build 28:~~		[https://sectorgame.com/fsfiles/uploads/Resources%20and%20Tools/Tools/ModelView32.zip Download this archive] and follow the installation instructions inside.
	#*[~~http~~://~~webzoom.freewebs~~.com/~~twisted-infinities-va/modv32b5.zip Fairly reliable host] <br>OR~~
	~~#*[http:~~//~~www.geocities.com~~/~~vasudanad~~/~~modv32b5~~.zip ~~Not-so-reliable host]~~
	~~# Install it to wherever (usually defaults to "C:\DMTOOLS\MODVIW32")~~
	~~# And then paste the exe in~~ this ~~zip over the one in the "C:\DMTOOLS\MODVIW32" folder (or wherever you installed it to.)~~
	~~#*[http://webzoom.freewebs.com/twisted-infinities-va/modviw32_high_limits.zip Fairly reliable host~~] ~~<br>OR~~
	~~#*[http://www.geocities.com/vasudanad/modviw32.zip Not-so-reliable host]~~


	~~The .exe there is exactly the same as the regular 05, except it has most of~~ the ~~limits regarding FS models I could find bumped really high~~.

Snail at 22:24, 11 February 2009

2009-02-11T22:24:49Z

← Older revision		Revision as of 22:24, 11 February 2009
Line 1:		Line 1:
	Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[~~Freespace~~]] and [[~~Freespace~~ 2]]. Though not as versatile as PCS, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.		Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[FreeSpace]] and [[FreeSpace 2]]. Though not as versatile as PCS, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.

	The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly vrsion (the community standard) are below.		The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly vrsion (the community standard) are below.
Line 27:		Line 27:


	=== ~~Freespace~~ Co-ordination system for models ===		=== FreeSpace Co-ordination system for models ===

	It is impertive you be familiar with the co-ordination system of ~~Freespace~~ 2, in order to add additional features to your model such as turret or fighter weapon firing points, thruster glows, dockpoints, paths, shields and subsystems.		It is impertive you be familiar with the co-ordination system of FreeSpace 2, in order to add additional features to your model such as turret or fighter weapon firing points, thruster glows, dockpoints, paths, shields and subsystems.

	Modelview is the best way to learn how this system works since it uses a WYSIWYG viewing pane. The axis directions are as follows:		Modelview is the best way to learn how this system works since it uses a WYSIWYG viewing pane. The axis directions are as follows:
Line 58:		Line 58:
	If you're using Modview and FS_Open, chances are, you won't be able to see all or most textures. This is because FSO now uses the DDS format for textures, whilst Modview still uses only 256 colour PCX images. If Modview does not find any PCX images, it will complain that the model has none there.		If you're using Modview and FS_Open, chances are, you won't be able to see all or most textures. This is because FSO now uses the DDS format for textures, whilst Modview still uses only 256 colour PCX images. If Modview does not find any PCX images, it will complain that the model has none there.

	The best way I've found to circumvent this is to create a dummy 'root' ~~Freespace~~ directory with a "data\maps" directory inside it. In that maps folder you put copies of all textures you want modview to be able to see, and batch-process them in something like IrfanView to turn them all into 256 colour PCX's. While clumsy, it does work and lets you see all your models.		The best way I've found to circumvent this is to create a dummy 'root' FreeSpace directory with a "data\maps" directory inside it. In that maps folder you put copies of all textures you want modview to be able to see, and batch-process them in something like IrfanView to turn them all into 256 colour PCX's. While clumsy, it does work and lets you see all your models.

	==== Model ====		==== Model ====

VA at 16:16, 11 January 2006

2006-01-11T16:16:02Z

← Older revision		Revision as of 16:16, 11 January 2006
Line 27:		Line 27:


	== Freespace Co-ordination system for models ==		=== Freespace Co-ordination system for models ===

	It is impertive you be familiar with the co-ordination system of Freespace 2, in order to add additional features to your model such as turret or fighter weapon firing points, thruster glows, dockpoints, paths, shields and subsystems.		It is impertive you be familiar with the co-ordination system of Freespace 2, in order to add additional features to your model such as turret or fighter weapon firing points, thruster glows, dockpoints, paths, shields and subsystems.
Line 55:		Line 55:
	----		----

	== A Note About Textures ==		=== A Note About Textures ===
	If you're using Modview and FS_Open, chances are, you won't be able to see all or most textures. This is because FSO now uses the DDS format for textures, whilst Modview still uses only 256 colour PCX images. If Modview does not find any PCX images, it will complain that the model has none there.		If you're using Modview and FS_Open, chances are, you won't be able to see all or most textures. This is because FSO now uses the DDS format for textures, whilst Modview still uses only 256 colour PCX images. If Modview does not find any PCX images, it will complain that the model has none there.

	The best way I've found to circumvent this is to create a dummy 'root' Freespace directory with a "data\maps" directory inside it. In that maps folder you put copies of all textures you want modview to be able to see, and batch-process them in something like IrfanView to turn them all into 256 colour PCX's. While clumsy, it does work and lets you see all your models.		The best way I've found to circumvent this is to create a dummy 'root' Freespace directory with a "data\maps" directory inside it. In that maps folder you put copies of all textures you want modview to be able to see, and batch-process them in something like IrfanView to turn them all into 256 colour PCX's. While clumsy, it does work and lets you see all your models.

	== Model ==		==== Model ====

	In this pane you can edit		In this pane you can edit
Line 72:		Line 72:


	== Submodels ==		==== Submodels ====

	Every piece of geometry on your ship that is not the hull or LODs, is some type of sub-model, or in other words, a child of a parent. Eg: a spinning radar dish is a submodel with the main hull as a parent object. This means that the radar dish is attached to the hull, which is usually what we want.		Every piece of geometry on your ship that is not the hull or LODs, is some type of sub-model, or in other words, a child of a parent. Eg: a spinning radar dish is a submodel with the main hull as a parent object. This means that the radar dish is attached to the hull, which is usually what we want.
Line 103:		Line 103:


	== Subsystems ==		==== Subsystems ====

	These are the things that the player can target and destroy in-game. Click on the rectangle next to the red x. This creates a new subsystem with no radius or position. Set the size of the radius to a number which is high enough for you to see it easily. Fighter subsystems are usually only a couple of meters across, while cap-ship subsystems can be much larger.		These are the things that the player can target and destroy in-game. Click on the rectangle next to the red x. This creates a new subsystem with no radius or position. Set the size of the radius to a number which is high enough for you to see it easily. Fighter subsystems are usually only a couple of meters across, while cap-ship subsystems can be much larger.
Line 121:		Line 121:


	== Shields ==		==== Shields ====

	Can't really do much here but import the shield data from another model, remove them all together or change the size along any of the three axis'. Things like the strength and recharge rate of the shields are set in the tables instead.		Can't really do much here but import the shield data from another model, remove them all together or change the size along any of the three axis'. Things like the strength and recharge rate of the shields are set in the tables instead.


	== Guns ==		==== Guns ====

	The Guns section refers to the primary and missile fire points on fighters and bombers. They consist of a location and a normal, although the normal is ignored by the game - they always point forwards. The firing points of guns or missiles are arranged in banks. You may have noticed how the Herc 1 has two banks - one bank consists of 4 fire points and one of 2, giving it six firing points all up. The Erinyes has two banks of 4 each, giving it 8 all up. Each bank has one primary/secondary weapon assigned to it in the fighter loadout screen in-game.		The Guns section refers to the primary and missile fire points on fighters and bombers. They consist of a location and a normal, although the normal is ignored by the game - they always point forwards. The firing points of guns or missiles are arranged in banks. You may have noticed how the Herc 1 has two banks - one bank consists of 4 fire points and one of 2, giving it six firing points all up. The Erinyes has two banks of 4 each, giving it 8 all up. Each bank has one primary/secondary weapon assigned to it in the fighter loadout screen in-game.
Line 136:		Line 136:
	Note that this is not always followed, even by Volition. The [[GTB Ursa]] has a highly unusual, asymetrical firing setup, as do several [[Shivan]] fighters and bombers.		Note that this is not always followed, even by Volition. The [[GTB Ursa]] has a highly unusual, asymetrical firing setup, as do several [[Shivan]] fighters and bombers.

	== Turrets ==		==== Turrets ====

	Turrets are probably what Modview does best. To make a turret work, you need to use this section in conjunction with the associated submodel properties and your ships entry in the ships.tbl file. If you define a turret in here, but don't give it any properties in one or both of the other two areas, it won't be seen as a turret in-game.		Turrets are probably what Modview does best. To make a turret work, you need to use this section in conjunction with the associated submodel properties and your ships entry in the ships.tbl file. If you define a turret in here, but don't give it any properties in one or both of the other two areas, it won't be seen as a turret in-game.
Line 158:		Line 158:


	== Thrusters ==		==== Thrusters ====

	Since this has only been half-implimented, it's a bit useless. You can only change the location, size and direction of existing thruster glows, but not make new ones or delete old ones.		Since this has only been half-implimented, it's a bit useless. You can only change the location, size and direction of existing thruster glows, but not make new ones or delete old ones.

VA at 16:14, 11 January 2006

2006-01-11T16:14:41Z

← Older revision		Revision as of 16:14, 11 January 2006
Line 1:		Line 1:
	Descent ~~Manager~~'s ~~ModelView32~~, written by Heiko Herrmann, is the ~~most popular program for~~ the viewing ~~and editing~~ of ~~Freespace~~ POF files. ~~Its features include the ability~~ to ~~edit turrets~~, ~~subsystems~~, ~~shield meshes~~, ~~weapon banks, gunpoints~~ and ~~texture names, as~~ well ~~as providing a wealth of information about~~ the ~~model~~.		Originally part of the Descent Network's FS Toolkit, '''Modelview 32''', written by Heiko Herrmann, along with [[POF Constructor Suite]] (or PCS), is one of the principal tools used in the creation, editing, or viewing of POF files, the model format used by [[Freespace]] and [[Freespace 2]]. Though not as versatile as PCS, many find its user interface easier to understand, and more intuitive. It was also coded expressly as a POF ''viewer'', with the POF editing functions almost secondary. PCS was coded principally as a POF ''editor'', and its viewer is less well integrated into the program.

	~~A stable, intuitive interface and~~ the ~~ability~~ to ~~categorize~~ and ~~browse~~ the ~~models of VP files have seen Modelview become a foundation of Freespace modding~~.		The most recent modifications to the Modelview program allow higher poly models to be loaded and edited. Instructions on installing this higher poly vrsion (the community standard) are below.


Line 22:		Line 22:
	== How to edit a POF with Modview: ==		== How to edit a POF with Modview: ==

	~~You can only modify~~ a POF ~~file with ''newer'' versions of Modview~~. To begin editing, click the "POF-Editor" button on the far-right of your toolbar. If it's not there, you don't have the latest version. (see above)		Newer versions of Modelview include a POF editor, as well as a simple POF viewer. To begin editing, click the "POF-Editor" button on the far-right of your toolbar. If it's not there, you don't have the latest version. (see above)

	Some features like Dockpoint and Path editing are not implemented. You have to use the [[POF Constructor Suite]] to set these. Also note that thrusters in Modview are only partially implimented - you can edit existing ones, but you can't delete them or create new ones.		Some features like Dockpoint and Path editing are not implemented. You have to use the [[POF Constructor Suite\|PCS]] to set these. Also note that thrusters in Modview are only partially implimented - you can edit existing ones, but you can't delete them or create new ones.


Line 33:		Line 33:
	Modelview is the best way to learn how this system works since it uses a WYSIWYG viewing pane. The axis directions are as follows:		Modelview is the best way to learn how this system works since it uses a WYSIWYG viewing pane. The axis directions are as follows:

	X-axis: Right & Left => Width of your ship		{\|
	Y-axis: Up & Down => Height of your ship		\| width=50px\|X-axis:
	Z-axis, Forward & Back => Length of your ship		\| width=100px\|Right & Left
			\| Width of your ship
			\|-
			\|Y-axis:
			\|Up & Down
			\|Height of your ship
			\|-
			\|Z-axis:
			\|Forward & Back
			\|Length of your ship
			\|}
	The numbers you enter for the co-ordinates of anything in Modview are ''in-game meter units''. Normally, the co-ordinates of 0,0,0 are the model's center (the point around which the model rotates).		The numbers you enter for the co-ordinates of anything in Modview are ''in-game meter units''. Normally, the co-ordinates of 0,0,0 are the model's center (the point around which the model rotates).

Line 100:		Line 110:
	Now, start playing with the numbers. First, set its height - the Y co-ordinates. You can only change the position of your subsystems by changing their co-ordinates manually. Set it to the right place you want it to be. Do not place a subsystem inside or outside the hull plating of a ship since this would result in an un-hitable subsystem. Try to have the center of the cubes of subsystems on the surface of the hull since this is the most optimal, but FS will basically set any polys it finds inside the radius to be part of that subsystem, and when they are hit, it will damage the subsystem. Standard subsystems on cap-ships include:		Now, start playing with the numbers. First, set its height - the Y co-ordinates. You can only change the position of your subsystems by changing their co-ordinates manually. Set it to the right place you want it to be. Do not place a subsystem inside or outside the hull plating of a ship since this would result in an un-hitable subsystem. Try to have the center of the cubes of subsystems on the surface of the hull since this is the most optimal, but FS will basically set any polys it finds inside the radius to be part of that subsystem, and when they are hit, it will damage the subsystem. Standard subsystems on cap-ships include:

	$Communications		*'''$Communications'''
	$Engine		*'''$Engine'''
	$Navigation		*'''$Navigation'''
	$Sensors		*'''$Sensors'''
	$Weapons		*'''$Weapons'''

	The type of subsystem box refers to whether or not the subsystem is a normal visible & destroyable subsystem, or the special hidden "$Split 01" type. The $Split## types of subsystems refer to places that FS will snap the model when it is destroyed. Think of them as weak points in the structure that would logically break when the ship explodes, such as a thin neck.		The type of subsystem box refers to whether or not the subsystem is a normal visible & destroyable subsystem, or the special hidden "$Split 01" type. The $Split## types of subsystems refer to places that FS will snap the model when it is destroyed. Think of them as weak points in the structure that would logically break when the ship explodes, such as a thin neck.

			Remember to add a table entry for any new subsystems in the [[ships.tbl]]


Line 121:		Line 134:
	You should also try not to put the fire points out too far laterally or vertically from the cockpit, since this can create problems actually ''hitting'' small targets with both shots.		You should also try not to put the fire points out too far laterally or vertically from the cockpit, since this can create problems actually ''hitting'' small targets with both shots.

			Note that this is not always followed, even by Volition. The [[GTB Ursa]] has a highly unusual, asymetrical firing setup, as do several [[Shivan]] fighters and bombers.

	== Turrets ==		== Turrets ==
Line 132:		Line 146:
	The fire points are identical to gun firing points, but you've already done the normal. Here you only need to enter the places you want the weapon to shoot from (you can have at most 3, else it crashes the game).		The fire points are identical to gun firing points, but you've already done the normal. Here you only need to enter the places you want the weapon to shoot from (you can have at most 3, else it crashes the game).

	Finally, to complete your turret, you also need to enter a line in your ships entry in the ships table such as:		Finally, to complete your turret, you also need to enter a line in your ships entry in the [[ships.tbl\|ships table]] such as:

	$Subsystem: Turret02a, 1.875, 3.0		$Subsystem: Turret02a, 1.875, 3.0

VA at 15:52, 11 January 2006

2006-01-11T15:52:22Z

Show changes