[]Does this option only work for collisions in layer 1? I don't understand how there is a difference among layers. [/]
No, this option works for all the layers. Collisions in layer 1 are handled differently for compatibility reasons with previous versions of MMF1, as with the Paste into Background action you can make "holes" in the collision mask, a thing you can't do with the other layers.
Yves.
[]Does this option only work for collisions in layer 1? I don't understand how there is a difference among layers. [/]
No, this option works for all the layers. Collisions in layer 1 are handled differently for compatibility reasons with previous versions of MMF1, as with the Paste into Background action you can make "holes" in the collision mask, a thing you can't do with the other layers.
Yves.
Also TDA ((( 300,000 ))) not 30,000 or 3,000. You set part of your frame size to three >hundred thousand<
Also TDA ((( 300,000 ))) not 30,000 or 3,000. You set part of your frame size to three >hundred thousand<
Hey Just ran it on my "Cray 2006" works fine here whats the problem! Did have a little problem from the administrator wondering what I was doing sending all those zeros to the Rad array. <img src="/center/images/graemlins/smile.gif" alt="" />
Strange though used a bit of memory 585 Billion bits of ram, Still, or 406TBit of Swap space does take even a Cray a few minutes to calculate.
Some advice, seriously before you make these enormous playfield, think about the ram requirements.
Your better to store the object in a virtual array and then do some calculations to estimate where you are on the playfield.
Hey Just ran it on my "Cray 2006" works fine here whats the problem! Did have a little problem from the administrator wondering what I was doing sending all those zeros to the Rad array. <img src="/center/images/graemlins/smile.gif" alt="" />
Strange though used a bit of memory 585 Billion bits of ram, Still, or 406TBit of Swap space does take even a Cray a few minutes to calculate.
Some advice, seriously before you make these enormous playfield, think about the ram requirements.
Your better to store the object in a virtual array and then do some calculations to estimate where you are on the playfield.
fyi - I never intended on making the field so large, I did that by accident. (I was wrestling with a different issue at the time)
Thanks for your help with this. <img src="/center/images/graemlins/smile.gif" alt="" />
fyi - I never intended on making the field so large, I did that by accident. (I was wrestling with a different issue at the time)
Thanks for your help with this. <img src="/center/images/graemlins/smile.gif" alt="" />
Posting Permissions
Reply With Quote