HOME 
You spoke too soon.Originally Posted by jpinard
That said, I'm surprised no wise-cracker has voted "no". LOLThere's always one.
You spoke too soon.
That said, I'm surprised no wise-cracker has voted "no". LOL
Core i7 920 @ 3.995 GHz, HT off
12 GB OCZ DDR3-1600
GTX 680
2x Intel X25-M 80 GB SSD
Windows 7 Pro x64
ArmA2/OA Settings:
1920x1080 w/ View Distance at ~3600
Video Memory at Default
MSAA Very High, AToC=0, SMAA Ultra
Post Processing at Very Low
All other settings at Very High
Ok I sent one in.This is happening to me on even regular Arma 2 without OA now.Seems something went weird after patch to 1.07.CTD's after 2-5 min of play.
Last edited by WarriorM4; Jul 20 2010 at 08:14.
Dwarden, are there resources for users to sanity check their environment before submitting bug reports that are very likely not bugs at all? You ask for people to submit everything like crashes and such, but doesn't that produce a ton of tickets that are user configuration or user enviroment issues and not bugs?
For example, if after patching the game, a user has crashes but there aren't reports of that 'en masse', and the user does not provide repro steps or much detailed info, what is the workflow for something like that? Does it go to BIS for someone to load up into the debugger and report back what the fault was, providing a kind of tech support? To rephrase, does that fall into the scope that the CIT serves?
I am asking this because if the above situation is acceptable and desired by BIS, providing tools and guides for users to sanity check their environment may help alleviate the creation of such tickets that are user issues rather than game bugs. I often help troubleshoot peoples game issues, I have found that MD5's are very useful for determining if a users game data is corrupted. When the game is corrupted, all kinds of issues can arise, the most common of which is frequent crashing. (when the game goes to load an asset which is corrupted, poof) Also, in the above example case, the user could have had an error while patching that wasn't reported because he didn't see it or think to include it..(dunno, major lack of detail there) any number of things could have happened really but still likely not a game bug and isn't being reported to other users.
Any consideration for a similar yet separate CIT system specifically for tech support, such as community helping community, rewarded with rep points or something, like experts exchange or yahoo answers, to reduce the amount of non-bug dumps going in BIS's direction? (BIS could still get involved for tough ones, or if enough people are having the same issue(as in a game bug), a staffer would forward the ticket to the original CIT)
In a perfect world, the game should never crash, even if presented with garbled input.. But that is never going to be the case, and I've never seen a complicated application capable of doing that. The error checking and handling code would equal or outnumber the actual app code!
Just curious,
Cheers
(also sorry to you Warrior for using your ticket as an example, don't take offense)
Last edited by oktane; Jul 20 2010 at 10:51.
wrong place
Last edited by Sabbath; Jul 20 2010 at 19:37. Reason: wrong section
Hi, i've observed may "issues" that i would call bugs, in the ArmA2, they're there too after patch the game to the 1.07; mainly things like missing parts on LODs (i.e: the M1911 front sight = not pressent.) or shadows bugs on the units (i.e: USMC officer's cap don't haves shadow), this model don't have chest pockets on his jacket and neither on his sleeves. And are some more like this, i've also issues with the keys not responding in game and i've a "small issue" with the OA single (training) missions as i don't have an specific key to crouch, so i can't pass the 1St stage = closed access to OA's armoury. This kind of things that don't make CTDs or entire break the game... are issues that report in the CTI? or we should do it here, in the forums instead?. Let's C ya
Yes, while minor those would all be actual bugs imo, aside from the ones about pockets and crouching. Especially if they can be reproduced on another players machine, then for sure they are universal bugs. (like i have verified that the shadow is missing for the hat)
The pockets inclusion was the artists choice when BIS made the model, I don't see how this is a bug at all. If it was posted, it would pretty quickly be assigned into a feature request I bet. The last one about crouching, um, set a key to crouching? That sounds like a user configuration issue, the game expects you to have a key bound to it. If you don't want to do it, then while in the mission, hold down left shift and type: numpad -, e, n ,d, m, i, s, s, i, o, n (without the commas, all while holding left shift) What that will do is pass the mission successfully. Dunno if it works for what you are talking about. I find it simpler to use the mission editor to test things rather than the armory.
I too had some LOD issues with the betas that became 1.07 and 1.07 itself. Especially certain weapons held by other units appearing to be square and malformed up close. (very low LOD) This has also started happening in recent OA betas. The front sights being missing may be a part of this overall LOD issue, or something else..(I can't understand why the game would show low LOD models for the players 1st person gun, it shouldn't do that afaik) If you run very low graphics settings, be sure to mention that if you report it or find the existing ticket. I looked at the 1911 and it appears normal in my 1.07 A2, it has a front sight even though it is a bit low. (the camera alignment is a little bit off, it's hard to see)
Cheers
Last edited by oktane; Jul 21 2010 at 07:18.
Hi, with all or most the settings on high, this is how i see the M1911 A1 front sight in the ArmA2 and OA:
I'll call that a bug... the problem to reproduce some of the other issues that i've, is that some are not easy to reproduce AFAIK... like the keybinds issue... i'd configured the game (ArmA2 and OA) as the ArmA, same kybinds for same functions; but for example the switch fire modes key don't works most (like %80) of the times as soldier on foot... and never work as gunner on tanks and APCs/IFVs, like on the LAV III or the AAV7A1 so i don't know how to reproduce this issue that i've with the keys other than copy and paste my entire game's config, where everything looks normal to me. Let's C ya
Sort of off-topic, but what is that little radar thing with the names at the bottom of your screenshot? Is that some mod?
Last edited by W0lle; Aug 3 2011 at 18:51.
Hi, yeah man, it's a great mod/addon made by zx64 called: ShackTac Fireteam HUD. And can be found here: - ShackTac Fireteam HUD v100715.
It looks great and do a great job, i've only try it in SP on the 1St missions of the campaign (of the ArmA2) and is really usefull, but if you load a save game... it don't shows up again; i hope that they fix that little issue, improves very much the game play. Let's C ya
Quick Bug report Arma2 OA combo.
Don't know if any one mentioned a small graphics issue with some of the Mi8 helicopters?
Empty ones when started up ,the hub starts to spin about 4 seconds before the blades giving a weird tangle effect.
Posting Permissions
Reply With Quote
