Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass closing resolved issues not updated since November.

Mass closing resolved tickets from last month.

Mass-closing resolved issues not updated in 10 days.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass closing resolved tickets from last month.

Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Does this work now?

Dupe of #11678

That's why you usually should make one ticket per issue.

Is the game still freezing?

Maybe it should throw a script exception or simply do nothing (i.e. <obj> setmass 0 should not modify the mass).

Mass close.

Mass closing resolved tickets from last month.

Mass-close of resolved tickets not updated in last two weeks.

Can you please attach a repro mission from the editor (only zip it, no pbo)?

Sounds like a scripting error.

Mass closing resolved tickets from last month.

So it seems like there is an issue with the graphics card detection, if the nobenchmark option helped.

Could you please still attach the DXDiag output (go to Start screen -> type 'DXDiag' and run it -> select "Save all Information").

I think you'd rather bug them in the forum about it.

Mass-closing resolved issues not updated in 10 days.

Please attach dumps with current development branch.

Dumps are found in C:\Users\<username>\AppData\Local\Arma 3.

No *.mdmp?

Mass-closing resolved issues not updated in 10 days.

What is it now? Fixed or still broken? A bit of both? :-)

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

What happens if you doublemap LShift-<mousebutton> to the appropriate actions?

Mass close.

Mass closing resolved tickets from last month.

Mass-close of resolved tickets not updated in last two weeks.

Try the http://forums.bistudio.com.

Mass closing resolved tickets from last month.

Mass-closing resolved issues not updated in 10 days.

Mass close.

It's been discussed to death in forums, where these kind of text belongs. Closing.

Cheers, please post the ticket # here so I can relate it.

Linked up the tickets, kinda making this a meta-ticket.

If you got more tickets to add, let me know by comment.

Dupe of #11197.

You should open a new ticket then, do a correct description and repro. You can mention it here and I will link it.

Closing as unable to repro (I don't see such stars, like in the screenshots).

Mass close.

If they make a mini ToH within A3, this might happen, else rather not.

Please read in #9786 about the reasons.

Closing in favor of #17082 with more votes.

Mass closing resolved tickets from last month.

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass closing resolved tickets from last month.

Can you please make the flickering texture a different ticket and edit it out of this one?

Dupe of #7979 or #8909.

If your PC crashes or freezes, the game's usually not the culprit, rather the drivers, lack of cooling, too little memory, etc.

Please take this to the forums if you need additional support; http://forums.bistudio.com.

Does this still happen?

Looks like the default query string is:

"not (gametype = 'DAYZ' or gametype = 'DAYZ_M' or hostname like '%dayz%' or mission like '%dayz%') and not (reqBuild<=108906 and requiredVersion=77)"

on build version 77.108906.

It looks like there is one too many 'not'.

Update: I was too quick on my assertion that the one gamespy query was the source of the problem. Master85, of which I got the info just dug deeper and found out that it was only part of many queries which rely each on the previous ones.

The question thus remains why we don't see proper filtering/server listing.

Could it be a router/firewall issue?

EDIT: I realized you mentioned A2 already; so it could be indeed a NAT/Firewall issue.

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

Let's say, they use it wrong. Dupe of #12363.

Re-opening by author request.

Dupe of #10421.

Please split up your bugs (1,2,3) into different tickets, but do not create duplicates, search first and improve other tickets, if they match your suggestions.

Marking dupe of #10726. Devels will certainly review dupe tickets for good inputs.

On another note, you only offer another way to improve #10726. So this is indeed a dupe.

I'm sorry Demongornot, this ticket is hard to read, a wall of text.

• Keep the "Description" short and concise
• Use bulleted lists (like this one)
• Try to adapt the scheme "Observed", "Expected" (for issues also "Repro")
• Do only list one feature or issue per ticket
• If you want to give elaborate information use the "Additional Information" field

Thanks.

Mass-close of resolved tickets not updated in last two weeks.

Related to #11704.

Mass-closing resolved issues not updated in 10 days.

Looks like it might primarly be the issue with the marker STATE:

https://dev-heaven.net/issues/3212#note-3

Can you verify, if it's actually the same issue?

Updated Additional Info, reassigned.

Well, I don't think so. There is a DirectX 12 Upgrade planned for this year for one, so they don't ignore all the fancy tech out there.

But I guess Apex would only makes sense if really dynamic destruction is considered, which would have a huge impact on multiplayer synchronization too. They got enough issues as it is without new features there. So, we'll have to hang in there and see what the roadmap features bring (http://arma3.com/news/arma-3-roadmap-2015-16). If anything, then for APEX update (guess the naming is coincidential though). :-)

PS: Above VBS is mentioned. BIS and BISim are completely separate companies for a while already and while some cooperation between the two companies still can be expected, they can't simply "take" VBS devs or resources for A3 for an engine rehaul. Then again, for basic engine, VBS and Arma are too far apart to simply "graft" such base features easily.

OK, I've been trying to clean up this thread, but I've given up for today, it's too long and I don't have multiselect; every delete action takes 10 seconds on the FT.

Let there be a word of warning, those abusing and insulting will have their account suspended, specially if it comes down to masses of such comments.

I won't accept further derailing of this thread and will remove any unrelated or uncivil comment.

Mass close.

Please add a simple repro mission (editor).

Please do not dupe your own tickets, it doesn't help anyone and just clutters up the Feedback Tracker which makes it harder to find ANYTHING.

OK, thanks for that, but in order to fix the issue, a way to reproduce it is needed.

Optimal would be a small repro mission and repro steps or at least observations as to WHEN it happens and possibly WHAT the trigger to the issue is.

Also a screenshot of the erroneous message would be helpful, because if it says "Hans was killed" it means the engine confuses the player with AI or environment damage and not the player object or var name itself is lost.

Danke erstmal; aber um das Problem zu beheben, muss ein Weg aufgezeigt werden, wie das reproduziert werden kann.

Am besten wäre eine Repro-Mission, Repro-Schritte oder zumindest eine Beobachtung, zu welchem Zeitpunkt es passiert, resp. was der Auslöser für das Problem sein könnte.

Auch ein Screenshot der fehlerhaften Meldung wäre interessant, denn wenn es wirklich nur "Hans was killed" sagt, dann wäre dies ja nicht nur ein Verlust des Spielerobjekts oder des Variablennamens, sondern dann würde der Server den Spieler der den anderen tötet mit einer AI verwechseln. Wenn es "Hans was killed by " sagt, dann wäre es effektiv ein Problem mit dem Spielerobjekt selber.

Niemand versteht dieses Ticket, welches offensichtlich mittels Google Translate (oder ähnlich) aus dem Deutschen übersetzt wurde.

Kannst du bitte deinen Text noch auf Deutsch liefern, dann kann ich übersetzen resp. feststellen, ob es sich um ein effektives Problem handelt?

Updated some details in the ticket.

I kindly suggest, that you wait with such requests until the full game with it's myriads of weapons already prepared, comes out.

Mass close.

Ok, I think we get the point.

Please review your ticket and request specific animations which are actually missing (edit the description).

Excellent, thank you. Red circles or arrows are missing, but I could spot it right away.

Mass-closing resolved issues not updated in 10 days.

Pardon the German, but the video in there is in English:

http://video.golem.de/internet/12304/tracking-point-stellt-netzwerkfaehiges-gewehr-vor.html

Another example, how modern technology warfare (it's not even 2015!) will look like!

Dupe of #4823.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

I believe this is fixed, right?

No bug.

Actually, I believe it should work under water, but it probably should look more like ink flowing out. Guess that's just a minor visual issue.

Mass closing resolved tickets from last month.

Dupe of #4493

Mass closing resolved tickets from last month.

Dupe of #10726.

I suggest mouse controls should be fixed to head rotation only, but there should be a way to interrupt the healing sequence.

Closing this ticket down in favor of tickets like #23127 - it may or may not have been fixed in earlier build (according to the last few comments), but the engine changes in 1.42 are a whole new 'game'.

Mass close.

Actually, I think the OP made himself very clear in "Steps to reproduce".

Action becomes invalid and is retained in unclickable state until the action menu is closed.

galzohar suggests that the current action selected disappears when invalidated and no other action would be selected, but the action menu remains open. The invisible cursor would stay at the same position where the invalidated action disappeared, so if you used the mouse wheel you wouldn't have to start from the top.

I think the OP's idea is less confusing.

Good idea!

Dupe of #10726.