Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/11/22 in Posts

  1. My wife had never flown before she met me, and she had a significant fear of flying, didn't particularly like me doing it either. She was forced to fly on a couple short trips to Kyiv, and then the big trans-Atlantic flight when we moved to the US and they didn't go real smoothly (I looked over to see her in tears repeatedly crossing herself during the first takeoff ) Anyway, fast forward a few months and I'm trying unsuccessfully to coax her into a sailplane and she wasn't having it. Some of you may have noticed me struggling with my VR headset lately, and now I've given my wife a couple flying lessons in VR. Being able to learn in the same aircraft used by the Ukrainian Air Force (L-39 obs), in an area strongly resembling the Carpathians where she grew up (the mountains south of Kobuleti) was icing on the cake. She is no longer afraid of flying. Learning about the aircraft a bit, how they fly, how you control them, made a big difference. It's no longer ''unknown and scary''. It was also nice seeing her quietly looking at the mountains getting homesick and remarking how beautiful it is. She said it's not ''almost'' like real, it IS real. My wife is now willing to give the glider a try, and we can also play DCS together a bit now. Thanks to @Barthek for the lovely Caucasus textures she was admiring, @Strikesabre98 for the UAF skin her plane was wearing, and Eagle Dynamics for the simulator she used to experience it all
    6 points
  2. At the moment, I have written more than 400 pages for the AH-64. The cockpit description, start-up, takeoff, landing, and sensors sections are complete. The weapons section is still being worked on. Once the weapons section is complete, I still have to work on the navigation, autopilot, powerplant, countermeasures, multicrew, and aerodynamics sections, which should prove to be slightly "less complicated". Work on the Mirage F1 guide has not started yet. I'd rather not work on stuff in parallel since I know some users are getting impatient about the AH-64 guide.
    6 points
  3. Which is kind of ridiculous. News should be posted in the relevant forums here first. Period!
    6 points
  4. Hello all, just thought I would add my thoughts to the discussion after test-firing all week First of all, in my honest opinion as of right now, the biggest problem with AIM-54 Pk is not the missiles themselves, but rather the AI they're being fired against. The AI seems to react almost too early, knows precisely where the missile is relative to them at all times, and executes nearly perfect evasive maneuvering to counter the incoming missile most of the time. Over the past week of test firing, I've seen some downright ridiculous and inhuman maneuvers from the AI. Obviously this is a problem that affects all missiles in DCS, but has been much more noticeable on the Phoenix (at least for me) being a long-range AAM. Second, while the Phoenix may be slower overall now, 60NM shots against fighters are still very possible (though launching above that range against aware fighters is a bit of a diceroll imo) and 40NM shots at 30,000+ (speed=mach 1) I have found to be quite effective, especially now that the Phoenix bleeds far less speed after going pitbull on a target, allowing for more endgame 'pull'. Third, given my grievances I mentioned earlier with the AI in it's current state, I suspect the AIM-54s could have a higher Pk against targets flown by actual humans, simply due to reaction, choice of maneuver, and lower SA. I have yet to test the Phoenix in multiplayer, but I plan to do some pvp in the coming days and I am extremely curious what results I'll see. One peculiar thing I would like to point out, when I launch an AIM-54C Mk60 at a target 40NM away at mach 1 at ~40,000 feet, the AI will instantly execute a split-s when it goes pitbull and run the the missile out of speed 100% of the time. However, under the exact same conditions, the target will never split-s (though it will perform some other maneuver) against the AIM-54C Mk47 and will hit about 85% of the time. Both Mk60 and Mk47 are close to the same speed and altitude when the AI reacts. Not sure if this is a bug, but I'd be interested to know if anyone else has experienced this? On a final note, the Phoenix may now lack the raw power it had before, but it feels much more refined now (despite still having some remaining polish needed), and with how closely this version mirrors real world data shows the work Heatblur have accomplished with the relatively limited info they have. Well done.
    6 points
  5. First version of moving infantry, armed with the Ak5. Before you comment, I'm fully aware that the moving animations looks like a bad version of stop-motion animated ED-209, haha. But I got to start somewhere.
    5 points
  6. As Stated Previously, When there is news to share it will be shared, Simply asking for updates isn't going to do anything.
    5 points
  7. Lol, are you guys still talking about removable CFTs? It has been what? An year talking about this? The answer is still "NO" I think.
    4 points
  8. I thought Razbam had already said that they will not include an option to remove the CFT (among other things because that would mean a completely new FM)... Then what is actually still being discussed here?
    4 points
  9. I’ll take my warning or suspension for this one… Sorry bignewy ED and DCS certainly have plenty of things worthy of criticism. I’m still upset about the Yak being abandoned. But complaining about module announcements is childish and whiny. More developers brings in more money for ED. This lets them focus more on core development. It’s a good thing. Of course you can whine as much as you want. But there’s no real justification to complain until someone takes money for something. That being said I’m excited for recent announcements. Sure they may be years away. Whatever. I think the Skyraider is awesome because it is HUGE. If you’ve never stood next to one it’s hard to understand the scale of this single engine radial. It’s good to know we’ll have some unique planes coming that I never thought we’d get, like the C-130 and F-100. It’s nice the see the move away for boring Gen4Blu4 JDAM slingers.
    4 points
  10. With all due respect, reactionary comments in the thread are hillarious. Sorry to put it bluntly, but all it ever boils down to is not being able to contain personal hype and manage expectations. 1 - Things take as long as they do, and not less. It is the nature of the beast, and it is good for them to take as long as they do to arrive on our virtual hangars at least mostly properly. We've seen otherwise enough times, and I'm sure great majority of us agree we'd rather stick with this approach. 2 - Not announcing a product early on makes ZERO business sense, especially when it will take years to put it out into the market. It builds interest in the potential buyers, and it also helps avoiding conflicting efforts of multiple vendors (see recent case of Magniute 3 and OctopusG both working on a Su-17/22M4, or the L-39 many years ago) 3 - I do personally LOVE knowing that an aircraft I am very interested in is in development, and love to learn of it as early as possible. Even if I know it is many years ahead of any sort of release. I can start deepening my knowledge of the type, and think of/start working on scearios and/or even lua scripts to use with it when it comes etc. 4 - It does no real harm to anybody if we have to be honest with ourselves. Yes, I know it does get annoying if you let the hype to control the ship, if you know what I mean Hell I have been in that boat, I was screaming "GOOD FOLKS!? SEE THEE, HOW THEY MOCK US! OFF WITH THEIR HEADS! OFF WITH THEIR HEADS I SAY!!" with pitchfork in one hand, torch in the other when waiting for MiG-21 for example and while not as sure of it, I may have done so for a few others too back in the day. But honestly... knowing something is coming WAY in advance, and learning of delays etc later on only has the side effect of disappointment on us, but it doesn't have any sort of malice or real harm behind it. If you've been in DCS for many years, but still haven't learned to adopt the rule of "take an announcement, add a year or two to the estimated release date", honestly it is on you Now, there are outliers like Kiowa and Corsair. But again... c'est la vie... I'm sure devs would want it more than any of us to be able to have it out there and sell it already yesterday, but for one reason or other, they are taking as long as they do. Still, unlike back in 2013-14, it's not like we are lacking for alternatives to keep us entertained until they get here.
    4 points
  11. I actually don't care at all for any off the new plane announcements anymore, my self i'm losing interest with the core game which is what only ED can fix, being with DCS since the days of Lockon I have seen how it all works with news from ED, I really wish for more on what ED are doing with the core game, for example The AI, its pretty bad on the ground using helicopters against any ground based asset, that's its actually become boring playing helicopter PVE missions and this is using all of the excellent missions I can find on user files that some great mission designers have made, the Apache and the Hind have really shown how bad the ground AI really is, we have announcements that AI animations are being updated, what about the logic. The weather, the new clouds were great but the next update that was promised is taking a long time with no information for a long time from ED, the last I saw was a moving GIF that Nineline had somewhere. Vulcan and multicore, as stated still in early testing, I believe we are 3 years on since that announcement with its being worked on as the std line, I get that ther is nothing to show that we can truly see but at least a report every now and then on how its going would be nice. Combined Arms, nothing happening here at all from a game play point of view that I have heard about for a long time, it could be such an excellent module with some time spent on it. The core game needs an overhaul, my group ran 3 servers over the last 4 year, 600 players registered on our Discord, some time sup to 40-50 a night online over all 3 servers (mission dependent mostly PVE) we are currently down to 2 severs and luckily to pull in 10-15 players on a weekend with a good Foothold mission, with a core 5-6 still playing week nights, we are about to drop to 1 server due to numbers, if our players want PVP we send them off to boost the better PVP servers numbers I'm sure all the above is being worked on and no doubt I will be told all in good time.
    4 points
  12. XCNuse your say you are a supporter we appreciate that, but your feedback is constantly negative here on the forum and other places. We understand we can not please everyone and we are not trying to but you have given your feedback many times now. If you dont understand why we are giving the third party news early even after I have explained it here in this thread there is nothing else I can say to you that will help.
    4 points
  13. The ''roots'' are ''the best possible at the time''. For its Era, FC3 was 'high fidelity'. MAC will be a completely separate product providing more or less what you want. DCS is about high fidelity aircraft and always has been. You will notice the distinct absence of production of ANY ''low fidelity'' aircraft since DCS came into existence. This IS its ''root''. The only reason FC3 was ever incorporated at all is because there was a distinct lack of variety at the time, a lack since rectified.
    4 points
  14. Serious question though; don't we end up in quite literally the exact same place we basically just were? Projects are locked up and key tossed out, and when that case is handed to a developer who gives zero news.... we end up being fed information about future releases. This system is still just as bad as it has always been..... We need to be getting news of IMPENDING RELEASES. Meanwhile, we're sitting here with knowledge of all of these third party developers, and what they're supposedly working on, but... they're free to do as they wish when it comes to communication. My perspective: I'm a supporter of DCS because there are expectations of what is being sold. I'm familiar with those expectations, and like knowing these things.... things other flight simulators have never and likely never will do. It's unfair [to me] that we're informed of products that MIGHT not even release! What's the point of sharing this information? We've got companies like Polychop who have had the Kiowa lock and key for how many years now? And what's the progress to show? We've got companies like Miltech/Leatherneck, who have been working on the F4U Corsair FOR FIVE YEARS!!!!!!!!! We've got companies like Heatblur who have the A6 wrapped up somewhere under covers, that's allowed to be in trailer videos, and was announced 4 years ago. The list can keep going because we know about 20+ ongoing projects including aircraft and scenery now.... Simultaneously, none of these companies are willing to give a status update but MAYBE once a year, if it's even on topic! It's "fun" and "exciting" to hear about these potential products to DCS. But ED.... take a step back. Seriously. What's the point of having the same issue you did 10 years ago, talking about all these products release, and then they never come? You should genuinely be forcing your third parties to be giving quarterly updates (that is LEGITIMATELY not asking for much), and we should be fed that. These recent newsletters are getting out of hand. Some of these are frankly being shared far too soon... Knowing full and well that these third party developers are doing this as side jobs. They cannot be trusted to release; so why should your customers be informed about them? The news up eventual releases is going to give a majority of your newer and younger customerbase whiplash and walk away sooner than you think when they realize that the stuff being shown off, won't be around for years to come. It's a dangerous move when showing this younger customerbase who are generally gamers, not flight sim enthusiasts, "DLC" that may or may not release. It's still equally confusing to th ose of us who have been around for a long time, imagine how people unfamiliar will react? These newsletters have turned into clickbait...
    4 points
  15. RELEASED! The first post has been updated. Enjoy!
    4 points
  16. Greetings @everyone today we have a new video showcasing the new cockpit made by @Yatsieand the new EFM made by @Fatspacepanda that was recently pushed to our testers. This update adds more force and moment coefficients in Pitch, Roll and Yaw axis and control surfaces, gathered with VSP Aero. The result is an unstable aircraft at subsonic speeds, meaning the nose pitches up in correlation with angle of attack. A flight control system capable of controlling both angular rates or normal load (depending on flight envelope) has been developed alongside the flight model. A RM12 engine model from Gasturb14 is currently being implemented. Future steps are ironing some issues, adding functionality and tuning the gains for the control system to achieve the correct feeling and responsiveness. That's all for now stay safe and check six
    3 points
  17. Yes and no. Keep in mind: the announcements are managed. The hype is managed. The dangling of shiny objects in front of the customer's eyes is managed. The whole "Oh my god you really want to buy this!!!" salesmanship is managed. It's all part of a business plan to sell stuff. And that's just fine. But it is unreasonable to play that game with the customer - especially to play it over and over and over - and then in the next breath tell the customer to keep his pants on, show some patience, and quit asking when things will be ready. You can play that game, of course, but it comes off looking... less than great.
    3 points
  18. That's a clear-cut case of "it depends". Obviously, you first need to enable the aircraft's Situational Awareness Datalink (SADL), which is very inappropriately labeled "JTRS" on the AHCP. Once the jet is up and running and the HMCS is on, that's it. Now, it depends on a bunch of factors. Many AI flights will show up without a problem, including A-10C and F/A-18C (not sure about the F-16C). For player controlled aircraft in Multiplayer, only A-10C (no matter if legacy or A-10C II) will show up, but F/A-18C and F-16C won't. AH-64D use their own kind of datalink and don't show up on the HMCS at all, regardless if they're player-controlled or AI (the AH-64E uses Link 16, but we don't have the Apache Guardian in DCS yet). The problem here is that SADL (used in the A-10) is not compatible with Link 16 (used in Hornet and Viper, IIRC) and needs a gateway, like an AWACS, but DCS doesn't seem to make that distinction, so in some cases aircraft with an incompatible type of datalink still show up in our A-10, in other cases they don't, and I'm not aware of any workarounds. So it's a mix of an actual real world problem together with a DCS-related problem.
    3 points
  19. I love Silver Dragon's frequent posting of news, but I agree with you here. Facebook is pure trash and I keep getting kicked off Twitter , so they are useless to me. And to many others I would imagine. News should be here.
    3 points
  20. Where I'm at right now I'd just like to see some of the modules in the works come out, and to see Eagle focus on improving DCS core.
    3 points
  21. The other day NineLine said multicore is in internal testing at the moment, and ED have stated previously Vulkan will come after Multicore.
    3 points
  22. ED has stated several times that there will only be full fidelity modules in the future. In any case my vote is none. MAC/(FC4) will come eventually, and will take care of the need, will probably get that too.
    3 points
  23. Why would the pilot or RIO know the missile's speed during the shoot? They'd need to recall their altitude, airspeed, target alt/airspeed, closure rates, angles, all that. There's so much more to this than someone off the cuff saying "sure it was Mach 5 capable" when even NASA documents showed that the missile wasn't quite hypersonic and they would/did make changes to get it to be hypersonic. They used the Phoenix because they believed it had the potential and there were stocks of them available, not because it already was a 5+ missile. Now if you find the guys from PMTC, VX-4, Pt Mugu, etc. that were actually doing Phoenix testing and could recall shot profiles and they got to see the instrumentation and after action reports, that might hold a bit more water. Because fleet pilots got to shoot missiles sometimes, but that doesn't necessarily mean "test fire" and "testing" for the purposes of gathering data. Just because I went and qualified at the range doesn't mean I can tell you the actual muzzle velocity my M16A2 was laying down, round per round, from a random batch of M855. They only gave us a general number and instructions for how to make and log our adjustments. The guys testing the ammo and developing it at Aberdeen or Dahlgren are the ones to tell you the velocity, BC, chamber pressure averages. The guys shooting them might tell you what their holdovers/DOPE was and how it did in the field.
    3 points
  24. Captain Bob, I believe that it's you that needs to get his facts straight. The AD/A-1 had dive brakes on the sides as well as one on the belly and as for which ones served in Korea and which ones served in Vietnam, the later model AD's that the Navy put in storage after Korea were picked up by the Air Force and were the same airplane. They just got renamed courtesy of Sec Def R McNamara. Some of the versions had the dive brakes removed because of their changed mission such as ASW or AEW or Night Interdiction. It went from the AD-1 to the AD-7 with many changes in systems and equipment over time. This is from Wikipedia: AD-6 (A-1H) Single-seat attack aircraft with three dive brakes, centerline station stressed for 3,500 lb (1,600 kg) of ordnance, 30 in (760 mm) in diameter, combination 14 in (360 mm) and 30 in (760 mm) bomb ejector and low/high altitude bomb director; 713 built I doubt very seriously if you could distinguish an AD-4 that flew in Korea from an AD-6/A-1H that flew in Vietnam.
    3 points
  25. Also I think it's a modern H, looking nothing like '52's of the Vietnam era. I believe an AI model should be made for the 52D, with the "Big Belly" configuration, that allowed lots of extra ord on the wing pylons... smooth chin, big shark's fin stabiliser... painted black underneath.... Agreed!!
    2 points
  26. Skyraider is coming; now is the AH-1G time!
    2 points
  27. Look very cool, good game ! The animation is still better than ED's annimation xD
    2 points
  28. Only if you use the old clouds. Select NONE for the presets and, then, use the sliders to set the cloud base and thickness for the old (very old) clouds. Finally, select "10" for the density.
    2 points
  29. You'd be hard pressed to find a single fact in all of his 4.6k posts. I'm not trying to tell the mods how to do their jobs, but the fact that there have been no consequences for sabotaging countless serious discussions is beyond my comprehension. His delusional ramblings are basically forum poison.
    2 points
  30. Oh, I'm sure I'm guilty of something, so don't feel bad about including me. While there is no concerted effort to stop people from asking when a module will be released, there is often a thundering silence as to information being offered in the form of a response. For example, if I ask when the Skyraider will be released, I will get either no answer at all or at best a diplomatic brush off. If I ask if the Skyraider will be released within two- years, I will get the same answer. If I ask if it will be released within four-years, I will get the same answer. And thus the issue. If the shiny object is dangled in front of hungry eyes today, and we are directed to look at all the lovely angles and bodacious curves, and get all hot and sweaty about it... the inevitable question will arise; "When?" A response of "We have absolutely no idea and we wouldn't tell you if we did" does not exactly elicit a great deal of love. The responsibility for the managing of expectations in this case involves both parties.
    2 points
  31. Many thanks to [MVP] Indianashane from our community who has been spending time designing up our original F86 Sabre cockpit accessories into 3D so that new replica units can be manufactured. His latest work is the Canopy Declutch handle, which is located to the top right hand side of the instrument panel. We will be setting up an online store shortly, where each of these will be listed and you can purchase them - more on this when we get it live.
    2 points
  32. Well, the video answers this: To train for air defense sorties... without CFTs. Something you said doesn't happen
    2 points
  33. The way I've come to look at module/map announcements, is as a long term roadmap for DCS. I may get hyped if it's something I really want, but as the vast majority here I'm well passed my teenage years, and I know how to wait. So I remember it'll take years to come out, am happy to see what's to come and wait. The only thing I'd recommend, to manage expectations of newcomers would be to add a "ETA: TBD" at the end of the announcement trailer. So it's clear the release is a bit further down the line. That said, I'm not much of a prop plane flyer, but the skyraider does seem awesome. I'll definitley keep a closer look at it, especially if it gets torpedos. Can a Nimitz or Forrestal handle it?
    2 points
  34. @XCNuse Apparently you have a serious problem with news and announcements. The simple knowledge that something is in the works or even just planned makes you think it's some kind of blood oath. But you're wrong. They don't owe us anything and there's life beside DCS, you know? Please don't project your own feelings onto young and new players. They don't care as much as you'd think about the distant future of the game they have just started playing. Devs already explained their point and keep reminding (to no avail) that modules and core development take years. As we all see the business is going pretty well, don't worry.
    2 points
  35. We don't have modern Hornet, but year 2004-2007 standard. Some player made MOD - why not.
    2 points
  36. Added Bronco OV-10A mod stuff: - Wiki (https://github.com/asherao/DCS-ExportScripts/wiki/Bronco-OV-10A) - exportScript lua (https://github.com/asherao/DCS-ExportScripts/tree/master/Scripts/DCS-ExportScript/ExportsModules) - WIP streamdeck profile (https://github.com/asherao/DCS-ExportScripts/tree/master/docu/StreamDeck Examples)
    2 points
  37. No because the F/A-18 we have is not a Super Hornet and because ED modeled one from 2007. There is no official Super Hornet. You would have to ask the mod creators but pretty sure then dont have the needed tools to change that. Beside that, the colour is only beeing tested and wasnt intruduced into the airforce yet.
    2 points
  38. Here's hoping that this will be a beast. From other mods we've seen API available for: Radar FLIR/SHKVAL RWR Multicrew With the above, the iglas, possible MWS, and (I hope), the capabilities to interact with black shark laser channels and data link, we can finally give some more love and expanded capability to the shark with this thing.
    2 points
  39. At 30 miles you should be shooting a Sparrow. You absolutely need to be shooting longer; the chart-matching Phoenix is like a fine wine- you have to let it breathe. 1v4, just because I have the mission ready, 14A with 4x 54C-60s against 4x veteran MiG-29s. 3 for 4, with a dropped lock at 40 miles. Shots were taken between 64 and 58 miles. Tacview-20220910-145137-DCS-1 v 4 Mig-29s Long Range New BVR Test.zip.acmi
    2 points
  40. I've created a proof of concept for extensions, which should make it fairly simple to add new buttons to the Scratchpad (way simpler than my first take on that topic). More details are available here: https://github.com/rkusa/dcs-scratchpad/pull/35 If you want to try it out, you can download it at: https://github.com/rkusa/dcs-scratchpad/archive/refs/heads/extensions.zip The following screenshot shows some example extensions:
    2 points
  41. ED modules have had the same issue in the past, I wouldn't be surprised if others did/do too. In this case at least it's 80km/h or so, not 300, and the 21 has some hard limits that stop you achieving warp speed 9. Needs fixing at any rate, so hopefully that can be done without too much delay. I'd recommend detailing your findings on the M3 bugtracker to make sure it gets seen, as often forum threads don't. e/ APU-60-II was mostly reserved for MiG-23 and occasionally 25, IIRC, as there were never enough in supply to meet demand. Photos of them in use on 21s are relatively uncommon and usually foreign (I've seen them on Finnish and Indian 21s). It's hard to say what limitations there were to prevent loading 8 missiles but it's possible that the reason wasn't just wiring, but perhaps negative impacts on stability particularly at low speeds, as the 21's manual is full of such limitations for pretty much every store except the existing air-to-air missiles and rails prior to R-60 being brought across to the 21. R-60 itself didn't pass state trials until after the bis was in production and so it's unlikely its launch rails would have, either. Early prints of the aircraft manual make no mention of the weapon at all.
    2 points
  42. I would hope that the DCS community at large has a much greater maturity level and understanding than a 5 year old. I get it's just an analogy, but the premise of that statement to prove a point is flawed. Nobody here should have the maturity of a 5 year old, nor is making a complex simulation of any aircraft for a consumer level video game something that can be completed in one afternoon (obviously).
    2 points
  43. Go tell your five-year old you're making great big delicious gooey chocolate chip cookies, show him pictures of big plates of them, dozens of cookies all piled up ready to be devoured, and when he's all excited and asks when they'll be ready, answer "Maybe when you're seven or eight. No one knows." Yeah, see what that gets you.
    2 points
  44. New Supercarrier Airboss station and mission breifing room....
    2 points
  45. Dear all, I recently had both the luck and opportunity to sit down with @Enigma89 for an interview. I very much enjoyed being his guest, and would like to express my thanks here again! I found his approach very refreshing and interesting, and while I am sure I talked too much as usual, I hope those of you who are interested, enjoy it, too. This time we talk less about day to day development, roadmaps and updates and more about some of the thought process that stands behind - at least some of - the things we do. We also talk a bit about the history of Multiplayer in DCS in general, the role of Cold War and the Cold War Server in it in particular, and how that affects us as developers. Big thanks again to Enigma and the entire Cold War Server and Community.
    2 points
  46. A-1H is a presale buy for me for sure. I don't need Vietnam to make that an enjoyable module (doesn't mean we can't get it, but what a fun COIN aircraft for fictional scenarios). Best of the new announcements since the Kola map. I think this is fair. So many announcements lately I can't believe all of them (or maybe most of them) are anywhere near ready for OB. I'm in the minority, but I do prefer announcements made closer to when a module is near completion to avoid the overhype.
    2 points
  47. I suppose that's part of my point; should it be us managing expectations or should it be ED managing a reasonable time frame for announced modules? At this point someone could announce a B2 bomber and a complete map of Asia for Q3 2028. Everyone cheers, the forums light up, and then... what? ED is building hype with these announcements, and I'm all for it. I love my DCS toys. But maybe a balance between our expectations and what they can reasonably deliver within say, two-years?
    2 points
  48. Hello everyone! Since we started making our slew upgrade, one thing that has come up several times is the limited axis update rate for the slew axis. It doesn’t update as quickly as the other throttle axes, which has meant that even after upgrading the physical slew the axis still doesn’t work as well as it could. This was a limitation inside the throttle firmware, so couldn’t be changed by the slew upgrade directly. Other the last few months I have been working on reverse engineering the Warthog throttle firmware, so I could modify it to increase the slew axis speed. I am pleased to announce our first custom Warthog throttle firmware version, which removes this limitation and runs the slew axis at full speed! Delta_Sim_Fast_Slew_v100.tmf is released free of charge, and is compatible with all our slew upgrades, including the force sensor. Please find the firmware file and install instructions attached for download. You will need the Thrustmaster firmware update tool installed to do the update. This comes with the Thrustmaster Warthog driver package, so you probably have it installed already, or it can be downloaded from the Thrustmaster website. This has been a lot of work, so I hope it will be useful to someone Delta_Sim_Fast_Slew_v100.zip
    2 points
  49. There you have it, would be just one would you have checked just once!
    2 points
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...