For a quick & dirty fix (currently working for me), open \X4 Foundations\extensions\hound\assets\units\size_l\hound.xml in a text editor (Notepad++ recommended). Bring up a find/replace window for easy searching, and search for something simple, like "eng" for engines, then note that, starting midway through each line, there is a section that looks sort of like: tags="engine large "> If you change the engine lines in hound.xml to end with: tags="engine large standard "> it should allow hound engines to install correctly in ver 6.0 (tested with hotfix 4). Tags are the keywords that tell the game engine what can be attached to the ship. Ver 6.0 added the tag "standard" to engines and shields, so editing the tags for those attachments in the ships' xml files to include the "standard" tag is a hard requirement to make them configurable in a shipyard (at least using Egosoft vanilla parts). Weapons and turrets that use guns (as opposed to just missiles) need "combat" added to the "tags" section of each weapon or turret entry in every stupid ship (and yes, hound needs all 4 of these). Any ships not updated for 6.0 by their authors will need this fixed, at minimum. If you run into one whose mod files are packed into a .cat file, you'll need to use the "XRCatTool to unpack all its files, then edit the ship xml, and then either repack all the extracted files or just delete the leftover cat files. It's a huge pain in the rear, but editing the xmls is easy with notepad++, since you can click "replace all" once you get comfortable with the tags required. As awful as that is, it's nothing like what most modders have to do to ensure complete compatibility with the new physics engine. Any ship modders who haven't given up on X4 probably deserve a coffee at minimum, if you can afford it. I don't make mods of any consequence. I just noticed the differences between some ship mods that worked in my updated game and the dozens that didn't. Hope this helps somebody.
**Edited for grammar and legibility after a quick proofread. Also please note that xml syntax and proper English are not compatible, so for direct editing instructions, follow the example above on my 3rd and 4th lines, and don't put an extra "quotation" mark around each new tag.
**Also added an unsubtle plug for literacy: If you thought this was a long, complicated post, I dare you to find a similar youtube tutorial that takes less than 40mins to watch (or one that clocks in at the less than 5kb of data you've been slogging through so far). If you made it through all that, you should probably start a zen garden or something. Props to you.
This ship is an A+ and is a major patrol part of my fleet. I was able to add additional rooms using the More Rooms Mod. This is really one of my favorite ships because you can look at the forward docks from the bridge of the ship. There is a minor texture issue in the rare dock. Please see screen print link: Minor texture issue.
Suggestion: Could you make it so the appropriate faction build this ship for their own use too (just like the XR ship pack does)? It would be great to see them flying around in thie Hound.
im working on a big overhaul of all my ships. sorting them by faction is part of that. but i cant promise what it will release. new issues and new things to do keep popping up.
20 comments
If you change the engine lines in hound.xml to end with: tags="engine large standard ">
it should allow hound engines to install correctly in ver 6.0 (tested with hotfix 4).
Tags are the keywords that tell the game engine what can be attached to the ship. Ver 6.0 added the tag "standard" to engines and shields, so editing the tags for those attachments in the ships' xml files to include the "standard" tag is a hard requirement to make them configurable in a shipyard (at least using Egosoft vanilla parts). Weapons and turrets that use guns (as opposed to just missiles) need "combat" added to the "tags" section of each weapon or turret entry in every stupid ship (and yes, hound needs all 4 of these). Any ships not updated for 6.0 by their authors will need this fixed, at minimum. If you run into one whose mod files are packed into a .cat file, you'll need to use the "XRCatTool to unpack all its files, then edit the ship xml, and then either repack all the extracted files or just delete the leftover cat files. It's a huge pain in the rear, but editing the xmls is easy with notepad++, since you can click "replace all" once you get comfortable with the tags required. As awful as that is, it's nothing like what most modders have to do to ensure complete compatibility with the new physics engine. Any ship modders who haven't given up on X4 probably deserve a coffee at minimum, if you can afford it.
I don't make mods of any consequence. I just noticed the differences between some ship mods that worked in my updated game and the dozens that didn't. Hope this helps somebody.
**Edited for grammar and legibility after a quick proofread. Also please note that xml syntax and proper English are not compatible, so for direct editing instructions, follow the example above on my 3rd and 4th lines, and don't put an extra
"quotation" mark around each new tag.
**Also added an unsubtle plug for literacy: If you thought this was a long, complicated post, I dare you to find a similar youtube tutorial that takes less than 40mins to watch (or one that clocks in at the less than 5kb of data you've been slogging through so far). If you made it through all that, you should probably start a zen garden or something. Props to you.
no engines, engine slot is a weapon
win 8 , doc path , steam Version 3.2 SV