Jump to content

thaFunkster

Members
  • Posts

    343
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by thaFunkster

  1. O thanks. That is so simple I should have thought of that. I will and give it a whirl... --- Ah, sweet relief. Viper you saved me from depression and misery many thanks.
  2. Yeah but that does not work, I tried that. I am now trying using the trigger as Ralt + Space, because I thought being digital, button two may just be on or off, but maybe the trigger stays pressed.... I dont understand how it helps using the default in game keys, because I tried that way too.
  3. O yeah, duh guys, I should have known that :P Well, I mapped 'Release Weapon to the button 2 on my X52, the moment I tap it (to begin holding) it just deselects my target. So, I cleared the keys in options, went to the X52 profile editor, and mapped Ralt + Space to Button 2...Same thing happens. Only way I can fire is to take hands off stick, reach over to the keyboard and hold Ralt + Fire - hardly a satisfactory situation, and making pretty much impossible to ever fire an Aim9 or R77... Thanks for all your help so far, but any X52 users also having this issue?
  4. So what is the difference between 'Fire Weapon' or whatever it was called (Enter) and 'Release Weapon' (Alt+Space)??
  5. AH, thank you. So I maybe just need to hold it down...I will try that.
  6. I have just got FC2, have almost the same system specs: E8400 @ 3.5G, 4G RAM, ATI 4850, Win7 64 Bit. I get the same stutteing with clouds I just tried a flight where there was total cloud cover below 3000 ft, and framerate was about half what it normally is. I am going to go and see if it exists without clouds. Then try the workaround incase that makes a difference. I post because I have almost the same system and this may help ED to narrow the problem down.
  7. Ok, I am no newbie here, been playing 1.12 for around a year. As I posted in the General Section, ED you have done a great job on FC2, I am really delighted with it. Now the only problem is with the controls. I loaded my old X52 Lock On profile, and some things work as they are supposed to, some things, (minor details, like oh, say firing missiles :music_whistling: ) do not work at all. Now I have all the keys mapped through my profile to the keyboard keys, so Button 2 on my joystick corresponds to 'Enter' on the keyboard, or 'Fire Weapon'. Now this just does not work, every time I hit it, it just unlocks my target. Ok I thought I will try another way, so I tried mapping the Joystick Button 2 to the Fire Weapon as well as the Release Weapon function in the FC2 Options. Still the same thing. Ok, as a test I tried firing using the Enter Key on the Keyboard - still, all it does is Unlocks my Target. I cant fire a damn missile! What is going on please?
  8. So, I finally fired it up. I was expecting an incremental improvement over 1.12, but right from the word go I was impressed. Sleek new interface, very nice. Nice music rather than horrible irritating radio chatter, nice. Then I jumped in to quick flight with the f15 and wow - it blew my mind. The new colour pallette and contrast settings look absolutely stunning, the feel of the aircraft is incredibly responsive and just feels better. The terrain and scenery is a joy to look at and overall it impressed the hell out of me. You have really done well this time ED, good stuff! Complaints: I loaded my old X52 LOMAC profile, when I went to use it I found some commands (BVR Mode, Change weapon, Fire cannon) that I had mapped still worked fine. However, some commands like release weapon did not work, so I had to just use my cannon. (Spacebar did not work either for some reason). So have you changed some commands from 1.12? This would be a strange thing to do. I went to the options and found that now I have to set my axis tuning for every single aircraft - I have to do the same thing 8 times over! Not happy about that. The option to set controls for every aircraft is a really good one, and I applaud you for including it. However, please implement a global control profile as well which will be applied to all aircraft, and only overriden if the user specifies controls for a particular aircraft The way I like to set up my profile is to clear all key commands in game, then map the default keyboard commands to my joystick outside of the game. This does not seem well supported in FC2. I only set axis commands in game. Anyway, overall impression is that I am very impressed, if the complaint list seems long, it's only because this complaint is preventing me really enjoing the game, and it will take forever to reset. Funk.
  9. I have thought the same thing as it is the same as you describe in 1.12... But why would they model it unless it was there for real as if they did it for the A10 then surely they can do it for the rest of the aircraft if they wanted to..
  10. Bring on DCS:A10!! Then DCS:F/A-18, then DCS: F15E, then... Please!
  11. Nice flying once again! I have been playing FC for around a year, and I never developed your bait tactic, going to use it for sure from now on!
  12. Excellent stuff! I enjoyed the hell out of that, reading in this style really gives a sense of realism to the whole thing. Glad to see also that not only does the terrain in FC2 look great, but they have done up the interface immensly! Well done ED! Now looking forward to firing up my copy some time in the next week. Keep that AAR's coming mate.
  13. Beautiful it is indeed. It still amazes me that a hunk of metal and composites like this can stay in the air on such small wing area...Its amazing. Not talking specifically about Mig-29, but all aircraft, except maybe ultralites, they and kites are about the only things that look like they should be up there.
  14. Nice, New South Welshman here.
  15. Yeah, if I was in the squad I would probably volunteer for some Tower Time, sound kinda cool to me. --- O: About everyone having to be on TS, well, that would not be such a big deal, there could just be one "Tower and Approach channel" or something on TS, people would just have to log into it for takeoff and landing, and would not have to be on TS for the rest of the flight. Those who failed to respond to Tower calls could be given one warning and then banned.
  16. Yeah, it would be ok if the patches were not made from square shapes, but rounded shapes instead. So, Im in the ugly camp too Im afraid.
  17. Another Aussie? Or Asia somewhere?
  18. Yeah, I would have thought it was some weird HOTAS thing before I thought of it as a mouse!
  19. Or from taxiway, same deal if you wait for them. --- Actually I think I am wrong, I take it back.
  20. Good point Mustang, but this obstacle already exists. The rules that need to be followed regarding taxing and takeoff would have to be broadcast by server in all languages at the start. Very very cool avatar, totally spinning me out!
  21. @Joe Kurr: Wow, that is really neat! @Mogas: Funny, that is actually a cool idea having cadets do that sort of thing. Just laughing to myself imagining a 3 hour AWACS escort, how boring!
  22. Only if you plan on doing a lot of 25T flying.
  23. You can cycle the designated target, I think with the ~ key. There is usually more than one pre-programmed target.
  24. @ Pilotasso: I dont entirely understand what you mean about the notch thing. Are you saying that you have to close to target before firing a 27ER because at long range you can easily defeat it by doing a split-s or similar? Isnt that also the case with a 120? @isoul: You might be right, but I am not sure that evaluating missiles in combat would really add that much data: They would already have live fired the missiles in every conceivable situation I imagine..
  25. Ok, but they will be written from your checkbook...:music_whistling:
×
×
  • Create New...