NeMeSiS

No, then it could more easily handle the physics interactions of the particles (for example: smoke being blown against and along a wall by wind, instead of going through). But the slowdown is caused by drawing the particles, not by their physics interactions (which i think are nonexistent for the gunsmoke anyway), and cannot be improved by physX.

They should take the AI out to a proper date. :)

While i am fine with the current situation the 'like coloring/opacity of the current stance figure' sounds like a very elegant solution, so i voted for that.

Only if it is realistic that they die instantly, otherwise a bit of a falling animation that transitions onto ragdolls makes more sense. Luckily we usually dont spend our time shooting guys in the default idle animation, so it looks a bit more natural during regular gameplay. :)

It has been changed since OFP. Thats why ArmA3 is not an exact replica of OFP with just the models/islands replaced. :rolleyes:

Aren't we allowed to ask for donations already? I don't think anyone is stopping you from putting a link to your paypal, amazon wishlist or dogecoin wallet in your signature. It is something i am very much in favor of. There are a lot of people who i would like to buy a beer to thank them for their work, and donations are an easy and opt-inish way to solve this. It is not really an incentive to start modding since you are not selling anything, but it is an easy way to thank people for their work and show appreciation.

Some of us prefer it this way. :rolleyes:

Try without SLI, and or check if your GPUs arent already at full capacity.

I am pretty sure that most games use some generic shader/texture layer for most, if not all, objects and terrain.

Are these myths? Ive rarely, if ever, seen anyone arguing most of these.

While i think that this thread is completely useless besides containing the anger of a bunch of people who would disrupt the forums otherwise' date=' i do think that you are being a bit overzealous in defending ArmA3's performance. ArmA3 runs acceptable, at best. Considering the amount of CPU usage* there is definitely [i']room[/i] to increase the performance of ArmA3. Most people clearly do not understand the difficulties of multithreaded programming, hence a significant amount of whining, but still, if BI was prepared to throw a bunch of money and (mostly) time at it, they could do something about it. But clearly, it has been decided that it isn't worth the investment, and everyone in this topic is wasting their time staring at FPS counters and hoping for some kind of magic patch that will never come. Either turn off you FPS counter** and live with it or stop playing altogether, it will never be much better than it is at the moment and everyone here is wasting their own, and Myke's time. The closest game we can compare it to is ArmA2. Besides PhysX i cant think of any new feature that would eat CPU time. Did we sacrifice (roughly) a third of our performance for some shittily implemented physics that cant be turned off? This is not a defensible position. *Anyone talking about GPU usage/perfomance/whatever either has a weirdly balanced PC, or no idea what he is talking about. **Doubles the subjective feeling of FPS after 30 minutes, guaranteed.

What if the samurai has a horse?

So, halfway the article there is this image viewer with 125 pictures. Pics 48 - 52, screenshots of the lost OFP:Vietnam idea? Everything else seems to be Game2 assets/screenshots.

Congratulations, you succeeded. ;)

It works somewhat okayish when i hold fire and move every unit individually. Unfortunately that does not work at all in practice, since noone has time to micromanage every unit when they are trying to move units in combat. Unrelated sidenote: When was the 'hold fire' command changed to make units actually hold fire, even when they are being shot at? I much prefer the old implementation where they would start shooting once detected, even though half the community did not understood that is how it worked.

Well, i just decided to make my problem clear by polluting youtube with another badly edited ArmA AI video. :) Note: @TPW_MODS was running while recording. I tested it afterwards without any addons and it made no difference, but i couldnt be bothered to record again. EDIT: Video will be up in a few minutes.

Maybe if there are no enemies in sight, but i just tried it, and as long as they have a unit in direct LOS they will pretty much stay where they are until the fight is over, or they are dead.

True, but my point was that removing auto combat mode would not solve anything, and create a bunch of problems on its own. The default behavior is currently quite fine, but a "stop auto behavior and do what I told you" command is what should be added. Currently retreating is impossible, and every time it is needed I just abandon my squad, no point in trying to save them at the moment. On the other hand: I do like it that medics don't run to you when you are wounded in the middle of a field and under fire, trying to help you in such a moment would be a retarded decision anyway, so I do think ai autonomy overriding orders has it's place.

Units automatically switched to combat mode since OFP.

Why would you have to rewrite it? Sqs still works fine. It is supposedly a bit slower, but nothing disastrous. If needed just rewrite the most used parts.

I dont really see why you would need to use the arrow keys if you are a lefty. If your desk is small WASD may be a bit cramped, but it wouldnt be all that hard to change it too IJKL and surrounding keys. I have played with left and just used the default WASD setup, though rarely (usually play with right).

AFAIK you only use l' when the first letter of the next word is pronounced with a vowel. So a, e, etc, but often also H in french (considering you do not pronounce the H in words like 'hotel' in French). The G in Garcons doenst start with a vowel like sound, so it wouldnt have l'.

It seems like Scott Miller is going to build himself a new superweapon. :p

Ah yes, just like bigfoot in ArmA2.

Lets say i am trying to draw a line from point a to point b (x,y and z coordinates). This point will intersect an object at some point, and there are commands that will tell me if and what it intersects with. However, i am trying the find the position where this intersection takes place. It does not have to be perfectly precise(<0.2m would be my guesstimate). I figured there are 2 solutions: 1) Try the lineIntersects command along the line. However, i cant get my head around the required maths, and do not know to to calculate the required positions i would need to try. 2) Spawn a bullet that will never deflect, has no tracer, does no damage and will not fall down due to gravity, and just keep tracking it until it hits something, the reported position would be close enough. However, this requires me to config such a bullet (not sure how to do that, but should be possible with a couple of days trying and crying :p ), then shooting it along the line. However, i do not know how to find the angle between point a and b, or how to shoot the bullet at that angle. Anyone has any idea how to handle this? :)