FileFront Forums
Page 5 of 7 « First 34 5 67
Show 50 post(s) from this thread on one page

FileFront Forums (http://forums.filefront.com/)
-   ST:A2 Modding, Mapping and Editing (http://forums.filefront.com/st-a2-modding-mapping-editing-139/)
-   -   Joint/Hardpoint Tree Structure Tool (http://forums.filefront.com/st-a2-modding-mapping-editing/428340-joint-hardpoint-tree-structure-tool.html)

Dominus_Noctis April 22nd, 2011 08:03 PM
Re: Joint/Hardpoint Tree Structure Tool
 
I can easily zip up and attach the rest of the sprite stuff if that would help (will do so now in fact). I'll talk to Optec this weekend and see if he has the time/information readily available to help :)

Muldrf April 24th, 2011 04:32 AM
Re: Joint/Hardpoint Tree Structure Tool
 
From the setup I doubt any other spr files have fleetops content in them.

Code:
@sprite_node Warpglowspriteblue6 flare_glow_soft const (6,6) (0.06,0.06,0.12) billboard
@sprite_node Warpglowspriteblue6A flare_glow_soft const (6,6) (0.0,0.0675,0.12) billboard
@sprite_node Warpglowspriteblue6B flare_glow_soft const (6,6) (0.0,0.09,0.12) billboard
@sprite_node Warpglowspriteblue6C flare_glow_soft const (6,6) (0.0,0.045,0.06) billboard
@sprite_node Warpglowspritedarkblue6 flare_glow_soft const (6,6) (0.045,0.045,0.09) billboard
@sprite_node Warpglowspritered6 flare_glow_soft const (6,6) (0.12,0.0,0.0) billboard
@sprite_node Warpglowspritered6A flare_glow_soft const (6,6) (0.12,0.04,0.0075) billboard
@sprite_node Warpglowspritered6B flare_glow_soft const (6,6) (0.12,0.015,0.015) billboard
@sprite_node Warpglowspritegreen6 flare_glow_soft const (6,6) (0.0,0.14,0.0) billboard
@sprite_node Warpglowspritegreen6A flare_glow_soft const (6,6) (0.03,0.12,0.06) billboard
@sprite_node Warpglowspritegreen6B flare_glow_soft const (9,9) (0.375,0.6,0.3) billboard
@sprite_node Warpglowspritegreen6C flare_glow_soft const (6,6) (0.0,0.09,0.0) billboard
@sprite_node Warpglowspritegreen6incubation flare_glow_soft IncubationGlow (10,10) (0.0,0.14,0.0) billboard
@sprite_node Warpglowspriteocher6 flare_glow_soft const (6,6) (0.07,0.10,0.04) billboard
@sprite_node Warpglowspritepink6A flare_glow_soft const (6,6) (0.12,0.075,0.105) billboard
@sprite_node Warpglowspritepink6B flare_glow_soft DefenderGlow (10,10) (0.12,0.075,0.105) billboard
@sprite_node Warpglowspritepurple6A flare_glow_soft const (6,6) (0.045,0.0,0.12) billboard
@sprite_node Warpglowspritewhite6 flare_glow_soft const (6,6) (0.06,0.06,0.06) billboard
@sprite_node Warpglowspritegold6 flare_glow_soft const (6,6) (0.10,0.075,0.025) billboard

@sprite_node Warpglowspriteblue9 flare_glow_soft const (9,9) (0.06,0.06,0.12) billboard
@sprite_node Warpglowspriteblue9A flare_glow_soft const (9,9) (0.0,0.0675,0.12) billboard
@sprite_node Warpglowspriteblue9B flare_glow_soft const (9,9) (0.0,0.09,0.12) billboard
@sprite_node Warpglowspriteblue9C flare_glow_soft const (9,9) (0.0,0.045,0.06) billboard
@sprite_node Warpglowspritered9 flare_glow_soft const (9,9) (0.12,0.0,0.0) billboard
@sprite_node Warpglowspritered9A flare_glow_soft const (9,9) (0.12,0.04,0.0075) billboard
@sprite_node Warpglowspritered9B flare_glow_soft const (9,9) (0.12,0.015,0.015) billboard
@sprite_node Warpglowspritegreen9 flare_glow_soft const (9,9) (0.0,0.14,0.0) billboard
@sprite_node Warpglowspritegreen9A flare_glow_soft const (9,9) (0.03,0.12,0.06) billboard
@sprite_node Warpglowspritegreen9B flare_glow_soft const (9,9) (0.375,0.6,0.3) billboard
@sprite_node Warpglowspritegreen9C flare_glow_soft const (9,9) (0.0,0.09,0.0) billboard
@sprite_node Warpglowspriteocher9 flare_glow_soft const (9,9) (0.07,0.10,0.04) billboard
@sprite_node Warpglowspritepink9A flare_glow_soft const (9,9) (0.12,0.075,0.105) billboard
@sprite_node Warpglowspritepurple9A flare_glow_soft const (9,9) (0.045,0.0,0.12) billboard
@sprite_node Warpglowspritewhite9 flare_glow_soft const (9,9) (0.06,0.06,0.06) billboard
@sprite_node Warpglowspritegold9 flare_glow_soft const (9,9) (0.10,0.075,0.025) billboard

@sprite_node Warpglowspriteblue12 flare_glow_soft const (12,12) (0.06,0.06,0.12) billboard
@sprite_node Warpglowspriteblue12A flare_glow_soft const (12,12) (0.0,0.0675,0.12) billboard
@sprite_node Warpglowspriteblue12B flare_glow_soft const (12,12) (0.0,0.09,0.12) billboard
@sprite_node Warpglowspriteblue12C flare_glow_soft const (12,12) (0.0,0.045,0.06) billboard
@sprite_node Warpglowspritered12 flare_glow_soft const (12,12) (0.12,0.0,0.0) billboard
@sprite_node Warpglowspritered12A flare_glow_soft const (12,12) (0.12,0.04,0.0075) billboard
@sprite_node Warpglowspritered12B flare_glow_soft const (12,12) (0.12,0.015,0.015) billboard
@sprite_node Warpglowspritegreen12 flare_glow_soft const (12,12) (0.0,0.14,0.0) billboard
@sprite_node Warpglowspritegreen12A flare_glow_soft const (12,12) (0.03,0.12,0.06) billboard
@sprite_node Warpglowspritegreen12B flare_glow_soft const (12,12) (0.375,0.6,0.3) billboard
@sprite_node Warpglowspritegreen12C flare_glow_soft const (12,12) (0.0,0.09,0.0) billboard
@sprite_node Warpglowspriteocher12 flare_glow_soft const (12,12) (0.07,0.10,0.04) billboard
@sprite_node Warpglowspritepink12A flare_glow_soft const (12,12) (0.12,0.075,0.105) billboard
@sprite_node Warpglowspritepurple12A flare_glow_soft const (12,12) (0.045,0.0,0.12) billboard
@sprite_node Warpglowspritewhite12 flare_glow_soft const (12,12) (0.06,0.06,0.06) billboard
@sprite_node Warpglowspritegold12 flare_glow_soft const (12,12) (0.10,0.075,0.025) billboard

@sprite_node Warpglowspriteblue20A flare_glow_soft const (20,20) (0.0,0.0675,0.12) billboard
@sprite_node Warpglowspritered20A flare_glow_soft const (20,20) (0.12,0.04,0.0075) billboard

@sprite_node Warpglowspriteblue30A flare_glow_soft const (30,30) (0.0,0.0675,0.12) billboard
@sprite_node Warpglowspritered30A flare_glow_soft const (30,30) (0.12,0.04,0.0075) billboard

@sprite_node WarpglowspriteSaber6A flare_glow_soft SaberWarpGlow1 (6,6) (1,1,1) billboard
@sprite_node WarpglowspriteSaber6B flare_glow_soft SaberWarpGlow2 (6,6) (1,1,1) billboard
@sprite_node WarpglowspriteSaber6C flare_glow_soft SaberWarpGlow3 (6,6) (1,1,1) billboard
@sprite_node WarpglowspriteSaber6D flare_glow_soft SaberWarpGlow4 (6,6) (1,1,1) billboard
@sprite_node WarpglowspriteSaber6E flare_glow_soft SaberWarpGlow5 (6,6) (1,1,1) billboard
@sprite_node WarpglowspriteSaber6F flare_glow_soft SaberWarpGlow6 (6,6) (1,1,1) billboard

Muldrf April 25th, 2011 08:35 PM
Re: Joint/Hardpoint Tree Structure Tool
 
Optec did get back to me, but I have one more email off to check on a final question. If it comes back one way it's about done, if not I have to do a little work on the warpsprites.

Here's a look at the current interface. I've changed the interface a bit tonight, the other "Tabs" are now nearly the size of the interface to let you view more data in them, although they are rarely used. It gives a nicer flow I think. It also gives me more room for additional buttons etc if I need them in the future.

I found I have to make the window so it can't be resized. I also forget if I fixed up the Tab Order (as in the order the Tab key will navigate from item to item on the interface).


I am posting the proposed readme as well.

I also didn't note it but, it requires Microsoft .Net Framework 3.0 to be installed to run. Although the tool should be able to be compiled to work with 2.0 I'm forgetting if Vista came with 2.0 preinstalled or if it only came with 3.0.

http://public.bay.livefilestore.com/...ht3.jpg?psid=1

Quote:
Joint/Hardpoint Tool for Legacy & Armada 1/2 by Muldrf

Version: 1.0.0.3a

This new build of the joint tool is for aiding in creation of new joint trees and modification of existing joint trees for use in conjunction with Milkshape for Star Trek Legacy, Star Trek Armada and Star Trek Armada II games.

-----------
Initial Setup:
The tool should work with Xp, Vista 32 and 64bit, and Windows 7 32bit and 64bit. It requires Microsoft .Net Framework 2.x

Just extract the exe file and create a shortcut to it. Copy the msMJTExporter.dll to your Milkshape folder

-----------
Basic Features:
Welcome to the Hierarchy Hardpoint/Joint Tool. It is used to create new or modify existing "Joint" data for use in Milkshape Specfically to aid in the Porting of ships for Star Trek Legacy and the Star Trek Armada games. Originally created for use with Legacy models, I have added support for Star Trek Armada, Armada 2 and Fleet Ops modes. This is used in conjunction with the "Legacy Joint Tool ASCII" Milkshape Exporter. You can start from scratch making a tree using one of the 4 baseline trees, Legacy, Armada, Armada 2 or Fleet Ops. You can import Mesh Group Names from Milkshape with the Legacy ASCII exporter, as well as any existing joint data. The Output txt file that is created by the tool is in Milkshape ASCII Format so that it doesn't require a special "importer".

To import trees into Milkshape from the tool you must first delete any existing Joints from the model (or it won't import the new joints), then use the Milkshape ASCII Importer and select the file. If you have an existing tree you can doublclick on the "h_scene root" (Legacy, Armada2, Fleet Ops) or "h_root" (in Armada 1) to highlight it then press "Delete" on your Keyboard. When importing the data Milkshape may make your textures disappear, when that happens save your file then reopen the saved file and it will refresh your textures.

Interface:
"The Tabs"
Tree View - Shows your overall joint structure. This Tab is the one that is used primarly. You can Drag and Drop joints in the Treeview to other Parent joint "levels", such as drag a joint from the h_hardpoints section to the h_lights section if you misplaced it. This also has most of the joint manipulation buttons on it.

Grid View - This shows the data that the tree view works from, including the other underlying information that is used, such as location and rotation and and joint comments (only used in Legacy). While you can edit some the data in the Gridview it's not generally done. The main thing I use the Grid View for is when porting a model I will verify that the m_ joints are at 0,0,0 and have no rotation at all, if they don't I will manually edit them back to the proper 0,0,0 values.

Output tab - This is a preview of your output file. You could copy and paste the text from here into notepad etc and save the txt file. This view is generated either when pressing the "Pre-Build" button or when pressing Export. The Pre-Build button allows you to generate the output and do some manual adjustment if you like before saving the file. If you do edit the Output text you then must still Export it by using the Export button, just tell it to NOT Flush the Output data when it asks, it only asks that if the output window isn't empty.

"The Buttons"
Tree View Buttons:
Up - move the selected joint "up" on the list at it's current Hiearchy level, this will move it to the top of it's current level but not into the next higher level.
Down - same as "up" but moves the currently selected joint "down".
Move Checked - will move every joint that has the checkbox checked to be attached to the currently selected joint. There are some situations where this will have to be pressed more than once to get them all moved. I just haven't tracked them all down yet.
Rename - Shows a box where you can edit the name of the currently selected joint. You can rename a joint fully if it's currently a h_ joint you can rename it to something totally different such as a s_ joint.
Pattern Color - This button is only for Legacy it lets you edit the Pattern and or Color/Intensity values of a Light Sprite, it is disabled in the Armada modes of the tool.
Delete - Deletes the currently selected joint, be sure to delete any "child" joints first, I never intended to delete joints using that button that had "child" joints under it.

Right Side Buttons:
Clear Tree - Clears the tree back to the Default tree for the currently Selected Mode.
Import - Imports joint data from a "Legacy Joint Tool ASCII" format file, including model group names, and all joint data including joint name, parent joint, position, rotation and comment data.
Pre-Build - as mentioned above this populates the current data on the tree and grid views to the Output window in the Milkshape 3d ASCII format. Useful if you want to do some additional tweaking before saving the output file. I have very rarely used this, but left it enabled "just incase".
Export - This will check if the Output tab is populated and if it is ask if you want to repopulate it and clear the changes or use the current data there, if the output window is empty at the time it will populate it automatically. This then saves to output text to a Milkshape 3d ASCII format file that can be imported into Milkshape.
Help - Displays the Help menu.
Exit - Closes the program.

"The Other Stuff"
h_ Section. This is for creation of h_ type joints at the currently selected joint on the treeview. Either hierarchy or harpoint joints. It also allows automatic creation of an additional joint that will be placed in a specific direction from the joint. You can also add more than 1 at a time by using hte Quanity box, when using that box the Increment function will tag on a ## suffix such as if you place "hp" in the name field and Quanity of 3 you will get h_hp01, h_hp02 and h_hp03.

s_ Section. This section is for creation of s_ type joints at the currently selected joint on the treeview. It also has the Quanity and Increment function except it places a _## suffix suc has whitestrobe and qty of 2 would give s_whitestrobe_01 s_whitestrobe_02. The Pattern and Color data is only for Legacy, it allows making custom blink patterns and colored lights without having to add new spr file entries, you can actually make a blue strobe into a pink constant light if you care to.. Again the Pattern and Color boxes are disabled in the Armada modes.

m_ Section. This section is for creation of m_ type joints at the currently selected joint on the treeview. These are Model Group joint names, they are used to tell the exporter to export the model group sections to the sod (Aramda1/2) or m3d (Legacy). If you use the Legacy Joint Tool ASCII exporter in milkshape you can import the Mesh Group names directly from Milkshape, otherwise you can manually type them into the box and add them. The "Add" will add a joint with the name that is in the box at the time. The "Add All" button will add every group name to the currently selected joint, this is helpful in Legacy where you could have a large number of mesh group names.

e_ Section. This seciton is for the creattion of e_ type joints attached to the currently selected joint on the treeview. These are generally used when a ship takes damage. For Legacy only the plasmamed and plasmalrg emitters actually work. For Armada games you can apparently use all the plasma and the steam type emitters. For Armada you can have Incremented names as well like the s_ joints with a suffix of _##. For Legacy you can NOT use the Increment function, I'm hoping to get the Leagacy exported updated to allows incremented emitter joints to work, or I would have disabled the function in Legacy mode.

Custom Named Joint (no Prefix) Section. This is for adding a joint of any name. Unlike the other sections this is a litteral name, as in if you put in "Bob" it will place the joint of "Bob" on the tree without any prefix or sufix. This is incase you need some oddly named joint. I have not had to use this so far, but I figured it was a good thing to have "just incase".

List of Joints Box. This box basically shows all the joints you have on your tree currently in a running list.

Mode Box. This box is to allow you to switch between the various modes of the tool. When you switch the mode it will wipe out your current tree in favor of the base tree of that mode. The various modes have different s_ joint list to work with. Also the Armada modes don't support the Pattern and Color function on the s_ joints so those interface parts are disabled when in those modes.

-----------
Revision History:

Changes From Version 1.0.0.2a to 1.0.0.3a
1. Removed "crew#" joints from the initial tree. If you want to add them just do so from the s_ joint type.
2. Fleet Ops added the numerous "warpglowsprites" to the s_ joint type dropdown. Removed the crew# and sensor joint from the Fleet Ops tree as it seems they don't ever use them.
3. Added info to the Help window on the various interface bits and some basic usage info.
4. Can now add Mesh Group (And "Custom Named Joint(no Prefix)") names that are "unique" by "Capitalization" such as "m_R_logo" will no longer cause a duplicate if "m_r_logo" already exists. This is due to Legacy uses r_logo, R_logo, l_logo and L_logo as logo mesh names.
5. "Base Tree" joints now populate to the List of Joints box.
6. Selected Joint on Treeview now remains visibly selected when it looses focus.
7. The Root (first top level item on the Treeview) is now selected automatically on Startup or Clearing the tree to prevent errors when trying to add joints before selecting any initial joint.
8. Fix Loop if you answer "No" to the Auto Increment question when a duplicate joint name is found to be on the tree.

Changes From Version 1.0.0.1a to 1.0.0.2a
1. When changing the "Mode" box it will now ask if you want to switch modes or not. If you say yes it will preform a Clear Tree function to flush out the old modes tree. If you say no then it reverts back to the previous setting

Changes From Version 1.0.0.0a to 1.0.0.1a
1. Fixed "Increment" function for when duplicate joints are found for s_, e_, and h_ joints.
2. Added Crew1-Crew5, Crew16 and Sensor as options on the s_ joint list for the Armada games. These are fixed name joints, I don't know if they work with sufixes like _01 tagged to them.
3. The tool now saves the last used mode. So if you exit with it set to Armada it will reopen in Armada mode etc.
4. Added the Change Log that your reading.
5. Added file format check incase an improper file is selected for import. The "Legacy Joint Tool ASCII" that the tool imports is NOT the same as the "Milkshape 3D ASCII" file that it exports to.

-----------
Permissions / Notices:

This tool can be use to assist in modding Star Trek Legacy, Armada, Armada 2 etc.

This tool and these files are not supported by Maddoc or Bethesda Softworks Activision etc and they are not responsible for any damages to your game directory. As with all modtools you are using them at your own risk. The end user of the tool accepts responsibility for usage of the tools.

The Tool can not be distributed with any other package without obtaining permissions from myself (Muldrf).

The Tool exe must not be distributed without this readme.

-----------
Credits / Contact:


If problems are found with the tool you can contact me and I'll see what I can do to help. Also if you have feature requests let me know.

The Tool is coded by Muldrf

markenobrookstone AT hotmail DOT com

Your Daily Gamepad - Chris Jones Gaming - Index

I also follow the Filefront forums for Legacy.

Again anyone wanting to try the beta can send me a Personal Message and I will send the link. The link I previously gave out will not work any longer.

Muldrf April 29th, 2011 07:25 AM
Re: Joint/Hardpoint Tree Structure Tool
 
The Finalized version submitted for approval. v1.0.0.5

Starfox if you want it now, you can grab the 1005 from the same link as the last file at any time. Operationally it's the same as 1004 that you downloaded the other day. It has some layout and tab navigational changes though, that I think help it flow better. If you don't use "tab" to navigate around the interface you won't notice much change though.

http://myipdq.bay.livefilestore.com/...t15.jpg?psid=1

starfox1701 April 29th, 2011 07:54 AM
Re: Joint/Hardpoint Tree Structure Tool
 
I'm On my Way :D

Muldrf April 29th, 2011 02:18 PM
Re: Joint/Hardpoint Tree Structure Tool
 
Have fun with it Starfox.

My wording wasn't as "clear" as intended. It might be misread, I meant to say "I have submitted the file to Armada files for approval". I'm not sure how fast or slow it is for the files to be processed.

Terra_Inc April 29th, 2011 04:02 PM
Re: Joint/Hardpoint Tree Structure Tool
 
Quote:
Originally Posted by Muldrf (Post 5498735)
Have fun with it Starfox.

My wording wasn't as "clear" as intended. It might be misread, I meant to say "I have submitted the file to Armada files for approval". I'm not sure how fast or slow it is for the files to be processed.
With the screenshots broken, it may take some time. Depends on BreakIT now. :uhoh:

Muldrf April 29th, 2011 06:06 PM
Re: Joint/Hardpoint Tree Structure Tool
 
Well POtDs have started working tonight it seems, that mean the file images are fixed as well? I see "previous" stuff hasn't had the images show up on the file, but thinking maybe anything "newly" posted will be in order?

Majestic-MSFC April 30th, 2011 06:12 AM
Re: Joint/Hardpoint Tree Structure Tool
 
I just download the tool from A2Files, took a bit to get working, but it looks great I have made a HP template for my Fleet Ops models, but haven't tested it in-game yet as I have no models ready for in-game use.

One addition I would ask is a save option, where you can save the tree that can be re-opened in the program, perhaps having it be able to load in the format it exports. But this is a great tool and will really help many modellers out as hardpoint is a real pain but having a complete map with every possible joint needed will really save time for many. :)

StarBlade April 30th, 2011 06:56 AM
Re: Joint/Hardpoint Tree Structure Tool
 
Quote:
Originally Posted by Muldrf (Post 5498859)
Well POtDs have started working tonight it seems, that mean the file images are fixed as well? I see "previous" stuff hasn't had the images show up on the file, but thinking maybe anything "newly" posted will be in order?
We honestly have no idea. As Terra said, it's up to the Break IT guys now. The file may or may not work, and/or be available for download, and/or have its associated images showing, at any given moment. They're in the process of rebuilding the entire server side of the main site (not the forums) from scratch, and there is no easy way to do that.

Just for the record, for everyone, this is not intended as an invitation to public discussion of A2Files', and FileFront's, issues, so please don't offer me suggestions or well-intentioned criticisms. I have neither the means nor the intention of acting on them, or even passing them on.

That being said, this looks like it'll become an essential tool for modders, and it represents a very positive development for the A2Files modding community. Thanks for the hard work, Muldrf.


All times are GMT -7.
Page 5 of 7 « First 34 5 67
Show 50 post(s) from this thread on one page

Powered by vBulletin®
Copyright ©2000 - 2016, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.