Arma Tactics takes the best from the popular strategy genre... and goes mobile. The finest assets used in the critically acclaimed Armaâ„¢ series on PC now come to life on the Android mobile platform, in one of the best looking mobile games to date.
Take On Mars places you in the seat of a Rover Operator, allowing you to control the various, fully simulated mobile Rovers and stationary Landers. With this scientific arsenal at your disposal, you will work your way through the numerous Science Missions in each location, unlocking the secrets of Mars' distant past.
For discussions not strictly related to our games. Topics should ideally still be related in some way, for example: military, politics, science. Note that just because this is for offtopic it's not a case of "anything goes", silly topics and especially topics which don't have any scope for discussion will be closed/deleted.
So after using allowDamage on created units, it seems to be causing some issues where it stops working. So basically I create a unit with createUnit, call 'allowDamage false' on it and then put them inside the vehicle. They seem to occasionally lose their 'god mode' when they get into vehicles. Is this to do with locality? If so, would I just need to re-execute it on wherever the unit is local to? I read into unit locality and couldn't find much that states how their locality changes etc so I'm not 100% sure. Thanks in advance.
As the title says. Two fixes or changes for arma 3. if you had the say on to get priority on a fix. It might be wise to be realistic.
I'll get the ball rolling in no particular order.
The flickering lods. (big impact on the visual aspect of arma. But also affecting gameplay immersion).
The memory leak. Speaks for itself. While I don't get it nearly as often as some. I understand the frustration of those that do.(Was tempted to say Ai. But I have a feeling although not perfect far from. when wild lands drops, some appreciation for armas might shine).
I've taken a look at the unbinarized rail in CUPS. The underlying problem is that the "View Geometry" LODs for most of the rails are missing or only cover the metal rails. Ideally, I need the view geometry to cover the entire track (e.g. a simple box around the track). Without the View Geometry LOD, it appears non of the lineIntersect* methods work. Looking into how to open a request with the CUPS team. Maybe it's something that can be fixed.
If that can be fixed, that would be great. Otherwise, I have a work around using findNearestObjects / findNearestTerrianObjects that might work.