Jump to content

gearheadman

Member
  • Content Count

    19
  • Joined

  • Last visited

  • Medals

Everything posted by gearheadman

  1. gearheadman

    Altis: Criticism and Suggestions

    Caveat: Haven't been to all the island yet. But, first impressions: More tree stands/forrested areas. Also, more hills. Some areas should be a bit more Stratis-like.
  2. gearheadman

    Better optimisation at release ?

    Edcase - There are some things that can make a significant difference. Fire up FRAPS and look at water, then away. Look at a forrest, then look away. Quite a difference in FPS. If they are capping CPU and/or GPU utlization, then yes, tweaking that can make a difference. Take a look at Issue #0000716 http://feedback.arma3.com/view.php?id=716.
  3. gearheadman

    Graphics induced Crash.

    Did 2 things and it ran for 3+ hours with no crash, which it hasn't done in a quite a while. Directed Physx (thru nVidia control panel) to only use GPU for Physx. Rolled back drivers to 310.90. EVGA forum indicated that artifacting, which was the symptom in my crashes, has been an issue with randon nVidia boards for drivers past 311. No common thread, it just seems to affect a random sampling of GeForce GPUs, regardless of type motherboards, CPUs, etc. Not sure which did it, or both. Might try to find out.
  4. gearheadman

    Graphics induced Crash.

    Ive got a GTX570 and have been having issues all along, but have increased 10x since the latest default branch patch. What happens is that my video crashes; get a screen full of green $signs overlaying the last game frame and the screen goes black. At least half the time my audio is still running tho: can hear players talking and ingame effects. Task mgr would indicate app was unresponsive tho.Downloaded and installed the latest drivers from nvidia sans the 3d glasses drivers, and did a steam validation of my game files. Started running MSI Afterburner and did notice something significant. Everytime it crashed, the gpu utilization completely spiked to 100% in a split second. It could have already been at 99%, but much more often it'd be running at 40-60%. Almost like it was told to calculate something with a zero in the denominator (infinity). I was running the nvidia drivers available just when the game came out. Only switched to the latest after the latest alpha came out and my probs spiked. Have switched back but no diffrrence. On a bad day, crashes ever 30 min or so. Good day 2-3 hours. Average is about 70 mins. Anyone else have these probs? If so, what settings you used to correct? If you have one of these nvidia cards and dont have probs, what general settings u use? Thanks all!
  5. gearheadman

    Graphics induced Crash.

    Only option is to choose what does the physx processing: card chooses, cpu, or gpu. Have run the first 2.
  6. gearheadman

    Graphics induced Crash.

    Last fault Fault address: 68B56DD7 01:000D5DD7 C:\Program Files (x86)\Steam\steamapps\common\Arma 3\PhysX3_x86.dll file: 404Wasteland_ArmA3 (__CUR_MP) world: Stratis Prev. code bytes: 44 D9 04 43 89 5D F4 8B 45 E8 8B 55 E4 8B 4D C0 Fault code bytes: 89 04 8A 8B 17 89 57 04 8B 0E 8B 55 D0 89 4E 04 Registers: EAX:00000000 EBX:493613A0 ECX:00000000 EDX:6E5FFC00 ESI:494A7A1C EDI:49468BFC CS:EIP:0023:68B56DD7 SS:ESP:002B:23BBFEA4 EBP:23BBFF38 DS:002B ES:002B FS:0053 GS:002B Flags:00010246 ======================================================= note: Minidump has been generated into the file C:\Users\Roger\AppData\Local\Arma 3 Alpha\arma3.mdmp
  7. gearheadman

    Graphics induced Crash.

    Will look into both. The later does have me puzzled; NVidia install has a check mark for clean/fresh/etc. install which appears to remove the existing drivers. I am assuming that this doesn't do the trick either?
  8. I've had way more crashes since newest patch. On average, once an hour.
  9. gearheadman

    Where is everyone?

    No, the error was to charge $3X for an alpha. Have run into numerous players who had no idea what an "alpha" build typically is or thought that "Alpha" was just part of the title. Seriously. People who pay money have certain expectations.
  10. "It is planned to update the default branch with the current hotfix this week (target: Thursday)" http://alpha.arma3.com/sitrep-00009 BTW, that was not a trolling answer. It's a reference to a common John Carmack (Doom, Quake) answer on when a game'll be finished. http://kotaku.com/5931411/john-carmack-says-doom-4-will-be-done-when-its-done
  11. gearheadman

    General Discussion (dev branch)

    Agree. Having an open-to-public Alpha -will- make Arma3 an even better game. The hacking asshats are poking holes in it now vs after final release.
  12. gearheadman

    General Discussion (dev branch)

    Bottom line is that BIS should NEVER have had them in there to begin with. Nobody should have had the opportunity to make a bad choice.
  13. gearheadman

    General Discussion (dev branch)

    Not a complaint or drama. It's just reality. Which is what it was posted as. Plus, A3 DnA was VERY specific in his post "we want to know how widely these are used (for legitimate purposes ). We don't use them ourselves." http://forums.bistudio.com/showthread.php?153686-Hacked-by-a-player-with-no-ID&p=2382507&viewfull=1#post2382507
  14. gearheadman

    General Discussion (dev branch)

    Reality: http://forums.bistudio.com/showthread.php?154001-whats-been-going-on-with-alpha-I-can-t-play&p=2384082&viewfull=1#post2384082
  15. gearheadman

    whats been going on with alpha? I can't play

    Problem is that the dev build fix has disabled a lot of existing missions that use the vehicle scripts. For the most part, Wasteland, which is running on 4+ of the top 10 Arma3 servers is now broke. That mission alone has been responsible for quite a number of alpha sales. Until things are resolved, new sales are gone.
  16. If you pull up the #userlist, you'll get something like this: 34 CleverUserName 387782 The number to use for banning is the -first- one. User name and the longer ID# don't work (for now). It does put the longer ID# in the ban list file, oddly enough. Note: you have to use the #userlist call to get this number. It is -not- the same as the in-game player #.
  17. On my keyboard, "/" is the default key for opening the chat dialog box. The "-" key is a zoom function key. So am not quite sure what your answer means. I most definitely say thank you for answering, and so quickly! What we can do is open the chat dialog box, type in #userlist, and get a return of 5 players - sesion id, nick, and player id. Getting the initial list to pop up is not a problem, it's cursoring through the entire list of players. Thanks ahead of time.
  18. Trying to use #userlist to ban players using first number displayed (the one that is like a session id# ; consecutively assigned # as each player joins). It's the only one we can get to work. Problem is that it only displays the last 5 or so players even with a full 50+ population. "Page up" doesn't scroll the list. Have unbound all in game "page up" kbd commands, but no go. Is this a bug, are we doing something wrong, and/or is there another way to scroll the #userlist?
×