fixed in 2.00
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
Nov 2 2020
Sep 13 2020
Sep 9 2020
Mar 29 2020
Jan 31 2020
Jan 18 2020
Jan 13 2020
Mar 11 2019
Jun 16 2018
May 12 2018
In T128506#1680882, @Wulf wrote:Hello.
Thank you for the report, but can you please send me a repro of what exactly you did?
May 3 2018
Jul 22 2017
Apr 26 2017
Mar 28 2017
Mar 7 2017
Jun 1 2016
May 10 2016
This and another error don't seem to occur anymore after I updated my video drivers.
Went back to devbranch today, this issue doesn't seem to happen anymore.
Uploaded. :)
I'm able to find RPT files, but not BIDMP or MDMP files. They should be in the same folder, right?
This and another error don't seem to occur anymore after I updated my video drivers.
Heads up: My PC fucked over and I don't think the issue is with Arma atm. Had to reinstall OS and a bunch of other stuff. You can close this issue if you want. I found the problem a while back: SweetFX.
I updated the ticket with 4 new images: 2 crash messages from the launcher and 2 images using the dependency walker.
I don't remember how but it seems to me like I fixed any issues with battleye. I made a post on the Biforums as I really want a fix ASAP.
Link: https://forums.bistudio.com/topic/183450-startup-crash-with-windows-10/
I'm also gonna upload the crash files to the ticket. I was getting a entrypoint not found error but it seems to have stopped showing up in the unusual crash popup.
I fixed the original issue by verifying integrity of game cache, but another crash has arisen. I updated the ticket accordingly.
UPDATE: I believe it's a model issue, I disabled the original shadowVolume but I'm not sure... It works in game now and doesn't crash. Should I send the files of the weapon for testing?
I'm having issues with the feedback tracker's file upload so I've uploaded the crash files else where.
https://mega.co.nz/#!TwJnxZbB!mr5iT_RpUAklupZF8rIXUiaQYM01qi0ip1agICoijnY
Yes, but I'm talking about visual effects AND the feature.
I seem to have fixed the issue by disabling this part of my mod.cpp:
Here is the link to the files: https://mega.co.nz/#!Lk5jWaST!V3RRagZzm2DZfbEdnL5yBNjje9Ivjjyeka0uL1x92JI
And he is the mod.cpp:
https://mega.co.nz/#!u1RGASaK!NbBnhsMkD0pRVkEBR0SK1bo1P56HrHIRCm_AFDmdHN
I disabled the buggy code and it was fixed.
This is resolved so I don't see why it isn't closed...
Yes, CBA, Blastcore: Pheonex, Dragonfyre, Grace Sway, Mao blood mist, and my own personal mod which should have no effect. I've disabled dragonfyre before and that's how I found it, but it still happens with dragonfyre.
It seems after further testing it's happening to all weapons after some time firing them. Very strange.
disregard this, I was wrong and figured it out
This would be an issue with the ShadowVolumes. There are a multitude of issues with clothing/gear that BIS never fixed.
Ex. This, UV errors on CSAT uniform, NATO UV(?) errors on uniform, 5.56mm Mags in NATO vest, etc.
@AD2001 - Yeah he is. Also is the Up-Armored variant gonna be a future variant of the Slammer in a an update?