Jump to content

killaalf

Member
  • Content Count

    158
  • Joined

  • Last visited

  • Medals

Posts posted by killaalf


  1. Nevertheless now that I know the problem and thank you for your help my question is, I have to tottaly reinstall the game or if I just replace the cracked exe for the original one will do?

    Just copy the original *.exe file back in and you should be good, it's the only file you replaced, right? So why would you have to reinstall the game? Absolutely unecessary, imo.


  2. Hellfires don't need that do they? They are optically tracking as far as I know.

    Well yes, they optically track a laser beam to the target tounge2.gif They also come in infrared and radar guided variants. What really gets me though, is that AFAIK the AH-1 does not employ Hellfire in real life, but TOW missiles. And don't get me started on their weird flightpath that more resembles that of a Sidewinder missile.


  3. In my opinion, all this hugging walls and shooting over cover as seen in R6: Vegas (a rape of the franchise, I might add) takes control away from the player - you're no longer there in person, you just control some muppet. Suspension of disbelief goes POOF! in a big way. If it was implented as in Vietcong then we're talking, that felt very natural to me.


  4. Has anyone been able to figure out how to use two controllers?  I have a HOTAS Cougar and rudder pedals and the last time I tried to use both of them at the same time I couldn't.  Did that change in 1.05?

    I'm using a Cougar also, plugged into which are my now pretty old CH rudder pedals (gameport connection), the setup is working flawlessly here. Then again the whole shebang is seen as one joystick by the OS, so if your setup shows up as 2 separate sticks you may be SOL.

    Why not program your Cougar to use, say, the radio switch (IFF in/out) as a rudder? It's not the same as using the real deal, granted, but it should work. It's how I've set up the Cougar for BF2.


  5. I usually play a chopper pilot in multiplayer coop games, and I have noticed some issues with helicopters.

    -Re-arming the Cobra is a nightmare. It wont re-arm no matter what I do.

    -It's impossible to turn off the engine after you have landed since the chopper will ascend if you don't hold down the key that keeps it on the ground.

    -NV goggles (as mentioned) are useless in the Cobra.

    -There is a parachute bug where people that jump out of my chopper are dropped from the parachute before they reach the ground, resulting in their deaths.

    Anyone else having the same problems, or have a solution?

    1) Re-arming works fine here. Admittedly it is a bit of a chore to find the right spot and then keep the heli steady there, but it is certainly doable. But I think the bug where you could not reload an empty aircraft is still there, so leave some ordnance aboard before reloading.

    2) I have no problem turning the engine off once landed, I have mapped the action menu to my HOTAS and just turn the engine off there.

    3) NV goggles in the Cobra are not useless for me, granted, it's easier to see with them when on foot, but I can see just fine nonetheless. Their usefulness diminishes the higher you go, I noticed, but as I like to stay real low it is not a problem for me.

    4) Never tried that, so I cannot say anything about it.


  6. I think the main purpose of this thread is not to discuss the problems, but to ask for some info from BIS...

    It's probably up them that can give the proper answers of causes and possible fixes etc :P  But shoot me if im wrong

    The thread is called "Dual core users....", the problem with framerate loss is imo caused by the GPU not the CPU, so the only logical info BIS could give is: "There is no problem with using Dual Cores, you just asked the wrong question" wink_o.gif


  7. What makes you think that the drop in performance is related to the CPU? To me, that loss is clearly on the GPU side of things. How do I know? Well, whenever my framerate drops significantly I look up at the sky and boom, the framerate shoots up again. Now, the CPU would still have to calculate all the goings-on around me regardless of where I look at any particular moment, the graphics card, however does not have much to render when looking straigt up, so to me that is a clear indication that the graphics renderer is the culprit here, wouldn't you agree?


  8. Choppers fly higher than 500 m for various reasons, for example to minimize the risks of small arms and machine gun fire.

    And thereby maximizing the risk of getting caught by manpads, SAMs, AAA with their pants down - uhmm, I don't think so, small arms and machine gun fire is the lesser evil by far.


  9. So the difference appears to be in the way controls are mapped and/or used.

    That's it then, as I was always using a HOTAS for flying in O:FP, I never used the keyboard at all - I even have the action menu mapped to one of the hats of the stick.

    Based on these findings, maybe plaintiff1 would like to reevaluate his opinion of the flight model in O:FP. That said, I still like the flight model in ArmA better, with the exception of the "slower" collective and the (imo) overdone banking/pitching induced by rudder input (especially in the Cobra).


  10. Are you suggesting that a helicopter that "crashes" when 500 metres above the water can be blamed on the pilot?. He didn't say they crashed in to the sea, they crashed when no where near it as I read it. That would indeed sound like a bug. In fact it sounds like something someone here suggested about bird strikes somewhere near the coast. The Sahrani Triangle I think was how it was being described. The effect was that the pilot was killed, but the chopper was completely unharmed, until it hit the water of course.

    According to Suma, it's fixed in 1.05

    http://www.flashpoint1985.com/cgi-bin....1014169


  11. I'm truly baffled by wamingo's video - all I can tell is that my Flashpoint (it's not the GOTY edition, btw) behaves quite differently and if I would have flown that, the heli would've crashed at least 3-4 times if I left the collective alone. Then again, maybe this terrain following only kicks in at a certain height? It's a rare occasion that I climb above 30-40 meters, in general I'm about a couple of meters over the treetops max. Ok it's not that, tried flying higher and no change - when I approach a rise, my height over ground diminishes and once I'm over the hill, it rises again according to the ground under the heli, but all in all I'm staying at the same height above sealevel the whole time.

    Having flown around a bit in Flashpoint again, I wish that BIS would give me my responsive collective back, push it away from me and I start to drop immediately and vice versa, sigh.


  12. Both.  Depends on what I feel like.  Try without the mods.  I think I read that Radic uses mods too.  

    edit: Try this also, judge the maxium height above the terrain you can fly at near sea level.. now go up a cliff and see what the maximum is.  If the alt reads the same you're being influenced by the ground (IIRC, the alt in OFP reads above the ground rather than above S/L or a calibrated height).

    I just tried without mods, versions 1.46 and 1.96. Played "ground attack" and after destroying the convoy I approached a hill/mountain just a bit southwest of the carnage. Speed was around 20 (is that knots or kmh btw? I'm betting on kmh as the altimeter seems to be metric, too), the height would gradually decrease until my nose touched the hillside and the chopper settled down. Surely that was not too fast to prevent that terrain following to kick in, now was it?


  13. Well if that is the case I played OFP LAN coop with my wife successfully for over 2 years without any problems! tounge2.gif  It also let me join on other PCs too without telling me that the CD key is in use as is the case currently with ArmA.

    Delta Force 1,2 +3, Raven Shield, all of R6 games, Ghost Recon, Ghost Recon AW and many other games all allow me to play over LAN on ONE CD key without any problems!  smile_o.gif

    Well, to be honest we did not see any adverse effects caused by this message and/or FADE itself. OTOH we rarely if ever successfully finished those coop missions anyway, so who's to tell if that was due to FADE or just our crappiness tounge2.gif

    Anyhow, to prevent any future mishaps in this vein I just placed an order for a second copy of ArmA with play.com for 28,- Euros delivered, a steal imo. Especially considering I spent about 80,- Euros for my german special edition, which I still think of as a bargain. I probably buy a couple more to give out to friends and get them interested in this marvelous game/sim. No wife watching over my wallet, so who's gonna stop me? biggrin_o.gif

    See, with tools like hamachi it is super easy to fake a LAN over WAN (=the internet) and I have total sympathy for any developer trying to prevent this from happening.


  14. So it seems than I can no longer play LAN games with my wife without having to go out and buy another copy!!  whistle.gif

    So who's idea was this or is it an error? Every other game I have bought to date (including OFP) has allowed me to play over a local network on at least two machines without needing a different CD key! I must say I am very disappointed. I hope it is an error and will get fixed!  confused_o.gif

    It's not an error and no, you could not play OFP with the same serial on LAN without FADE kicking in. Sorry, but you are mistaken there. I recently borrowed my OFP disks to a friend, because one of the disks of his GOTY edition was scratched and he could not install it from them. So he installed it using my disks/serial and as soon as he joined our session (via hamachi) we'd get the "Original games do not FADE" message.


  15. Radic:  Well established behaviour meaning everyone that I've ever heard of talking about the helicopter behaviour in OFP says the same thing but you.  Are you talking about OFP: Elite by any chance?  I'm not attacking you, I'm debunking your arguments.  Please try to understand that either you are not observing the behaviour of the program correctly or your program is different than everyone else's.  I am being no stronger in my conviction that what I have observed in ofp's behaviour than you are, but you are the only one (that I have heard) describing it the way you are.  Short of a mass hallucination on our part, something is wrong/different with your version.

    When I said authority I don't mean anything professional.  I meant it in a testimonial sense...

    Well, I'm nobody then, I guess. I repeat, my Operation Flashpoint does not exhibit this "established behaviour" and I've tried it just yesterday, with O:FP 1.96 + FFUR/SLX

    Even when I was just limping towards some hill, my nose bumped (not crashed, I was that slow) into it while the fuselage showed absolutely no tendency to rise above the obstacle if I left the collective untouched.

    Could you please tell me if you are using mouse/keyboard or a joystick?


  16. huh.gif - no, if I fly toward a hill - or some trees at a fixed "collective" setting and at a constant airspeed (which in OFP - without an artificial horizon instrument or VSI) is how you know you're flying "straight and level" - then I will crash!!

    In my OFP the engine pitch / rotor load sound doesn't alter unless I do something to make it do so....

    In fact... - I just popped off to the desktop, fired up OFP and CONFIRMED this!!! (did a classic CFIT into gently rising terrain at constant airspeed / AOA / no control input changes - then did same into a cliff).

    Maybe you're either unconsciously flying it or have auto-hover turned on??

    Same here, if I don't increase collective I crash into the hill every time. IIRC, there is a difference in the flight model when using a joystick vs. mouse/keyboard - I'm using a Cougar HOTAS with CH rudder pedals myself so maybe that's the reason?


  17. The big problem is that in OFP I must force AA and AF in ATI control panel, in ArmA I must let them on "application controlled"

    Since I still play both games, and since I still play many not so old games without AA settings embedded (thus I got to enable AA in control panel), I have to constantly switch AA in control panel to 4x/application controlled.

    ArmA is the ONLY game I know that disables AA if it is forced in ATI control panel, and that's troublesome.

    That is not a big problem at all if you use Ati Tray Tools, for example. Set up profiles for your games and tweak them to your hearts content. For ArmA I have AA/AF off in the profile, for OFP I have it on 6xAAA/16HQAF.

    I have been using only the naked drivers + ATT for years now, I have neither the control panel nor the bloated CCC installed. Works like a charm!


  18. What I  don't like:

    1. The aimpoint sight on the M16/M4!!!! Why is it so small? Surely you would place your eye right up to it, not hold it 10cm away when looking down it????It is almost useless right now. This is a MAJOR problem considering this weapon is used most.

    2. The machine guns. I love the fact that you can actually hit something with them now. The M60/PK in OPF were so useless I NEVER chose them. As it should be, the machine guns dominate the open ground in ARMA -- however you can now fire an entire 200 round box with the SAW with virtually no recoil, this weapon is now TOO ACCURATE over long distances! Equally the .50 cal gun on the humvee/BRDM has no recoil at all - it feels like a laser gun! A machine gun has to be fired in short bursts to hit anything in real life.

    3. Some of the weapon sounds are wimpy and low-fi sounding in ARMA. I love the 'crack' of bullets passing overhead (are these mini-sonic booms?), but the AK/M4 gunshots themselves are rather poor. Added to this I found some major sound glitches in the demo, but I'm sure these will be patched in due course.

    4. Why oh why oh why can't a fit, young infantry soldier simply climb/jump over a 3 foot (90cm) high fence when his life is under threat? It is ridiculous and shows that the player movement code has changed little from OFP. A major disappointment banghead.gif

    ad 1) Have you tried holding down on your second mouse button when in ironsight mode? This zooms the view in a little more and makes accurate shooting a piece of cake, imo.

    I'm not too sure on this matter but are all these different aimpoint sights not actually there so that you don't have to bring the rifle up to your eyes and still be able to hit?

    ad 2) Guys with firsthand experience on the reallife weapon say the SAW is fine as it is.

    ad 3) yep, those are sonic booms created by supersonic ammunitions.

    ad 4) Agreed. There's even lower walls (about 1 foot, 30cm) you should be able to just step over, but can't.


  19. Probably a noob question but where do i implement -maxmen command as i have over 2gigs, is it in the start up command line? Also what does -nosplash mean?

    Edit your ArmA shortcut like that:

    "x:\....\ArmA\arma.exe" -maxmem=xxx -nosplash

    -nosplash gets rid of the splashscreens at the start of the game.


  20. Do you use the CCC or some other tool for your X800pro, like AtiTrayTools? See, I'm using ATT myself and have experienced the same kind of artifacts with Gothic 3. All I had to do to get rid of them was having "Geometry Instancing" set to enabled in my profile for the game. No artifacts in ArmA either way, at least on my X1900XT Cat6.11, but still worth a try perhaps. Another thing to try is playing around with the "Catalyst A.I." settings.


  21. You're also not able to explain wrong LODs with a lack of graphics memory.

    I think ........ or game-version.

    btw People on a german board with a X1900XT report similar issues..........

    You're right, I'm not. But engine issue or not, if it does not happen on all machines you cannot totally rule out some hardware/driver conflict as well, imo. The issue better not rears it's ugly head on my X1900XT, though wink_o.gif


  22. Quote[/b] ]GeForce 6800 (128mb)

    Go for a better gfx card with at least 256 MB and some more RAM couldn´t hurt aswell.

    I second that. But still, at very low settings (800x600) his 6800 should be able to display the game with all the right textures loaded. New driver perhaps? Maybe the readme contains information with which version of drivers it was tested with. I'd try them first, but you need a new graphics card, asap! Then the RAM.

×