Jump to content

NoPOW

Member
  • Content Count

    246
  • Joined

  • Last visited

  • Medals

Everything posted by NoPOW

  1. Please google for Win32_152812.exe or Win64_152812.exe (I'm using the 64 bit driver), or send me your e-mail address by PM... I'm interested to know if it would solve this issue for you too.
  2. I think I better wait for this new version - might be just some stupid little thing I overlooked. For me ArmA won't start if the current user wants to use tbbmalloc but doesn't have locking rights, so that's quite easy to troubleshoot... and 32GB should be enough. ;)
  3. Nope, only Committed and Private bytes... I'll do some further testing. Does this mean that the 2GB is reserved for ArmA, but the program is not going to use it because it's not in its working set?
  4. Hmmm... It does seem to work, though the 2.048.000K only shows up in Committed and Private bytes, not in 'Locked Working Set'? (This happens in both user and administrator space.)
  5. Giving the client administrator rights is unfortunately a no-go for me; is this just for the time being and will it not be mandatory at a later stage? EDIT: I mean I'm not comfortable with granting ArmA/Steam administrator rights; neither by giving the current user admin rights, nor by granting the client admin rights...
  6. Well... I've tried to revert the Intel drivers and it seems that 9.17.10.2932 (December) and earlier perform flawlessly, while 9.18.10.3071 (March) and later tend to suffer from this issue... EDIT: Made a topic in Intel's Support Community http://communities.intel.com/message/214368
  7. I'm no longer able to resume scenario's from a saved state; every saved state and completion tick mark in the 'Scenario's'-menu has been deleted...
  8. Trying the game once a week to see if there is any progress concerning this issue, but to date it still crashes withing 5 minutes. Well, will gonna give it a try next week; very disappointing...
  9. Though it might solve the issue, updating your BIOS is not without risk and should not be mandatory to run a (read: just this) game. Having Arma 3 prefer not only an Intel/nVidia-combo, but also a specific MoBo-manufacturer's BIOS should be a no-go...
  10. That's just sad... EDIT: I was wondering, is there a way to generate the ground textures procedurally to get rid of that ugly stamping appearance?
  11. I'm impressed by the efforts and advancements made here... But is there any feedback from BIS on this issue? Hate to see all this work being in vain if BIS updates this themselves in the (near) future.
  12. Just drive the truck closer to the wreck; don't stop when your passenger tells you to... :)
  13. It could be a Windows 8.1 issue... But it caught my eye immediately after today's update; probably would have seen it if it was there before, not sure though...
  14. Seems to have been a glitch; restarted Arma3 and now it is gone. It wasn't the RAM but pagefile that was growing /w 50MB/s until it reaches the max. amount of physical RAM. Will investigate further if it happens again. EDIT: Did some further testing as I did keep encountering this 'glitch': First of all: It is not related to the new campaign, just starting A3 will flood the pagefile. Only in full screen mode (NOT windowed mode) the amount of 'Committed Bytes' keeps growing. If a pagefile has been set to a specific amount, exceeding this amount will trigger an 'almost out of memory'-message by Windows (8.1). Had my pagefile fixed, variable, on an SSD and on a HDD, all making no difference; except for having A3 in a window, which does not seem to suffer from this behavior.
  15. While playing the campaign my memory gets flooded, all of the 32GB... Alt-Tabbing resets it back to ~6GB, and then it starts flooding again.
  16. NoPOW

    AI Discussion (dev branch)

    That should be dependent of the AI's role: an MG would, a sniper wouldn't... EDIT: Once an enemy disappears behind an object, LoS should be devided into sub-LoS'es that mark a margin in which the enemy is 'captured'.
  17. I encountered the same problem... Do you have PPAA disabled? If so, can you confirm that enabling it fixes the rendering issues? EDIT: The whiting out of 1st person objects occurs relative to the sun's position, not the horizon...
  18. Hmmm... When PPAA is disabled I have both the rain disappearing and 1st person objects whiting out. Can somebody confirm this?
  19. Fixed: Light shafts rendering (1st person objects are now rendered correctly) Unfortunately, I still do encounter this 'whiting out' of 1st person objects.
  20. Today's DEV changelog: New possibility to turn off adaptive crosshair in options Searching these forums there seems to be no entry about what makes the crosshair 'adaptive'... Care to enlighten me? :)
  21. NoPOW

    Arma Steam Update problems

    Was the Steam version not issued by Atari? Have you already contacted them? PS. Try punctuation.
  22. Well, seems they (this one and the one from ECS) both make the VD relative to the altitude. Have to test it, but since ArmA has a lot of locations with harbours, an extremely low VD will unfortunately not work very well when looking out of a harbour...
  23. Just what I was looking for... but since it got removed from ArmAholic, the addon got abandoned?
  24. NoPOW

    Instant viewdistance

    Would it be possible to make the viewdistance relative to the drawn fps? So by entering an urban area or a forest the viewdistance gets limited to improve playability?
×