uh, mine for some reason doesn't do that; is that I need to open up a particle file, or create a new one to work with?

There already is a test version for entrenchment. It is possible to get, but since damnan hasn't made any links to it himself, I won't either. Besides that i couldn't get it to work with entrenchment so there is possible still quite some testing.

Hey, I can't get a mod to work; I get a minidump every time I try.  I may be missing something in the reference data.  What folders/files do you need in a mod for 1.17?

It's just a little mod I came up with myself.  It triples the capaxity of the Hangar defenses and quadruples the firepower of the orbital turrets.

Is it possible to add in new armor classes?  As in, currently we have: vl, l, m, h, vh, and cap.  Is it possible to do without yielding a minidump?

What's the debug?

EDIT: I got the developer's .exe and I put it in the same folder as the sins .exe, but every time I load I get a message saying I'm missing this: GalaxySetup.window

anyone who's still monitoring this thread, please pay attention!

Several things-

1. akkan117, I figured out Particle Forge. Turns out I hadn't RIGHT-CLICKED the emitter button, to create a new emitter. After that, it was just following the instructions.

2.  okay, so I'm making a mod called 'Vasari Supremacy'. I've scripted out most of the new ships, abilities, edited the strings files and manifest files.

The problem I'm having has to do with the models/textures. For my new ships, I'm using resized cap ship models (they're smaller). I used the mesh resize tool. I am using the developer executable of Entrenchment (v1.03 build) to debug the mod.

This was my first problem that I couldn't figure out at first (brackets are added to prevent confusion of question text):

[Assert @ c:\gs\entrenchment\CodeSource\Engine/DataStructures/DynamicVector.h(172)

i >= 0]

I think it has to do with the textures being improperly done. This is because when I took the resized Marauder mesh, then resized the 3 textures that go with it using GIMP (v2.6.6), renamed all three textures (the mesh is already renamed), this problem didn't pop up anymore. If you could tell me exactly what this means, that would be helpful.

These three complaints also kept popping up several times:

[Assert @ c:\gs\entrenchment\CodeSource\Engine/Render/Texture/FileTexture.cpp(260)

srcLevelCount == dstLevelCount]

[Assert @ c:\gs\entrenchment\CodeSource\Engine/Render/Texture/FileTexture.cpp(280)

dstSurface != 0]

[Assert @ c:\gs\entrenchment\CodeSource\Engine/DataStructures/List.h(431)

i != End()] (<- the parentheses here are part of the complaint of the dev.exe)

The first two I gather are texture-related. I also suspect the third is as well. Once again, if you could tell me what they mean (and how to fix them), that would be most helpful.

This one popped up once, and I think that it's also related to the textures, but I've no idea why.

[Assert @ c:\gs\entrenchment\CodeSource\Engine/Render/Texture/FileTexture.cpp(268)

DirectXAssert: [!FAILED(dxVerifyHR)]
Context: d3dTexture->GetSurfaceLevel(i, &dstSurface)
HR: (D3DERR_INVALIDCALL)-Invalid call] (<- once again, parentheses are part of the complaint)

Note that the pair of brackets- [!FAILED(dxVerifyHR)] are part of the complaint. Once again, actually being informed what this means and how to fix it would be nice.

3. If you guys could tell me how to create a shieldmesh for a custom ship (as in a new race's ships), that would be awesome. I ask because at this time I have NO IDEA how to do this, and I really want to know so I can.

Thanks 7DS team.

you'll need to add nulls to the model file (turn it into a txted version, the shipped versions are all binary) so that the effects are seen.

Otherwise, that's pretty correct. Changing a weapon is as easy as changing it's type (it's the 'weaponType' line). For changing what it looks like, you'll need to open up a ship file that has the weapon you want for the ship your changing, copy+paste the weapon data, like damageEnums, effects data, and damage profiles.

Note that only Starbases can have multiple attack types, so you'll need to make sure the 'COMPOSITE' attack type on the Kodiak is set up for all the weapons on it.

Also, each ship/structure/starbase can have only THREE TYPES OF WEAPONS. That's the 'numWeapons' line. It can go no higher than three. However, you CAN put two (or three, your choice) weapon types as the same (the Vasari Space Egg (Jarrasul Evacuator) does this).

a null point is a point assigned to the mesh. You need these because they determine where the particle effects (weapons fire, exhaust) comes from.

yes. All you need to do is script it, specify the mesh information, and the shieldmesh info.

Also, make sure that the model is compatible with the Sins version (1.17 vanilla/1.03 Entrenchment) your using.

Under the beam color.  The core is generally white (although you could change it) but the outside is your faction color.  I mean, you could make it so that the core of the beam was black and the outside was red, or it could be rainbowy, but generally its just white to your color to darker version of your color.  You need to change the outside color of the beam.

you don't want 7.5. It's a free trial.

You want the 6.01 Mod Too. It's free.

Go through the tutorials for the Mod Tool, that will kick-start you in XSI.

Hello all quick question has anyone ever encountered this error before? and if so know anything about it .