Terrain and preferably all other objects...

I tried setting the AEmitter to GetsHitByMOs = 0 and HitsMOs = 0, but neither of those affected it. After that, i tried omitting the lines entirely, with still no results. The AEmitter (in my case, a rocket that gibs from another rocket) exploded upon hitting anything.

I'm of the impression that this is possible (see the Nail Pistol magazine; it falls through terrain), I'm just not sure how.

Anyone know how to do this?

I haven't been here for long, but I'd guess that maybe if you set the HitsMOs and GetsHitByMOs to 0, the sharpness to a very very high number, and then remove the GibImpulseLimit variable, you may end up with an emitter that passes through everything, doesn't do damage to anything and does not get destroyed.

Then again, I could be entirely wrong.

Those two variables apply only to MOs, IE, Actors, Weapons, DropShips, etc.
To phase through terrain you need to have a null Atom Group, or an obscenely high mass (though the latter will destroy terrain as it goes).

I think if you manually (as is done with feet) make a atomgroup (and/or deepgroup) with no atoms, an object can pass through terrain. I'm not certain about that, but I know it's doable in some way though.

try autogenerate = 0

can't remember if that works

Give the AEmitter a sprite, and make the atomgroup and deepgroup resolutions greater than the sprites X & Y values, it won't matter if it's hits MOS or not, the collision detection will only trigger for areas outside of the sprite where it can't collide. if that doesn't work, just double the values.

Remember resolution = 1 = every pixel,
2 = every other pixel
4 is every 1/4th, etc.

the only problem with this is, it won't collide with anything, however you can use lua to do collision detection for MOS and stuff, so it doesn't really matter.

--edit
this was happening to me on accident a while ago.... although when I really think about it... it might have been 1 build ago, I don't know if it still works... >_>


--Re-edit
Open mouth, insert foot

I was 100% wrong on this, I am sorry, I just tested it 5x5 pixel sprite, 100 resolution. DID NOT WORK.

I think it has something to do with AEmitters acting weird, I know that's how it works for the MOS, so it only made sense. maybe make it an MOS with an attached AEmitter? thats all I can think of at this point.

if autogenerate doesn't work try a high depth

one of them should I think

isn't autogenerate for when things settle?

uh, no

autogenerate is whether or not the game automatically generates (geddit) an atomgroup, or whether it should use one defined in elsewhere.

Mmk... null atomgroup... right... uhh...

How would I do that? O_o

Also, I tried setting the depth of the atomgroups to 99999999. Didn't work.

This is a blank atomgroup, not sure if that's the same thing...

Hey.

Resolution = 9999999

Thats how the cool kids do it.

*the kids who use dumb arbitrary unnecessary variable settings that promote instability and are generally ♥♥♥♥

And it doesn't work anyway.

It does work, you did something wrong.
Resolution controls how widely the pixels of collision on the object are spread.
If the value is very high, the collision is very sloppy and wont take place and thus the object phases through terrain.