Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by animaal

  1. Thanks. I must say, TacView should be an essential addition for anybody who flies DCS. I frequently find I've been shot down, with no idea how or why. It's only when I view the replay that I see where I went wrong, or (more often) how I unknowingly avoided near death many times before finally succumbing. One question - is it possible to customise the models? E.g. the Harrier uses a default "paper airplane" model, I'd prefer to use one of the other built-in models. And the new Tarawa carrier is represented as a block, which is fine, but I'd like to change its size to be more representative of the true size of the carrier.
  2. Thanks for all the feedback. I only have two things to give back to the helpful community here - how I have my HOTAS set up, and how to crash spectacularly when landing on a carrier.
  3. I uninstalled 1.5 today; the only version I need is 2.5. I find the performance generally good in 2.5, although my laptop and playing style might not be the same as everybody else's. I'm delighted to have just one install to worry about, as opposed to the three I had a month or so ago. The issues that affect me most are the unresolved issues in DLC campaigns - e.g. some missions that can't start, or others where the new Caucuses map obscures landing areas or other objects of interest. But I know these are things to be fixed in the campaigns, not in DCS itself. All in all, I'm far happier being able to fly the 2.5 Open Beta than being still in 1.5 and being told that 2.5 is "coming soon".
  4. Aha, thanks - I'm relieved to see this thread. I spent a couple of days struggling to follow the Hinds when they stop to almost a hover, and then rise to go over steep hills. I can slow down, I can rise, but I found it hard to slow/stop and then climb without burning out the engine. I completed the mission eventually, by staying significantly behind/above the Hinds.
  5. I agree it's very difficult. I assume that the aircraft sizes are properly calculated. Remember, at normal zoom you're seeing the whole front window of the cockpit on a computer monitor. In real life, that front window would fill a lot of your field of vision. I wonder if the planes would be easier to spot on a huuuuge monitor? (I only use a little 15" laptop screen, I haven't tried it) I'm not sure what the solution is - ideally the plane sizes would vary with monitor size. But that's unlikely to be implemented, because I don't think a PC can reliably discover the size of a connected monitor. It would be open to cheating in multiplayer.
  6. 2.9 mil and it doesn't even come with a Chuck's Guide?
  7. The whole idea of seasons is a cultural construct (some cultures have 6 seasons). Ireland uses an ancient Celtic calendar system to determine the seasons, so spring begins on St Brigid's Day on February 1. Meteorological or Astronomical measurement of seasons is perfectly logical... but there's also a logic to having Midsummers Day (or the longest day of the year) in the middle of summer. In this case, I'd rather ED uses the ancient Celtic calendar :D
  8. I was wondering about that, but I didn't want to appear pushy. Where I live, Spring is usually considered to be February, March, April. (Summer is May, June, July - centred around the longest day of the year, in the second half of June). So reading that the Hornet would be made available some time from April to the end of Spring appeared to be a fairly narrow window! Not to mention that in the Southern hemisphere, Spring is later in the year.
  9. during a recent ED sale, I bought the F86. Not sure why I did, I knew nothing about it and had no real interest in it. But having the plane, it made sense to also get the Museum Relic campaign. Wow! It's so much more than a collection of "Go here, bomb this" missions. There's a story/progression to it, and it really feels like I'm having an impact on an ongoing engagement. Better again, it's suitable for all skill levels. I'm terrible at spotting other aircraft (middle-aged eyes and a 15" 1080p screen probably don't help!), but the missions are designed so that it's not necessary to spot and kill all hostiles to complete the mission. I frequently replay a mission after completion, to see if I can do better. Also, all the missions that I've seen so far are based around the same geographic area, so becomes familiar. More time flying, less time looking for landmarks on maps. I'm not finished the campaign yet, but I can see that I've been gently introduced to many of the features and capabilities of the Sabre, without feeling like the campaign is pulling me through a check-list of skills. This experience has me re-thinking other modules (more advanced than the Sabre) that I had previously bought and hastily written off because I thought there wasn't much to them (Hello F-5E!) I don't see any other campaigns from Apache600, but I'll be keeping my eyes open for the next one!
  10. Very interesting and valid points, thanks. Working mostly at a desk, I don't have to worry about broken arms etc when I think about ergonomics.
  11. Having gathered a few DCS planes, something strikes me as a little odd. It's the positioning of the stick in combat planes. In the old days, the stick was placed between the pilot's legs, with the throttle by/on the left armrest. I guess this made sense - the right hand on the stick, the left hand on the throttle. The stick needs more precise movement, and most people are right-handed. In extreme situations, both hands can be brought on the stick in order to apply extra force. But with fly-by-wire (e.g. M2000C, A-10C, F15), why is the stick still often between the pilot's legs? Surely this leads to the body being twisted/offcentre for extended durations. In an office situation that would be less than ideal - I can only imagine what it's like under high-G. The F16 has the stick in what I would think is a much better position. I've never flown any of these planes in real life; do combat pilots suffer more than most people from RSI? :)
  12. I've recently posted a thread describing issues I've had (and fixed) with my X52Pro. One issue us the same as the one you describe here; an issue with jitter when using the slider for zooming. Would you object to starting an extra application while using your throttle? If you install vJoy and Freepie, you may be able to create a new virtual device that filters the output of your slider. In effect you're smoothing the output. It works for the X52Pro, I think it should for the Warthog too.
  13. I’ve got a Saitek X52Pro, and after a lot of bad decisions, I’m eventually settled on a configuration that I’m happy with. I hope a few of these might save time for other X52Pro owners. I’m attaching a zip file with my default X52Profile for DCS, and the Freepie script referred to below. Before starting DCS, I have to plug in the X52Pro, then start the “FreePie” application. But for me the extra step is worth it. Wrong Approach: Originally, I started with a separate X52Pro profile per DCS module. The thinking was that I could keep the default key configurations in DCS for each module, and use the Logitech profile editor to create an X52Pro profile per DCS module, mapping each HOTAS button to the keyboard key presses expected by DCS for that module. This worked, but had a few problems. 1. Every time I moved from one plane to another in DCS, I had to Alt-Tab to the desktop and select a different X52 profile. 2. The keys sometimes clashed when used with modifiers. A made-up example: Wheelbrake might be ‘Shift-W’. Nosewheel-steering might be ‘S’. When I press both together, the X52 profile generates the keypresses “S” and “Shift-W” simultaneously. DCS might see ‘Shift-S’ instead of simply ‘S’. Let’s hope ‘Shift-S’ isn’t anything like Eject! 2nd Effort: I created a single X52Pro profile for DCS, and customised the controller configuration of each module in DCS. DCS is now reading the joystick input directly, rather than just seeing the keyboard presses simulated by the X52 Profiler app. This addresses the two problems described above. Rather than using the X52 Profile editor to manage Pinkie-shift states, I let DCS do the work. In the DCS control configuration, I can set up the pinkie button (Button ID #6) as a modifier. It simplifies the X52 profiler profile for DCS. To allow DCS manage the pinkie modifier, remember to disable the Clutch mode globally for the X52 pro. Be aware that this will also affect all other games. The single X52 profile configures a few global functions, such as using the Clutch button on the throttle for TeamSpeak/Discord, and the throttle ministack bands for radio commands. Problems/Solutions Problem: I use VoiceAttack/Vaicom sometimes. But not when the family’s around. How to use a single set of HOTAS actions to activate the radio by Vaicom or Function key? Solution: I generally don’t like to change X52 mode states while flying. So in my one X52Pro DCS profile I define Mode1 for F-Key comms, and Mode2 to be for VaiCom comms. These X52 DCS profiles are identical other than Mode1 having the throttle mini stick defined to activate the radio using F-keys and Mode2 activating the radio using Vaicom TX commands. When starting DCS (or at any later time) , I can choose Mode1 on the stick for Function key comms, or Mode2 for Vaicom voice comms. Problem: The X52Pro slider is great for mapping to the view-zoom. Except it’s jittery. Solution: Install VJoy and FreePie. Set up a new device in VJoy, with just one slider control. This is a virtual joystick that Windows thinks is a physical device. A Freepie script can provide a filtered/smoothed view of the X52pro slider through this virtual device. In DCS, the slider on the virtual device is used for zoom view. This approach was originally described here: Problem: I want to use Fire B with the Pinkie modifier to activate “TrackIR recentre view”. With DCS (rather than X52 profiler) managing the Pinkie shift states, I need to disable Clutch mode globally for the X52 pro. But Freepie has a problem. Freepie can translate HOTAS button presses to keyboard presses, but only sends these key events to the active window They aren’t picked up by other background apps. Solution: Freepie uses Python, so a chunk of Python code in the Freepie script can cause native Windows key events to be generated, bypassing Freepie’s keypress generation. Problem: The X52pro throttle has 2 scrollwheels and two buttons below the LCD screen, but these aren’t available through the X52 profile editor. Can DCS make use of them to simulate mouse clicks/scrolling? This would be useful in VR. Solution: Yes. I mapped the two buttons as mouse left and right click, and one of the scrollwheels as mouse scroll. This was more code for the Freepie script. The button IDs in Freepie are: Left Scroll wheel up/down: #34, #35 Right Scroll wheel up/down: #36, #37 Upper/Lower buttons: #32, #33 Problem: The latest X52Pro drivers and profile editor are provided by Logitech rather than Saitek. But the Logitech version doesn’t support a “default” profile that’s loaded automatically on startup. Solution: The Logitech software does support default profiles, it just doesn’t expose the option to specify the default profile. To set one yourself, edit the registry and create a new key Computer\HKEY_CURRENT_USER\Software\Logitech\Configuration\StartupProfiles Within that key, create a string value. Mine’s named: {75BB6CC8-FB40-4BE1-BF2B-4B10397A98A8} The string value is the path to a profile. See the attached screenshot. Now, when I plug in the HOTAS, the DCS profile is automatically selected. By the way, the X52Pro Mode switch can be used as a modifier in DCS. In DCS, you can create a modifier called "Mode1" using button ID #28, a modifier called "Mode2" using button ID #29 and a modifier called "Mode3" using button ID #30. X52Pro Profile and FreePie script.zip
  14. This would be so cool... I wonder how well it would work in a sim like DCS, with it (in real life) typically flying with a crew of 5. E.g. the navigation radar and ECM have dedicated personnel. If it's not possible, then how about the Blackburn Buccaneer?
  15. I'd love to know this too. It seems to be fixed in relation to the main axis from tail to nose. Although the word "Depressed" may imply it's offset somewhat from this axis...?
  16. I bind one of the spinny wheels on the throttle as an axis. That's for the X52 pro, but I think it should be the same with the X52.
  17. I fear you're overestimating the abilities of some of us (or at least me :D ) to get to grips with even the simplest of things... Last night I wanted to try the Master Modes (Nav/VSTOL/AG). The pocket guide refers to the "MASTER MODE panel", but I couldn't see it labelled in any of the diagrams. After a while searching through other documents, I found what I was looking for in the NATOPS flight manual - a diagram showed it as the "Master Armament Panel". In hindsight its position on the console is logical/obvious. I know I've a lot of searching ahead of me as I start trying other systems!
  18. I'm quite new to DCS, and I like the sound of these changes to DRM. Ideally there would be no DRM, but I suppose we live in a world where it's needed. The current mechanism had me baffled. Separate keys for each module? Differing activation limits? Multiple DCS installations (stable/beta/alpha) with separate module installations, but common license registry keys? The new way is far simpler, and hopefully will be more flexible for ED to tweak as time goes on. Maybe over time the DRM can be loosened up if it shows not to increase piracy. the only reservation I have is whether it needs cooperation from all the 3rd party developers. E.g. if a particular developer does not agree with the new proposal, will we end up managing the old and new DRM mechanisms at the same time?
  19. Not sure whether this is a bug or not, but I've heard it described as "not like real life"... The Magic missiles lock targets around the cross on the HUD (the major axis of the plane), rather than in the HUD circle.
  20. I've had a good MP match tonight using DCS build 1.5.7. (Flying the M2000). Eventually I got hit, and the plane wasn't responsive so I ejected. As soon as I hit Ctrl-E three times, the screen froze for a fraction of a second and then I was dumped to Windows. My tacview file for the session was 0 bytes long. Is this likely to be recorded by the server as an eject? Or a disconnect? Or is there anything obvious I might have done to contribute to the crash? I'm a bit wary that it looks like I quit when I was hit... Thanks.
  21. Hi, just in case anybody else has the same concern in the future and discovers this thread... I've spent the last day starting to get to grips with this plane and it's great with 3DOF. The protrusion from the front of the console blocks nothing - or at least nothing that I wanted to look at. In those Youtube videos showing the RWR blocked, it must have been due to the player having his head offset laterally while zoomed in. Thanks for the information in the posts above.
  22. The head tracker I use is the EdTracker. It is great to pan, but it doesn't have positional sensors. I wouldn't doubt you... by "a more modern F-5", I was comparing its role to the two planes I already have; the A-10c is really only a ground attacker, whereas the F-5 is mostly an A-A plane, with some ground attack capabilities. From a quick look, it seemed like the Mirage is stronger in A-A than A-G...? I think I'll buy it. I know I'll regret it if I don't :)
  23. 3DOF in the Mirage? Hi, I'm quite new to DCS, just starting to get comfortable with takeoff/flight/landing the A-10c and F-5. The Mirage looks very interesting, in capability perhaps a little like a more modern F-5. However, while I have head tracking, it's 3 degrees of freedom rather than the full 6. Is this likely to cause big difficulties with the Mirage? I've seen a few YouTube videos, and the Mirage seems to have a big "sticky-outy-bit" on the dashboard that blocks the RWR and a number of other controls unless the pilot can move his head to the side and down. Thanks!
  24. (sorry, wrong sub-forum, moving to the Mirage section)
  • Create New...