troop
Member-
Content Count
343 -
Joined
-
Last visited
-
Medals
Everything posted by troop
-
Please check this info. http://www.flashpoint1985.com/cgi-bin....t=58954 (Change system variable of 'TEMP' and 'TMP' to path without spaces) It has at least helped one fellow ArmA user;..maybe this is your solution as well? Worth a try, simple change involved. Let us know.
-
I can confirm the bug as well. SU-34 AI gunner fires rockets as soon as selected. (and a target is present;..if no target detected, AI holds fire [obviously, no? ] ) EDIT: small addition. AI Gunner even fires the rockets, when set to 'hold fire'
-
Simple, this one. Dont use said addon(s) until their readme (if any) clearly states *game version* compatibility. Most addons (goes for most other games as well) are made with/in mind of...one specific version of the game, say ArmA 1.02. A lot has changed since then. Perfectly normal, you (could) get errors, if you use an addon made for 1.02 with 1.05. If you already know the situation with OFP and its various version numbers, you already know, there were different game version addons as well. Say, addon for v1.46 (without any extensions) and another addon-version for *game version* v1.76 onward. From step to step, there were *major* code changes. If you did not have OFP and are new to ArmA, maybe you still have used addons for other games, were the same rules apply (also;..network code, savegames,...the lot)
-
Some things to try out. Daemon Tools installed: Uninstall Arma and clean install folder. You do not have to delete your profile folder! - Disable all Virtual drives (Set number of devices - disable) in the DT tray menue. - Open Device manager and 'disable' the virtual drive there as well. It will be named differently on every machine. (Mine = TA5536S VCH153V SCSI CdRom Device) - Remove your physical DVD-Rom drive in device manager (uninstall) and reboot. - After reboot, open device manager and verify, your physical DVD-Rom drive gets the first drive letter after your HDDs. If it does not get the letter, change it manually. - Install Arma - start once - reboot - patch 1.05 - *Optitional* Enable Virtual drive in device manager Enable Virtual drive (Set number of devices - 1 drive) in the DT tray menue. (Should get drive letter right after physical drive. If not, change it) ---------------------- Daemon Tools *not* installed: Uninstall Arma and clean install folder. You do not have to delete your profile folder! - Remove your physical DVD-Rom drive in device manager (uninstall) and reboot. - After reboot, open device manager and verify, your physical DVD-Rom drive gets the first drive letter after your HDDs. If it does not get the letter, change it manually. - Install Arma - start once - reboot - patch 1.05
-
Yes, just tried 2 single missions and both end with said command. shift + Numpad minus then type (faster) 'endmission'
-
This is my error when installing the patch
troop replied to mrbean1112's topic in ARMA - TROUBLESHOOTING
mrbean, Please check this information carefully: http://lists.mysql.com/win32/14957 Things to look for quickly... Do you have an 'Event ID 7000' in your system events log? Look for the latest entries. Do you know how to change your 'TEMP' folder path to C:\TEMP ? (Path with no spaces! ) (While you're at it;..also change the 'TMP' sytem variable to C:\TEMP, because many installaton routines use TMP also) Check the 2 pics attached;..sorry, german system, but you should get the idea. 'My Computer' - RMB - properties - advanced - system variables --- http://img45.imageshack.us/img45/8074/systemvariableyb0.jpg - http://img339.imageshack.us/img339/5968/systemvariable2ax2.jpg --- If the error still persists, maybe the file you downloaded is corrupt. If you can count this out, check for hardware failure (RAM) or too sharp settings. (o/c?) -
Almost sorry to update this information. Chopper rearming has *not* been fixed in 1.05 patch. You still need to retain at least 1 hellfire and 1 rocket to be able to reload @ truck. - Please include this in the next patch;..thanks a lot!
-
5104 - New: Grass flattened around soldiers, improving visibility. - 5115 - New: Terrain Detail now controls grass detail as well (can be used to turn off the grass) - 5130 - Fixed: Languages switching was disabled for some distributions
-
Hint: Does 'dotarget player; dofire' ring any bell? Activated by an radius trigger; regardless if player is seen or not? (true AI LOS meant here) - Once I played this mission, I had to have an look at it. They just could *not* have spotted me coming... I am sorry;..but the above init line, bound to an radius trigger... what would you call that?
-
Thank you *very* much!
-
Check this mission by maxqubit: http://www.flashpoint1985.com/cgi-bin....t=57182 It *can* be done.
-
Browse your 'documents and settings\yourusername\own documents\Arma' folder for the 'ArmA.cfg' file and either rename or delete it. (ArmA creates new one upon start) Also, you can try to change the resolution you have had working before manually within that file. (800x600? ) - Resolution_W=800; Resolution_H=600; - And also, check if this line: 'refresh=XX;' (xx=60 - ??) matches the supported refreshrate of your monitor. For mine CRT, this is set at 'refresh=85' Do not set higher than supported (= black display) -- For now, leave everything else in there untouched except res and refresh. That should do?
-
Sound issue - vehicles LOUD from miles away
troop replied to horrgakx's topic in ARMA - TROUBLESHOOTING
^ Oh yes;..I want to strongly second this. In my entire 'gaming career' in which I have been playing what must be hundreds of games (or so it seems) - since the advent of EAX;..OFP and ArmA are the *only* game, that exhibit this problem. (10 years+ for EAX? ) Not, that it kills me..then again..thinking about *that*... - No, honestly. I cannot think of any other game. The only one, that comes close with regard to vast open terrain right now would be Oblivion, which I did play lately, and..no such sound behaviour there. -
Sound issue - vehicles LOUD from miles away
troop replied to horrgakx's topic in ARMA - TROUBLESHOOTING
It seems, not every brand of soundcard is affected by this sound bug. Many onboard solutions, like the Realtek ones and other brands of PCI cards are not. My Creative Audigy 2 however (latest drivers) is affected and setting Hardware Acceleration to off (but EAX on) fixed it for now. (Reboot for good measure) --- Btw;..with OFP there were the very same problems;..at least for me..with 3 different Creative cards..during the *complete* OPF patch cicle: 1.00 throughout 1.96 (+now the same in ArmA) That is: 2001~2007 - SoundBlaster Life! Audigy 1 Audigy 2 - Thus, I do *no longer* believe, that this BUG will ever be fixed. For Creative cards, that is. Hardware Acceleration off = all good but waaay less 'beefy' with regards to explosions, for example. However;..due to the 'false' distance impression you get, stealthily crawling around there, you constantly 'feel' that tank driving over your neck;..while its still 2 miles away. - -
Check this thread: Joystick Sensitivity Adjustments http://www.flashpoint1985.com/cgi-bin....4;st=15 I can highly recommend KeyCats settings on the bottom of page 2. However, you may need to adjust for *your* gear/setup. Working very well for me with an MSFF2
-
Oh, and about that disappearing/non-present 'Rearming' (Bullets) icon... Say, you fired your second-to-last Hellfire and return to your FARP, not too far away from the action;..chances are high, that your *gunner* (if Cobra) is still *targetting* his last target, which may be in different angle than *your* (choppers) line-up with the ammo truck... - You will probably neither get the icon, nor the menue entry for rearming. So, make sure, you assign *no target* to your gunner, if you want to reload your chopper lined up with the truck. Make this an habbit. If he is, say, F2, hit 'F2-2-1' (Gunner;..target;..deselect currently tracked target)
-
^ This isnt a problem;..its just the game; it is nothing (enjoyable) for you. Good thing, you took it back already. Prevents you from getting higher blood pressure and heart attack. 'NO ONE uses wasd.' Yeah, right.
-
Aha. Ok, I cannot read italian, maybe another Italian ArmA player, who reads this, can make something out of this message? But;..if the DVD-drive from your former PC can read the DVD-contents, while your newer drive has problems, it is either an operating system problem or the drive fails to read specific media. I have got an similar configuration here, where one drive reads everything ok, but the other, different brand does not display contents. (and as an result, cannot start certain games, because the contents are not read) - 2 things to try now. Can you just swap those drives for an test? If this is successful and you can start ArmA every time you try then, you probably either need to keep your older DVD-drive in your newer PC, or shop for an different brand of DVD-drive to avoid future, similar read-problems. (Edit: I just want to clarify;..you only should consider shopping for an new drive, if *other* games/media are also not read correctly. ) - Is your Operating system up to date? (If XP, SP2 + all patches) Your chipset drivers for mainboard? (very important) - If you run Vista already, then sorry, no ideas there.
-
Hello nettrucker. Is it an generic Windows error message, or is it an 'specific' Securom (Copy protection) error message? (If the later is the case, you get an numbered code;..please post this code here) Can you please post the exact error message here? - How long does your DVD-drive read the DVD, before the error message pops up? More than 10 seconds? Do you have another DVD-drive around just for testing? (friends) - One more try: Open your Explorer and point to your DVD-drive with the Arma DVD already inserted. This should spin the drive up. While it is already beeing read, doubleclick ArmA-icon;...does this help?
-
Try a 'CLean Boot' if you have performance issues
troop replied to Tracer's topic in ARMA - TROUBLESHOOTING
As an alternative, Google for 'EndItAll 2' (fully configurable once; what to exit, kill, lock, ect. ) benefit: No reboot required for the same 'clean' effect. (~16-20 essential processes left running) Reboot required only for normal startup (with all programs) and no fiddling with msconfig. You save one. I love this prog (prepare for gaming immediately) ymmv -
There has been an report related to blurry visuals in *windowed* mode. (One ATI card, one NVidia) Not to be mistaken with the Depth-in-Field Vision effect! (postprocess high in settings) So;..do you have the same blurry visuals in *Fullscreen* mode as well? Or only, if you run the game windowed? (There seems to be some 'downsampling' involved) Do you have set postprocess effects to low or high? Are you indeed having blurry visuals *if* postprocess is set to *low* ?
-
Just to make sure;.. did you change the AA settings via 1. ingame options/advanced 2. extern/driver control panel 3. external 3rd party tool, like nHancer ? Thanks! ------- I am asking, because the ingame AA/AF functions, compared to the usage of an *external* tool like nHancer 2.1.1 do have *drastic* differences in quality/performance of the game! -- Everyone willing; (Nvidia cards) please make this short test and compare ingame picture quality/performance\FPS: 1. Set AA/AF to 'Very High' via ingame option. (What are the limits anyway? (x2, x4, x8, x16? ) 2. Set AA/AF (x4;x8 for AA - x8;x16 for AF! ) via external tool nHancer - >ArmA profile. -- From this I learned for my setup, that the ingame 'Very High' quality setting is actually *higher* in performance but 'worse' wrt picture quality-compared to external setting! -- Now, if I *disable* AA/AF ingame and use my nHancer profile with x4 MSAA(or x8 SSAA) AA and x16 AF, the ingame picture quality is *splendid* compared to above ingame setting, but performance drops to unplayable, very choppy levels. (foliage..) -- Same res and other settings, of course! So;..me? I am *not* using the ingame settings of ArmA because I like the higher *picture quality* I can get from nHancer settings;.. disregarding the lower FPS possible. If you want higher FPS/less picture quality, you'd better use the ingame options. -- Ohh, and this are only my observations on *my* setup. This has *nothing* to do with slamming ArmA/settings/options! Card used is an Gainward Bliss 7800GS+ (7900GT) 512MB AGP with 93.81b -- For an very quick (details@distance! ) test, just compare 'Very High' AF setting ingame with an nHancer x16 AF setting. What is your observation? --- And if you want the maximum in picture quality, fiddle with negative LOD (not too much; 0.3 - 0.5) as well.
-
Preordered; waiting.
-
MSFFB2 joystick ( with modified settings in config = perfect) Logitech TrackMan Wheel optical TrackIR 4 Pro with TrackClipPro