Classnames have changed. Not a bug.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
May 10 2016
In fact, it's the same issue.
I recommend posting suggestions like this on the forums. The tracker is mainly for bug reports and engine feature requests.
If you've already found an existing ticket, there's no reason to create a new one.
Both issues have already been reported.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Already reported.
Insufficuent/unclear ticket description. Please make a new ticket with a more clear description of the issue. (And search beforehand, in case it has already been requested.)
Duplicate of #13201.
Ok, seems that was referring to a different issue.
This ticket definitly needs a higher priority and severity! <<<
Done.
A few more crash dumps would be great.
Fixed: MP CTD when client submit briefing screen via the Continue button <<<
^^ From the September 6th changelog.
Can anyone confirm that this issue was fixed?
There are already several reports for this.
Covered here: #13172
Duplicate of ticket already assigned. (To the same dev.)
Added some info from here to there.
This issue has supposedly been resolved in the latest dev branch update.
Please test and report back. :)
This issue has supposedly been resolved in the latest dev branch update.
Please test and report back. :)
Because bug. I'm seeing it on my second (32bit) PC aswell, while all is well on the 64bit one.
The devs are on it with max priority.
@usnoozulooz, it supposedly is.
@nomisco, what settings are you running, specifically view distance, object draw distance, object details and terrain details?
Have you tried running with the -nologs parameter?
I was talking to nomisco. So far, I've seen only one other person with a 64bit OS report this problem, and he claimed that -nologs fixed it.
It appears that there are two different performance issues, one of which is exclusive to 32bit OS users and cannot currently be fixed by any known means. The other affects 64bit users but can be fixed by reducing settings or using certain parameters.
Some people who could run Stratis with 12k draw distance are apparently baffled that the same doesn't work on Altis.
Unable to reproduce in the patch from August 27th. Closing.
This issue has supposedly been resolved in the latest dev branch update.
Please test and report back. :)
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Duplicate of #10373.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Unfortunately this ticket is too vague and needs some concrete feature requests. BI cannot simply "implement JSRS2".
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Unable to reproduce in dev build. Probably already fixed.
Closing.
Has already been requested.
Ticket contains multiple duplicate issues.
Please search before posting and read the "how-to-guide" (red button, top right) before creating new tickets.
Closing.
Fixed in dev branch.
Closing as duplicate.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Working as intended.
Duplicate of #8658.
Already requested.
Closing as duplicate.
Please only report specific feature requests and bugs.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Marking as resolved.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Duplicate / already requested.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Thanks for the info. Closing. :)
Already reported. Please search before posting.
Unable to reproduce. Must a problem on your end.
According to the forums, this was fixed.
Duplicate of #1105.
Jumping has also already been requested. Closing as duplicate.
Already requested.
Closing.
Indeed a duplicate of #8658.
Duplicate of multiple issues.
Already reported.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Already reported.
Closing as duplicate.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
This is said to have been fixed.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
OPFOR and Independent now have different NVGoggles class names.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Closing as duplicate.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Duplicate of #12877.
Duplicate of #9955.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Duplicate of #10038. Please search before posting.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
There are already multiple tickets about helicopter physics.
Closing as duplicate.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Duplicate of #12798.
It's a feature, not a bug. If you want higher fidelity in the grass flattening, you'll need to make a feature request.
Closing.
Reproducable in latest dev build.
Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.
If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.
Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.
If this issue is still relevant in current dev build, please re-post.
Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.
If this issue is still relevant in current dev build, please re-post.
Smoke particles still cause massive performance issues in the latest dev version. Even a single smoke grenade can cut my framreate in half if I'm close enough that the smoke fills a significant portion of the screen. Went from 80 fps to around 40 in a test on Stratis using a single grenade. (GTX 770)
I wonder if BI have considered implementing something like this: http://http.developer.nvidia.com/GPUGems3/gpugems3_ch23.html
Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.
If this issue is still relevant in current dev build, please re-post.
Marking as reviewed.
Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.
If this issue is still relevant in current dev build, please re-post.