Jump to content

Vedexent

Members
  • Posts

    704
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Vedexent

  1. I think this would still be useful. I've seen a lot of "Blue on Blue" kills in multi-player. Now, whether its use outweighs the developer time/cost to implement is another story.
  2. Huh - I didn't know that. I guess that's working of Red/Blue faction affiliation? It does sound cool :)
  3. Really? I thought businesses just did whatever drives their bottom line. They can devote time and money to a new release product which will generate a spike in new sales revenue or they can spend time and money fixing issues in products already paid for. Which do you think they'll favor? True - in the long term it is in a businesses best interest to maintain quality, or people won't buy new product, and they have no revenue. But don't expect that they'll chop off their money maker - releasing new product - just to do customer support. Put another way: The MiG-15bis helps pay for fixing your F-86F.
  4. Thanks! I'll look into it. Any suggestions for securing the plugs into the blocks? Also, thanks to the people who brought up silicone greasing - I've noticed a bit of sticking recently, both in the flight stick and pedals (I guess never being serviced in 2-3 years will do that).
  5. I think the problem is that no one has implemented it ... so no one implements it :) An IFF pretty much has to work with everyone, and if "Plane A" can only identify whether other "Plane A" are friend or foe, it's kind of limited. Not useless, but limited. I'm also not sure that there's any functionality in the core to support this - so you could have a mish-mash of implementations (if implementing it without core support is even possible). If ED puts it in DCS 2.0 (2.2? 2.5? 3.0?), you may start to see support for it.
  6. 1) All mapping/keybindings need to be done in the CUSTOM KEYS dropdown, not the regular dropdown, for the C-101EB. This is a byproduct of it being a BETA, and won't always be so. If you have the T.1A Hawk, you'll find that it's setup the same way - and also a beta. 2) Liveries availability changes with country - and can be set in the mission editor, or mission planner. E.g. - the fictional USAF livery can only be assigned to US planes of this type. 3) You can start here although if you do some digging in the DCS documentation folders, you'll likely find a reference as well. In a pinch, you can look up real world airport data. DCS is usually correct. You can find radio charts if you look around in the User Files as well. Usually, such radio charts slip nicely into the kneeboard pages so you can look them up - literally "on the fly" - but the kneeboard isn't implemented yet. Hope that helps.
  7. I need some fresh air. Pretty sure I'm not supposed to be able to do this, at 300 Knts - but it's amusing. ;)
  8. Just a few minor ones: If I turn the COMPUTADOR off, I can still use the flight computer/director just fine - so what is this referring to? I get a CAWS alert, but it doesn't seem to have any effect on the computer, or engine operation. Is the IFF ever likely to actually have a function, or is this a limitation in DCS World it'self? What do the UHF / VHF Priority buttons do? Again, they don't seem to have any effect. Is this part of the not-yet-implemented Radio system? Same for NAV PRIORITY - toggling this off doesn't seem to interrupt TACAN or VOR navigation on the HDI What does the Backup ADI cage control for? The control seems to reset itself automatically, and I can't seem to cage the backup ADI - it reacts to attitude changes, no matter what. Emergency Air Brake retraction works fine - but the manual pitch trim does not, even when AILERON HYD OVERRIDE is engaged. Seat height adjustment doesn't work ;) Not complaining - and I suspect that most of this issues are a WIP, but I'm curious.
  9. Or - if you have Voice Attack, you can switch playlists by voice command - no need to alt-tab out :) Don't get me wrong - if Tango wants to leave this in, and expand upon it, I think it'd be great.
  10. I had no idea someone was developing this. It looks like she'd be fun to fly :)
  11. I'm not sure we want to get too fancy with this. Isn't it scheduled to go away once the UHF radio is actually modeled? While I thought this was a very clever "Easter Egg", if I really want background music, I can always play my media player at the same time I'm flying.
  12. We'll still see high end aircraft - just not as often, and they'll take longer to model as they're noticeably more complex. It's why we get a string of WWII aircraft, relatively quickly, in the time it takes the model a modern fighter. Belsimtek has managed to pump out at least three DCS level modules - Huey, Sabre, MiG-15 - and during all that time the F-18 is still under development (new high definition radar modelling, re-working of the PFM to include supersonic flight, etc. - you know, little things that need to be built). As Tango said, there are also licensing issue with active aircraft - look at the legal hurdles which delayed the release of the T.1A Hawk beta. So cherish those modern fighters - they're coming, but they will be much rarer.
  13. Noted :) I know that you fixed the vast majoring of issues, Tango - and quickly too!, wish we had more developers like you in my company :) - but we don't have the fixes yet :) I'm just doing trial and error here. I am generally used to deploying gear with the flaps in other aircraft, but found that the surge in drag and nose ballooning was quite noticeable. I've been working on the assumption that 190 was probably a bit fast to be deploying the gear. Are the gear more rugged than I've been giving them credit for - or am I hitting the glide slope too fast? If I can deploy the gear sooner, then I can still stagger the gear and flap deployment, with the gear coming much earlier.
  14. You bought the C-101 because you thought AvioDev would build a Mirage, based on Facebook images which they never actually commented on, or gave any indication they were developing? :doh: You do know that the girl doesn't actually come with the car, regardless of what you see on the billboard, right? I bought the C-101 because I want DCS to follow the FSX model of many developers creating planes, with DCS concentrating on improving the core simulator - so I bought this as well as the Hawk. I had no interest or knowledge of this plane previous to this project at all - but I've been very pleasantly pleased with it.:) Besides - there's nothing to say that AvioDev can't eventually do both. I suspect that that F-104 is probably a lot easier to develop given that it's no longer in service, has lots of published technical data, and there are at least 10 of them in civilian hands. So ... nothing to say the Mirage project couldn't get started in parallel, as it's likely to take a lot longer. F-104 might come out first, and the Mirage later. That is if and only if AvioDev has an intention of doing a Mirage; I have no clue if they are, or not.
  15. It could just be static scenery aircraft, or AI aircraft.
  16. Something else: While I can dial in mb barrel counter on the barometric altimeter, the altitude needle seems to jerk sporadically, and erratically. I'm used to dialing in the barometric altitude to "local airbase zero", but it's very difficult to dial the main needle to zero.
  17. Super minor - but apparently I can manually reset my gyros with the Vertical Gyro Fast Erect button, without ever having even turned the batteries on: totally cold cockpit. After I do this, the climb rate gauge will climb up to zero, apparently powered, now. I can't change it with the Manual Gyro Correction -just the Vertical Gyro Fast Erect button.
  18. I like the X52 Pro very much. I bought it with the non-combat pedals as well, and enjoy those. Mine have served me well for a couple of years now. I would disagree that there's no uses for the rotaries - I use them for Shkval tageting on the K-50 (one for zoom, one for gate size, with the throttle joystick for slew) - but if you don't fly Ka-50, or Su-25T, there may be less uses for them. Only two complaints so far: I would pay more for screw in connectors on the ends of the cable betwen the throttle and the flight stick. They seem to work out of sockets too easily, and I've had it happen at really inopportune times! The pinkie trigger toggle seems to be unreliable: did it catch this time, or not? I think they're a good medium level setup - but I've never tried the high-end sticks like the Warthog.
  19. I'd amend my earlier figures for ILS landing: Speed over the outer marker = 190 Knts Throttle to 82%, hold to ILS glide path. Possible use of speed brakes to slowly drag down your speed. Drop full landing flaps at 160 Knts. You may need to throttle UP after this to hold speed between 130-160 Knts, but don't drop the throttle below 80%-85%. The engine "spool up" time is too long. If you need to punch it up for emergency power, you need it running 80%+ so control with speed brakes. Be CAREFUL - there's an issue with the flight director altitude for ILS. If the flight director, and the indicator on the right side of the HDI disagree, the HDI is right. This is supposed to be fixed with next update, but isn't working now. Drop your speed slowly - you want to be 130 Knts over the inner marker. Inner marker - drop gear, nose up so that your rate of descent is about 500 feet per minute, throttle back to drop speed, but don't drop below 120 Knts. Keep horizontal course pegged on the flight director. Touchdown at 120 Knts - throttle back hard, flaps up to neutral fast, keep speed brakes out, keep her centered on the runway. Let her roll, lightly touching the brakes - she doesn't need tons of roll out room. This seems to work much better.
  20. OK - I threw up a mission on the server to challenge radio navigation,ILS landing, and cross-wind landing skills. It's simple. Get from Sukhumi to Kutaisi. In a blizzard. With 2km thick clouds with low ceiling. And wind ... lots of wind. Good luck! "Winter is coming" ;) p.s. Listening to the plane's built in stereo system works really well when you've got 10m visibility in a cloud bank and are locked to your flight instruments ;)
  21. NATO code designation "Fantasy" ;)
  22. From the FAQ on the website: Q: I bought (or going to buy) a license of Tacview 1.x, will I have to pay again for Tacview 2.x? A: No, you won't have to pay for Tacview 2.0 Home/Professional if you already bought Tacview 1.x! Even if the development of Tacview is longer and more expensive than initially planned (probably thousand hours of research and programing), I want to honor all the features promised from the beginning of this project. You will get everything you expected when you bought Tacview without paying more.
  23. Agreed! I'd love a Starfighter. CF-104, CF-5/116, L-39, and T-38 are all in my "oldies but goodies; I want to fly one" list.
  24. I had liberally scattered the ocean with Russian ships off the coastline of the mission airbase for "visual interest". Then I created some US C-101EBs to "mix up" the liveries available ... and forgot that there were Russian warships nearby ... until I saw the white trail of a SAM coming up to meet me ...
  25. You're part of one of those "It takes us three minutes to fix anything, but we can fix ANYTHING in three minutes" ground crews, aren't you :)
×
×
  • Create New...