Lauren

The problem is probably the projectile dying before impact. Try using a special power nugget that uses a special power with target type set to location to fire the actual weapon. That way the attack shouldn't be targeting the object but the ground beneath it (no homing missle that way). Also maybe giving the first projectile a warhead with just ReportWeaponFiredStatNugget might also be part of the solution.

tsins is a funny name for the directory. tiberium sins? ;D (yeah yeah ts installer, but hey where's the fun there?)

MSI Z170A Gaming M5 Intel i7 6700K (4GHz) Corsair Vengeance LPX 2x8 GB DDR4 3000MHz RAM Gigabyte GeForce GTX 980 Waterforce

Your pc will be the biggest hurdle, it has to encode in software mode or not at all which costs a lot of CPU power or a fast HDD which you do not have. Even for Generals 30fps will probably not be possible.

"[...]by male bodies (my frontal lobe won't allow it)" way to loose all respect, end of story.

○

Btw that's also the reason in the manual it says that you shouldn't look at the max vertex/poly count as sometimes in optimizing the strips it's easier to duplicate vertices so that it doesn't have to jump as much. Finding the right strips increases render speed by about 20% And well I studied that stuff, at least until I fluked it because of depression.

A few things to note: 1. it's w3D not w3X. 2. The author is still baffled about animations. Also for an exporter: it's not just enough to dump the data, that would be easy. Finding optimal triangle strips is important, as it increases final render speed (if this step isn't taken the graphics card has to go back and forth through the vertex array a lot more).

No, you don't skip time. Maybe your tech is insufficient to pick up enough intervals, but that's a different matter. Btw time dilation is already noticeable on commercial airplanes. https://en.wikipedia.org/wiki/Hafele–Keating_experiment

I can agree with a lot of what you've written but it's about the transfer of what you've learned already to be able to infer new solutions, which I just don't see. With just copying you seemingly never answer the question for yourself "why does this setting do what it does". For xml itself: there are thousands of resources out there which explain it very well. xml itself is really simple, it's just a human readable representation of settings, either via simple attributes or simple to more complex elements. Just sit back for a bit for a few of your files and look at them. Go through them and for each attribute just by its name think about what it probably does. They are very well named usually or the context is usually enough to infer what they do. That is basically all what xml is about. And for possible values check the xsd (which is just xml defining another xml structure) for TW, or the definitions for WrathEd (also basically the same as xsd, just slightly different as I am not legally able to provide the xsd for WrathEd). Yes going through all that stuff takes a long time, but it is necessary to be able to see what's possible. There are quite some logical combinations of behaviors for example to create an expected result. Yes some don't work anymore as the devs just hadn't had the time to fix them, but that's just trial and error (where you can also ask if you're running into a problem where certain settings run into unexpected behavior).

Please at some point do what I tell people over and over: Start to learn how to really understand stuff, not just copy/paste from others.

'tis a secret, sorry. If we would post it here people would copy it immediately.

What? That's completely not what I've said (again). The locomotor takes seconds, not dist/s^2.

It shouldn't even have worked if the module was working correctly, and why 17 seconds, that's an odd number to choose.

Do you even read the stuff you link/quote?

Bored update wouldn't have helped in this situation as a second object is needed for it to work.

Well it is slowing the object down. If the locomotor has a slow acceleration it will take time to speed up again after crushing.

The problem is usually between the chair and the monitor. And someone can say they set something up correctly and still having it totally borked just because they don't know better. And "updating the plugin"? Why does no one of his team do that? They seem to have the money to buy *coughcough* newer versions so they might just have or hire someone with knowledge.

Yes raven is correct. It was originally introduced in BFME as horses wouldn't be able to stomp over hundreds of infantry without them being slowed down. This in connection that you can set a minimum speed for crushing just makes stuff more realistic (horses can't easily trample someone in mass armor without having some speed to begin with, esp against pikemen... good thing they don't also have double-strike and lifelink).

max9 runs gud on even w10 x64. You just need to know what to do and how to configure it.

As written in the shoutbox: For TW use the command line switches -win -fullscreen combined with -xres -yres (each followed by the resolution you want) and -xpos -ypos (both followed by 0) That gives you a borderless window at the top left corner with the desired resolution for example -win -fullscreen -xres 1920 -yres 1080 -xpos 0 -ypos 0 -win also works in Generals, dunno about the others. You also don't need a sizer, just tell it to use the game window. (I use the same program to record ingame stuff) Btw as source, don't use window capture but game capture.

No xml is special, the options are very limited so as long as you know what you want it's usually very easy to achieve or to determine it to be impossible with the given toolset. Coming up with the idea of what you want to create is what it's about.

No vector involved here. Also 4x4 black texture will do just nicely (as it's black anyway and you don't need pixel precise information, with 4x4 being the minimum resolution).

Disregard that error. It happens always, you just didn't notice.