Jump to content

Mister Frag

Member
  • Content Count

    4266
  • Joined

  • Last visited

  • Medals

Posts posted by Mister Frag


  1. Not quite sure how it looks on your screen... However, if you aim in real life the sight will be a bit blur since you focus on the target with your eyes.

    And of course in real life you wouldn't do that, given the proper training. You're supposed to focus on the front sight and blur out the target.


  2. If I was in the armed forces I would definitely use a 3-point sling because you can literally drop your gun and whip out the sidearm or basically free up both hands in an instant...as opposed to putting the rifle on your shoulder/back.... Sloooow

    Actually, you would more likely use exactly what you are told/allowed to use.

    While some services may be tolerant of improvisation and field modifications, not all of them are. You certainly aren't going to have much luck if you decide to swap out the sling while you aren't deployed. Imagine lining up for inspection, and you are the only guy with a non-issue sling -- you are going to be scrubbing toilets for weeks.

    Having said that, I agree with you about the sling. I've got a couple of rifles, and all but my precision rifle have some form of three-point sling.


  3. I had the same problem with VoIP and V1.08 on my Audigy, and had stopped using it (VoIP).

    I downloaded the driver from Station Drivers and installed it, but haven't had the opportunity to test it yet.

    The reason why I'm posting is because ArmA would not start up after installing the Station Drivers Audigy driver, and reinstalling DirectX (the June 2007 version) didn't help either. What did the trick for me was to reinstall OpenAL.


  4. The cards that KODE suggested do have PS 2.0, and would therefore be able to allow sniperboy to run the game. They may not offer the best performance, but given the budget he has, they are one of his few options.

    sniperboy, before you commit to buying anything, please check whether your system has an AGP or PCI Express slot. Given that your current card doesn't have PS 2.0 support, the system may be old enough to date back to the days before PCI Express, and you don't want to wind up with the wrong card.

    pchaxor, being rude and insulting other members on the forum doesn't do much to enhance your credibility.


  5. Well here goes:

    I use FRAPS in the game to record orig video. But this file

    almost always get so big its hard to handle.

    So i use the "Quick Video Converter" to compress the

    file to mpg fomat.

    Then i use the divX converter to "downsize" even more.

    I got a 1.3GB orig avi/fraps file down to 45Mb divX form.

    There sould be a loss in quality when the film is done.

    I apologize for briefly taking this off-topic, but going from the FRAPS codec (which is lossless) to MPEG (which is lossy) and then transcoding again to DivX (which is also lossy) results in a needless loss of image quality.

    You're better off staying with the FRAPS codec while you edit, and transcode to your final delivery format at the very end.


  6. <rant>

    Grrrr... this is so annoying.

    I like to play SP Mission #4, where you fly the AH-1 and attack a convoy. I try to fly as flawless a mission as possible, staying low and sustaining little or no damage, and earlier today while testing V1.08 I wiped out the convoy, destroyed targets of opportunity, and didn't take any hits.

    I was on my way back to the base, just above the water and well out to sea to avoid AA fire from a Shilka I knew was lurking in a canyon near the coast. Then I got a radio message telling me that I appear lost, and seconds later the screen fades to black and the mission ends in failure!

    One of the things I've always enjoyed about OFP and now ArmA is the freedom to choose how to get a particular task done. Having mission termination triggers like this one in place really kills the experience -- please don't assume that I'm a complete idiot who can't navigate (especially when the next waypoint is indicated). I hope BIS will consider the removal of these triggers, or at least make them less strict.

    </rant>


  7. Whats the install procedure for this patch if i have the U.S. beta 1.07 patch? Thx.

    Just install the V1.08 patch by running the installer, and toss the shortcut to the Beta and the MOD directory it used. The beta didn't overwrite any game files and can be removed easily and cleanly.


  8. There is nothing that prevents you from making your own backup of the electronic download version on a data DVD.

    You are responsible for backing up anything you don't want to lose in the event of a drive failure or some other mishap, and that goes far beyond having a copy of ArmA. I assure you that when the need for having a backup arises, you'll wish you had spent the $0.25 on a blank DVD to back up your download, and any other files and documents that you can't easily recreate.


  9. So in the end after 16 pages....is it worth installing this Beta patch or not???

    If you have a 8xxxx nvidia card... definetly.

    Unless you have the US (Atari) version of the game, in that case it won't even start...

    Well thats an inaccurate statement if ever I've read one on these forums, and I have read a lot of them on here. Just because YOU have issues, which could for all anyone knows be hardware related or due to a third party addon confliction, not necessarily be due to the 1.07 BETA Patch, doesn't mean to say EVERYONE who has the US/Atari version will definately have issues. I've played MP games with a lot of Americans running the Atari version using the 1.07 BETA Patch and the worst they've reported is the occasional crash (more due to the CPU intensity of the Evolution mission we've played after 3 hours), and the rare graphical artifacts similar to those reported a few posts previously by Törni.

    There is nothing inaccurate about what I wrote. I never said the 1.07 beta doesn't work with the Atari ESD version -- I'm running that myself. This thread is specifically about the second 1.07 beta.

    If you install the second beta on a system running the original V1.07 beta applied to a Atari ESD version, you will not be able to start the game because it will require reactivation. The license key from the original purchase does not work with the updated beta, and Atari/Softwrap will not assist with this problem.

    Atari even sent out e-mail to registered users advising them not to install the public beta, probably because they got innundated with reactivation requests. I didn't save the message, but I received it not 24 hours after trying to activate the second beta.


  10. anyone else get a product activation page when starting this new patch?

    I purchased this through digital download and it says my serial is wrong so now I can't start it.

    Same here, I have the ESD version from Atari and can't run the updated beta, the activation fails. I can still run the non-beta, and was able to run the initial V1.07 beta, but not the update.


  11. Daniel @ May 16 2007,09:29)]If you're gonna get it, get a hard copy. Download activations are a pain in the arse.

    The download and activation of the US version from Atari is actually completely painless (if you can handle a 2+GB download), and has the advantage of being able to run without having a CD or DVD in the drive.


  12. Your integrated graphics controller is not supported. Here is an excerpt from the README file:

    Quote[/b] ]========================================================================

    9. Compatibility Notes

    ========================================================================

    I. Pixel Shader Support

    As is noted in the requirements for this game, a card requiring hardware Shader Model 2 support is needed to play the game. It is used by the game to render advanced effects, such as reflective surfaces and smoke, during gameplay. Here is a non-exhaustive list of video cards and what versions of Pixel and Vertex Shader they support:

    The following video cards support Vertex Shader 2.0 & Pixel Shader 2.0:

    ATI Radeon 9500 Pro, ATI Radeon 9600 Pro/XT, ATI Radeon 9700 Pro, ATI Radeon 9800 Pro/XT, ATI Radeon X300, ATI Radeon X600, ATI Radeon X700, ATI Radeon X800 XL/XT, ATI Radeon 850 XT, Nvidia GeForce FX 5200, Nvidia GeForce FX 5500, Nvidia GeForce FX 5600, Nvidia GeForce FX 5700, Nvidia GeForce FX 5800, Nvidia GeForce FX 5900

    The following video cards support Vertex Shader 3.0 & Pixel Shader 3.0:

    ATI Radeon X1300, ATI Radeon X1800 XL/XT, Nvidia GeForce 6200, Nvidia GeForce 6200 TC, Nvidia GeForce 6600, Nvidia GeForce 6600 GT, Nvidia GeForce 6800, Nvidia GeForce 6800 GT/GTO/Ultra, Nvidia GeForce 7800 GT/GTX

    The following video cards support Vertex Shader 4.0 & Pixel Shader 4.0:

    ATI Radeon X1300, ATI Radeon X1800 XL/XT, Nvidia GeForce 6200, Nvidia GeForce 6200 TC, Nvidia GeForce 6600, Nvidia GeForce 6600 GT, Nvidia GeForce 6800, Nvidia GeForce 6800 GT/GTO/Ultra, Nvidia GeForce 7800 GT/GTX

    II. Laptop/Notebook Video and Audio Chipsets

    Integrated laptop video chipsets are not officially supported for several reasons:

    * Laptop/Notebook video chipsets generally provide very limited or no DirectDraw or DirectSound acceleration.

    * Laptop/Notebook vendors, such as Dell or Gateway, do not typically test their systems for game compatibility.

    * Laptop/Notebook device drivers are not as frequently updated to address graphical and/or game-specific issues compared to desktop video cards. In addition, device drivers are usually tailored specifically to a particular laptop/notebook by the manufacturer working closely with the chip maker compared to desktop video card device drivers being created for the chip itself.

    * Laptop/Notebook graphics chipsets are designed for low power consumption and generally use a smal amount of embedded RAM; using system RAM to make up any differences. Comparatively, desktop video cards in general have a larger amount of embedded RAM and do not resort to using system RAM.

    * With some exceptions, such as the Radeon Mobility 9200 or GeForce FX Go 5200, notebook "3D" graphics chips do not support the advanced OpenGL and Direct3D features that have become standard on desktop 3D video cards.

    * The simplistic audio chip in notebooks is designed for basic multimedia functions like playing music DVDs or business presentations. The standard audio for games is Microsoft DirectSound. DirectSound requires a high-performance sound architecture that is able to do real-time mixing of multiple sound samples.

    However, all of this aside, here are some laptop/notebook video chipsets that should work with titles requiring a 64MB Hardware T&L video card or higher:

    ATI Mobility Radeon 9200

    ATI Mobility Radeon 9600

    ATI Mobility Radeon 9700

    ATI Mobility Radeon 9800

    ATI Mobility Radeon x300

    ATI Mobility Radeon x600

    ATI Mobility Radeon x700

    ATI Mobility Radeon x800

    ATI Mobility Radeon x1300

    ATI Mobility Radeon x1400

    ATI Mobility Radeon x1600

    ATI Mobility Radeon x1800

    Nvidia GeForce FX 5200 Go

    Nvidia GeForce FX 5600 Go

    Nvidia GeForce FX 5650 Go

    Nvidia GeForce FX 5700 Go

    Nvidia GeForce Go 6200

    Nvidia GeForce Go 6400

    Nvidia GeForce Go 6600

    Nvidia GeForce Go 6800

    Nvidia GeForce Go 6800 Ultra

    Nvidia GeForce Go 7200

    Nvidia GeForce Go 7300

    Nvidia GeForce Go 7400

    Nvidia GeForce Go 7600

    Nvidia GeForce Go 7800

    Nvidia GeForce Go 7800 GTX

    Nvidia GeForce Go 7900 GS

    Nvidia GeForce Go 7900 GTX

    Nvidia Quadro NVS 110M

    Nvidia Quadro NVS 120M

    Nvidia Quadro NVS 300M

    Nvidia Quadro FX 1500M

    Nvidia Quadro FX 2500M

    Here are some laptop/notebook chipsets that we have had reported will not work with titles requiring a 64MB Hardware T&L video card or higher:

    ATI Mobility Radeon 9000

    ATI Mobility Radeon 9000 IGP

    ATI Mobility Radeon 7500

    ATI Mobility Radeon 7000 IGP

    ATI Mobility Radeon

    ATI Radeon Xpress 200M

    ATI Radeon 340M IGP

    ATI Radeon 320M IGP

    Intel Extreme Graphics

    Intel Extreme 2 Graphics

    Intel Graphics Media Accelerator 900

    Intel Graphics Media Accelerator 950

    Nvidia GeForce 4 420 Go

    Nvidia GeForce 4 440 Go

    Nvidia GeForce 4 460 Go

    Nvidia GeForce 4 4200 Go

    Nvidia GeForce FX 5100 Go

    SiS Mirage

    SiS Mirage 2

    VIA/S3 Unichrome Pro

    VIA/S3 Unichrome Pro II


  13. In V1.07 Joystick Button #2 (NEXT TARGET) doesn't work, it behaves the same as NEXT WEAPON in-game.

    If you go into OPTIONS -> CONTROLS and try to map it, pressing JB #2 exits the configuration dialog. Cancelling the control configuraton, exiting V1.07, starting V1.06, and resuming the A-10 mission already in progress allows JB #2 to work, and it can also be configured correctly without ArmA exiting the dialog.

×