Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/16/25 in Posts

  1. As soon as I have news about a patch date I will let you all know. It very much depends on QA results. thank you
    5 points
  2. Hi, I want to thank ED and Winwing for their incredible work. I started with flight simulation when I was very young, at about five years old. I didn't understand anything at all, but I really liked it. That was with Lock On: Modern Air Combat, and I was just playing with a keyboard and mouse. Soon after, I switched to Pacific Fighters and Tom Clancy's H.A.W.X, which were more accessible for me because they were much more arcade-style. When I was seven or eight, my parents took me to an airshow at a military base near where I live. It was fantastic, and it made me want to dive deeper into simulation. I searched online and found DCS World. My parents and I bought a T.Flight Hotas X, and after I downloaded DCS, it reminded me of the simulator I had played before—I remembered Lock On. I flew with the T.Flight until I was 13 or 14, then I bought a second-hand X55. It was great, but not as good as I had hoped. I then bought some modules like the Su-33 and the F-15C. Years later, I added the F/A-18, and a few weeks (or maybe months) ago, I ordered the FF Fulcrum. Eventually, the throttle of the X55 broke, so I replaced it with a Thrustmaster Warthog throttle. Then, wanting a more premium stick, I bought the Winwing Orion 2 F16EX. The combination of the Warthog throttle and the Orion 2 stick is amazing. The TM throttle is very good, but the Orion 2 stick is way better than I expected. I really love it; it feels truly premium. A few months ago, I saw some information about Winwing's new FFB base (the Cyber Taurus). As a huge fan of Russia and its military, due to my family and cultural background, I was already really hyped for the FF Fulcrum. Then, during your live stream at FSExpo, you announced a MiG-29 stick and throttle grip. I was amazed—I couldn't believe it! I was waiting for a good reason to switch my throttle, and I finally found it. Thank you for this. You can be sure that I will be buying your MiG-29 hardware and your FFB base. I also wanted to thank ED for this simulator, especially DCS. It is something truly outstanding. I heard that Winwing's hardware will be linked to DCS like no other device. I don't know what that means. I am a Computer Science student and can't quite picture what that entails. Could you please explain it a bit? Thanks. To both ED and Winwing: you have brought me closer to my dream of flying a fighter jet. This dream is almost impossible for me because of my poor eyesight; I can't even join the military or become a civilian pilot. You both make it possible for me to be in the place I want to be, and I thank you for that. Finally, I also wanted to thank the community. Even if there have been some tensions in the past (e.g., with Razbam), you are all still here to support the simulator. Like everyone else here, you are driven by a passion for simulation, and I thank you for that as well.
    4 points
  3. This is a skinpack compiled for use by the "Iron Curtain Virtual Aviators" lead by 526th Blade who provided much of the research, editing and advise. Thank you sir. The four aircraft presented, 68-0467, 68-0526, 69-0244 and 69-0260 are depicted as they were at Ramstein Air Base circa 1983 and are rendered as close as possible to historical photographs. The folder exceeds the User Files size limit so it can be downloaded here: https://www.dropbox.com/scl/fi/gc6zjlo9tiokvkwklfxpb/USAF-526th-TFS-Skinpack.zip?rlkey=s6u4u88fnvzgn30vqzulvamnk&dl=0 The zip is designed to be OVGME friendly. Just make sure that all five folders including "USAF_526th_Common" are placed in your "\Saved Games\DCS.openbeta\Liveries\F-4E-45MC" folder.
    4 points
  4. I thoroughly enjoy DCS and I realize that by even replying to this thread (that I very occasionally check in on) that I too am making myself part of the problem. But honestly it needs to be said... are people serious? The level of armchair legal eagle action here is pure comedy. I assume most of you also have pretty busy lives and finite amounts of time to spend on things you enjoy? Is this thread really worth some of the energy expended on it? Imagine repurposing that energy to actually do some of those enjoyable things... like even, say, DCS.... or touching some grass FFS. Honestly, mind blowing.
    4 points
  5. Older HARM's in DCS would be great addition, they have similar guidance, but worse kinetic performance make them more fitting into Cold War scenarios, both as player modules, but also for AI planes. Range diffrence to current 90's HARM C is substantial
    3 points
  6. It looks like a bunch of us were working on this... GTFreeFlyer's above, with 23 Breakers/Fuses added... F4U-1D.lua
    3 points
  7. Hi VampireNZ, The Up-Short and Down-Short commands are provided as priority actions. The Up-Short (PHS SEARCH) command is meant for the CPG to stop his current task and immediately search where the Pilot is looking, used to rapidly get the CPG onto a target or enemy position the Pilot has visually spotted. The Down-Short command orders the CPG to stop tracking his current target and, if he is firing on it, to cease fire. Obviously this is an important priority action to order the CPG to cease fire, regardless of what the CPG is doing. However, more critically, the Up-Short and Down-Short commands must remain available, regardless of what the CPG is doing, to be able to command these priority actions. There are several conditions in which the Down-Long command contextually changes based on the current task George is performing. Therefore, if these commands were swapped as you ask, this would prevent the player from being able to immediately command George to stop firing on a target with a single command at any time that would be needed, which is not desirable. And regarding the delay when pressing Down-Long, the command itself is commanded with a long press >0.5 seconds as stated in the manual, but the actions George must perform may take several seconds after the command is issued before a Target List is presented. George emulates a human crewmember, so there are many actions that do not readily or apparently produce an immediate result. There is a lot more logic and commands that we cannot put into a single Mini-updates forum post, which was meant as a highlight of the key features we are adding. The George AI CPG section of the manual grew from 6 to 22 pages, so there is a lot of logic that we worked very hard to keep intuitive and easy to use, that may not be obvious from that Mini-updates post.
    3 points
  8. Many thanks! I just released it: F4U-1A Corsair (BuNo 17649) White 1 ''Big Hog'' flown by J.T. Blackburn, VF-17, November 1943.
    3 points
  9. Yes, please fill out this accident form: I would definitely recommend this AI to a friend or family. (Tick a number below) 10 10 10 10 10 10 10 10 10 10
    3 points
  10. I'm going to play with this sarcastically. I'm going to parody the ideas in Comic Sans. Once more, its not personal, I'm sure I'd like you as a person, just the ideas don't sit well with me and its got to a point where its a bit funny now. Heres the sracasm highlights. We see an SFM table in the coremods of the plane lua. This means that the AI uses this when calculating its dogfight state table. We know that the existence of the SFM means we only need to look at the actual model, not how its executed or used in the software. The fact that the table exists means DCS uses it. It doesnt matter that the C code is encrypted and unreadable, its only the LUA. And anyway, I can read the program, I know things for sure. Just use a stopwatch. We can rule out misuse of the SFM data because that doesnt make sense. Why would a game need to force the AI to do something at all, when it flies realistically? Stupid. There is no evidence of the AI not using the SFM data. Apart from the times when it doesnt, like when its following the player in line abreast perfectly and can turn at the same time and aero brake stop 100kts in 1 second. But this doesnt actually matter because we know because of the SFM data that the AI doesnt behave like that during dogfights. SFM = dogfight and climb. Everything else can be scripted, thats ok, but we know for sure its not breaking this rule. We can prove this by looking at when the AI isn't doing something stupid, like climbing. If we examine the climbing then we know for sure this must apply to the dogfight data. When we look at tacview, we can see the moment to moment forces and speeds and alpha recorded for the AI. It's OK to see things here that are within the SFM data. Look, the plane is going at 500kts straight up. That's perfectly OK, so the entire fight must be fine here. I don't need to see the plane doign these 500kt climbs again and again, because its just flying perfectly, there is no issue over time with the energy state. We havent seen any evidence of the AI using scripted behaviour. At least not between 3.30pm and 3.45pm in the afternoon of June 12th 2025. The AI would tell us he is using scripted behaviour through the comms menu. We haven't seen the Scripts folder of the DCS application where the AI routines are kept. At least, the ones that apply to normal flight. The dogfight ones got moved some years ago to protect people keep on arguing about this non existent problem because they are just bad fliers and need to stop wasting their time looking for excuses. We know the DCS AI is very good so the routines can be shared from MiG pilots to the Luftwaffe, so they can use boom and zoom too. Its a special trick, it might look the same, but actually each plane type, jet or prop can use the identical vertical manouvers and energy. But the SFM is what decides how it really is different. We also know that ED eventually gave up their special Flight model in development after realising it was pointless. It was pointless because the AI already was perfect. Why develop something to make it different when it is already the best? Also we know a lot of things about planes and so we've marked ourself as the solution very early on in this thread. Quite simply, they dont understand about SFM, its only for aeronautical engineers and high IQ. So being the solution saves time and is more effective in conversations.
    3 points
  11. Best video I could find is this one, uploaded 11 years ago, but can't know when it was actually recorded (must be some time before upload time but no info when) so it might be the same as our pod or some different version. Image quality seems better than what we have but I'm not sure we have the same version. Symbology suggests its mounted on F-16.
    3 points
  12. I think, the most realistic benefits from using two computers for DCS if you set up one as dedicated server and play on the other as client. That would take "some" load from the client if you happen to run a big mission with plenty AI-units etc..... Both computers need to be performant though....
    3 points
  13. That's you telling people how new you are to DCS and/or the forum without telling you're new Ah the entertainment value of this thread is priceless. Please keep going!
    3 points
  14. Per manual Highest takeoff speed: 375 kmh Highest landing speed: 330 kmh Limited by strength of tire Braking speed: 215 kmh
    3 points
  15. 300 km/hr is too fast. And that you need to do that suggests that you’re landing too hard as well. The fastest speed I’ve ever touched down was 290 and I was seriously overweight. With about 60% fuel and 4AAMs you should be touching down in the 270-280 km/hr range. With around 1,500 kg fuel remaining and 2 AAMs, I’m usually touch down in the 250-260 range. You need to come in flatter in this bird. Otherwise, you will end up landing too fast and too hard. EDIT: Just attached a TRK file landing at Kutaisi with 6AAMs and a bit less than 60% fuel (roughly 13,700 kg gross weight, I think). Touchdown speed was 270 km/hr. Note the slow descent rate at the end. Just before crossing the threshold you should begin slowly pulling the stick back. Just don't let your nose pitch higher than 10° (11° at most) or you might cause an engine strike as you touch down. In the end, it'll be just about in your lap as your wheels touch. Mig-29A Kutaisi Landing 13700kg.trk
    3 points
  16. COMING SOON In this short DCS: F/A-18C video, we’ll discuss the Terrain Avoidance, or TA, radar mode. This is the last primary radar mode of our F/A-18C. In the August DCS update, we plan to add Multi-Sensor Integration, or MSI, AWACS surveillance track files that can be set as an L&S or DT2 without the radar transmitting. This will allow stealthy target engagements with AIM-9 and AIM-120. This will be the subject of a later video. Terrain Avoidance, not to be confused with more modern automatic ground avoidance systems, displays two altitude clearance planes on the AG radar format page. The format displays three colors based on the terrain elevation ahead and is restricted by radar shadows. It’s enabled from the air-to-ground radar mode options, TA. When the aircraft is in level flight or climbing, the radar will scan the terrain ahead to determine which terrain is near or above the aircraft’s current altitude. Terrain ahead that is above the aircraft’s current altitude is displayed in bright green. Terrain that is within 500 feet below the aircraft’s current altitude is displayed at a lower-intensity green, and elevation ahead that greater than 500 feet below the aircraft is black. Note that terrain ahead in a radar shadow will also display as black. If the aircraft is in a descending flight path, however; the radar antenna will depress along with the Velocity Vector in the HUD. The radar color scheme remains the same, but this will ensure the pilot can see which terrain will obstruct the flight path when descending toward the surface. The display has a fixed azimuth of 70-degrees and range selections of only 5 and 10 nm. The minimum range displayed is 1.6 nm. To the left and right of the terrain returns are static wedges that allow you to adjust brightness and contrast. While certainly not as useful as other radar modes, this can be a useful feature when flying low at night or in bad weather to avoid a controlled flight into terrain. NOTE 1: The Iraq map was used for this video. NOTE 2: Please keep on topic to the subject of this video. I cannot comment on 3rd party products. NOTE 3: The F-16 in real-life and DCS has no such mode. But a similar mode is also coming to the AH-64D.
    3 points
  17. In the next DCS update, George AI Copilot/Gunner (CPG) will be receiving a significant upgrade, along with some improvements to his existing logic and behavior, in an effort to make him more realistic, interactive, and capable. It is important to note that no changes have been made to any existing AI Interface commands or control functions. Rather, additional commands have been added to the AI Helper Controls (Left/Right/Up/Down) when the AI Interface is displayed and set to NO WPN, and the Consent To Fire command has been modified as a contextual, multi-purpose button. In the graphic below, the new AI Interface is shown, with the new commands identified. New search tasks (explained below the AI Interface graphic) may be configured using the Left-Long and Right-Long commands while the AI Interface is set to NO WPN. The function of the Consent To Fire command under the current conditions is displayed in the center of the AI Interface, with the short press (<0.5 seconds) function displayed above the long press (>0.5 seconds) function below it. It is worth noting that the Consent To Fire commands may still be used without displaying the AI Interface. For example, if the player wishes for George AI CPG to begin performing an Area search, a long press of the Consent To Fire button may be used without the AI Interface displayed. However, to select a different Area search, the AI Interface will need to be displayed and set to NO WPN. New Search Tasks Up until now, George AI CPG could only be commanded to perform a direct, momentary search for targets along the line-of-sight of the Pilot’s helmet or the TADS sensor turret, and would rank those targets based on threat priority (i.e., air defense units would be at the top of the list). The player may now choose from 7 additional methods for George to search for targets, facilitated by the new changes in the AI Interface. Direct Searches. These are two searches that George was already capable of performing up to this point. PHS SEARCH - George slaves the TADS to the line-of-sight of the Pilot Helmet Sight (PHS) and performs a momentary search for targets. Targets are ranked by threat priority. TADS LOS SEARCH - George performs a momentary search for targets along the current TADS line-of-sight. Targets are ranked by threat priority. Area Searches. These searches allow George to proactively search for targets in a designated area or based on FCR target locations, visually identify FCR targets prior to an engagement, or perform battle damage assessment of engaged FCR targets after an engagement. FWD AREA - George slews the TADS in a 90-degree search pattern directly in front of the helicopter and continuously searches for targets. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. PHS AREA - George slaves the TADS to the line-of-sight of the Pilot Helmet Sight (PHS) and then slews the TADS in a 45-degree search pattern centered on the PHS-directed azimuth in relation to the helicopter nose and continuously searches for targets. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. FCR TGTS - George generates a Target List based on FCR target data obtained by the onboard FCR scans performed by the player or received across the datalink via FCR TGT Report or RFHO. George will enable C-Scope and attempt to identify the FCR targets highlighted in the Target List. If the target cannot be seen due to visual obstructions, George will verbally announce it. If the target is destroyed, George will verbally announce it and remove the target from the Target List. OWN PFZ - George slaves the TADS to the PFZ assigned to the ownship and continuously searches for targets within the geographical boundaries of the zone. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. ACTV PFZ - George slaves the TADS to the activated PFZ and generates a Target List based on FCR target data obtained by the onboard FCR scans performed by the player or received across the datalink via FCR TGT Report or RFHO. George will enable C-Scope and attempt to identify the FCR targets within the geographical boundaries of the zone and highlighted in the Target List. If the target cannot be seen due to visual obstructions, George will verbally announce it. If the target is destroyed, George will verbally announce it and remove the target from the Target List. Point Searches. These searches allow George to search for targets in the vicinity of a TSD point or the FCR Next-To-Shoot (NTS) target after the Player has Linked the TADS to the FCR in the Pilot seat. POINT - George slaves the TADS to the selected TSD point to perform an indirect rocket attack from behind cover; or may be commanded to adjust the TADS field-of-view setting, toggle the selected sensor (FLIR or DTV), or fire the laser, to assist with performing reconnaissance. If subsequently commanded to search for targets, George performs a momentary search for targets. Targets are ranked by geographic proximity to the TSD point, regardless of unit type. LINKED - George may be commanded to adjust the TADS field-of-view setting or toggle the selected sensor (FLIR or DTV), to assist with performing visual identification or battle damage assessment of the FCR NTS target. If subsequently commanded to search for targets, George performs a momentary search for targets. The closest target that matches the classification of the FCR NTS target is ranked as the first target in the Target List, and all remaining targets are ranked by geographic proximity to the NTS target symbol, regardless of unit type. New capabilities and procedures George must be commanded to perform start-up procedures if spawning into a cold start AH-64D. However, George will assist with more of the start-up checklist items such as powering on the FCR and RLWR, and will verbally announce to the player as he completes major items such as boresighting his helmet or when the FCR has finished its power-on sequence. George may also be commanded to perform the relevant shutdown procedures. George is now capable of engaging multiple targets in sequence. When presented with a Target List, the player can select multiple targets from the list, as shown below. In this image, the player has selected 4 targets from the list by pressing the Consent To Fire button as each target is highlighted in the list. If the player presses Right-Short to command George to begin tracking a target that has been added to George's "shoot list", George will slew to the first target in the list (tagged as 1). If the player presses Right-Short to command George to begin tracking a target that is not added to the shoot list, the shoot list is canceled and George will only track/engage that single target. As before, George will still wait for a Consent To Fire command before engaging the target if set to HOLD FIRE. However, once his current target is destroyed, he will automatically slew the TADS to the next target on the shoot list and wait for another Consent To Fire command before engaging the next target. If set to FREE FIRE, George will begin engaging if engagement parameters are met, and then automatically slew to the next target once the first target is destroyed, and immediately engage the next target (again, assuming engagement parameters are met). When tracking a target and GUN or MSL is selected, a short press (<0.5 seconds) of the Consent To Fire command will direct George to fire his assigned weapon as before. If the Consent To Fire command is pressed and held (as signified by the ADJ+ label in the center of the interface), George will adjust the crosshairs onto the center of the target to prevent laser overspill beyond the target itself, and then re-establish an auto-track on the target when Consent To Fire is released. However, the player should fly in a stable manner while George is commanded to refine his aim using this function, which is why the player has been given a command to coordinate the timing of such actions. Improvements to existing logic and more verbal communication The existing logic of George AI CPG has been improved, with more realistic behavior and procedures. For example, if the player has set the RF MSL PWR to OFF, and the player subsequently commands George to use RF missiles, George will set the MSL PWR back to AUTO. George will also verbally communicate to the player what is required for him to perform a command or provide verbal feedback if he is unable to perform a command. For example, if George needs the player to maneuver the helicopter into launch constraints before he can fire a missile, George will verbally request the pilot do so: "Get me in constraints". Previously, George would not fire an AGM-114 missile if any Performance Inhibits or Safety Inhibits were displayed, even if the Player pressed the Consent To Fire button. This would lead to confusion as to why George was announcing "Engaging" but did not actually fire a missile. Safety Inhibits cannot be overridden, but a Performance Inhibit may be overridden if George pulls the weapons trigger to the 2nd detent, which he will now do if ordered to do so. If any inhibit, Performance or Safety, is displayed when George is ready to fire a missile on his current target, George will announce "Constraints" to request that the pilot maneuver the helicopter into appropriate launch constraints. When and if this occurs, the player may now order George to override a Performance Inhibit by pressing the Consent To Fire button (except BAL LIMIT if the target is out of range). However, it is important to note that the presence of a Performance Inhibit increases the possibility the missile may not hit the target, either due to failure to acquire a laser or not being able to maneuver to the target. Therefore, the player (as the "pilot-in-command" of the helicopter) must be judicious with this command when a Performance Inhibit is displayed. This gives the player the freedom to make tactical decisions regarding when it is appropriate to override an inhibit, at the risk of expending a missile without striking the intended target. An updated DCS AH-64D Early Access Guide will be included in the next DCS update to fully describe these new functions and features in detail. We hope that these new features to George AI CPG will provide a much more engaging gameplay experience in the DCS: AH-64D.
    3 points
  18. Hi, I have been working to finish this bad boy here. It's working, basic systems, cockpit, most instruments, and basic weaponary It does an EFM and curves adjusted to be close to the Vampire, work in progress Download link soon
    2 points
  19. Hi folks sorry for long delay ... "broken pc is my excuse" its out now , follow this link https://soloist.ai/jafaproductions . BE WARNED - The initial version is NOT compatable with any other sound mods at all and will be a manual install only. Cheers Jafa.
    2 points
  20. Not to seem uungrateful of the coming changes, but I would love to see the commands for 'De-Slaved' and 'TADS LOS Search' swap positioins on the interface as per attached pic. This just seems logical to me to have both the instant 'Search' commands be controlled by the short-press positions, and essentially the two 'Disengage' commands that you are more likely to use after engagement be both linked to the long press positions. I mean having 'up-short' for PHS search, and 'down-short' for TADS search seems ideal? I have also lot count of the number of times I have wanted to quickly re-engage a target group, only to have George de-slave the TADS away entirely, requiring me to try and re-position my cross on the target area again to re-search! This forced me to always have the VID page up with TADS and just hold down till I see the zoom level change (which seems to be 2-3 secs, not 0.5 as per the manual), to know for sure he was going to search again. This will be mitigated of course with the upcoming changes, but my first points stands - it just seems logical. I would also be interested to hear why the devs decided on the current layout, as there may be a reason I am not thinking of - perhaps keeping to two 'Slave TADS to...' options the same 'short' action, which looks ok on paper but is not really how it operates in practice?
    2 points
  21. I wouldn't call it "all is good". It sucks being halfway through a mission and then it closes out and you get to start all over from the beginning. I've been getting a number of these boots.
    2 points
  22. Which is better Corsair or Zero? There's only one way to find out.....
    2 points
  23. @HIGHLANDSPRINGthank you for the kind words and wow! Those are some great screenshots. I'm really glad you enjoyed the campaign! It's the feedback from users that keeps me going, so thanks again!
    2 points
  24. I’ve played lawyer here as much as anyone, but seriously, Legal Eagle Dynamics: Digital Courtroom Simulator has to become a thing…
    2 points
  25. We can't or at least we don't know yet about it. HB is planning to release early F-14A in one of the next updates and I'm guessing they messed with it somehow.
    2 points
  26. Me. Id buy it on day one. I'd be more than happy to dogfight you in it
    2 points
  27. Just last night my AI wingman crashed into me while I was lining up for landing. In the same sortie, two C-130 decided to block each other at the end of the runway, effectively ruining the entire mission. Does this count as a complaint? Or do I need to fill a form?
    2 points
  28. Alright, I got most, if not all the clickable data (switches, knobs, etc) in here, with the exception of circuit breakers. I was able to test out a lot, but not everything. What I tested works so far. Feller, I added your name along with mine at the top for credits. This should satisfy most Stream Deck users. Work to be done: 1. Test and let me know if anything is broken. 2. Add more outputs (gauges, needle positions, indicator lights, etc.). I likely won't get around to this as I don't need these for my personal Stream Deck needs. 3. Continue sharing the love of this bird and reupload any additions/fixes you may have. Cheers, -GT- F4U-1D.lua
    2 points
  29. Just dropping a line to say how GOOD this is with ButtKicker! I was using the Hapticonnect software that came with my ButtKicker Gamer Plus, and it “worked” with DCS, but just felt kinda lame. Barely any rumble when firing up the F-15 engines. Just felt off. I decided to purchase this module (after being very satisfied with SimShaker Wings in Il-2), and… WOW! I felt like I was sitting on two powerful jet engines! My immersion just went through the roof! SO good!
    2 points
  30. И то не весь, летаю PVE на той же Сирии на 21 мигаре - каких-то ущемлений не чувствую, а на 29 уж и подавно не буду чувствовать. В PVP чувствую ущемления и страдания на любом крафте от вакханалии которая там происходит, начиная от школьников на ввп портящих погружение в игру прям со старта и заканчивая геймплейной концепцией "насрать амраамами абы куда и улететь" - очень интересно и увлекательно(нет). Наоборот хочется какого-нибудь специфичного необычного геймплея, по этому надеюсь когда-нибудь выйдет тот же миг-25.
    2 points
  31. They are both important. Personally, however, I would prefer a landmark that makes a city recognizable and unique over a correct HAS model.
    2 points
  32. Its no wonder. Most who might want a grip has got it. And while it might be great in the real tomcat (though I would prefer a different layout), I guess its not that suited to a sim environment where you would want more buttons to compensate for lack of cockpit. the real reason I write here though, is an encouragement to those who own it: Make sure to take good care of yours. The item is quite unique and it’s probable that no one will produce anything similar again for a long time. you might therefore own something more hidden and sought after than MH17s black boxes: A piece of PC equipment that might retain and even increase in value.
    2 points
  33. Usually caused by over speed or over weight landings, attach a track replay example so we can analyse thank you
    2 points
  34. Ok, as traveling for work keeps happening and I did not find the time to test (and will not until at least Tuesday), here is the file I made. Haven't got a clue if it will be even detected, so some troubleshooting for that may be needed, before even testing if I got the ID's correct. Maybe somebody can test this, correct this and re-share so we can all built it to full functionality together so we all benefit. As a heads up, I made this by following the guide here... https://github.com/s-d-a/DCS-ExportScripts/wiki/Documentation-in-English#Create I did this on a laptop that does not even have DCS on it. F4U-1D.lua
    2 points
  35. Tested and works fine in the server I flew in (Grayflag Syria) with no IC connection problems, fantastic sound mod
    2 points
  36. In FC3 tire pop up is modeled pretty accurately. Tires start to pop up after passing 200 kts. It also depends on the total weight, clean can take much more speed before tires pop up. Also not, Mig-29 accelerates pretty fast, and you are at 200 kts in almost no time. Mig-29 take off speed is bettween 150 and 160 kts! Remember that.
    2 points
  37. Working on the big one: HANGAR 1 – by far the most dominant and massive building at Gütersloh Airbase. It still puzzles me why UGRA Media released a map without modeling such a central structure. This one really defines the airbase.
    2 points
  38. Mi más sincero agradecimiento por el maravilloso trabajo que habeis realizado en la construcción del Juan Carlos I, tan solo haceros una pequeña petición, sería posible que los Harriers que van como wingman en una misión despegaran del barco desde más atrás, ya que si van un poco cargados caen al mar. Un saludo y gracias
    1 point
  39. Many thanks for the mini campaign Sedlo. Very atmospheric & enjoyable (as always). I completed each mission from cold start, but I do very much appreciate the F10 option (great for training). I understand it's twice the work since they are unique missions, so you're not likely to do more, but thank you for including them in this campaign. Five stars and looking forward to your next one as life allows!null
    1 point
  40. Hi, While ED grants this wish, may I suggest to give this Script a try, it was truly useful on my rocket training mission that I did for the MiG-21: Best regards, Eduardo
    1 point
  41. 1 point
  42. No only the Essex, remember ED has talked on February about the WW2 Pacific Assets Pack, with the USN and IJN ships, that has all DP Guns, and actuly we need a update if has plans about make a more necesery feature on the Core to all WW2 and Modern ships. The problem will be, the lack of all fire control on ships. That not help to simulate DP Guns with a propper missing systems.
    1 point
  43. AH-1Z ! Footage of the DEADLIEST Gunship Ever Created
    1 point
  44. Not a bug. It tells you in Mission 3 that reminders for Takeoff, Departure, Arrival, and Landing will no longer be given. Also your kneeboard is your friend. It has the callsign of all contacts and their corresponding presets for both the UHF and VHF radios so when they say "Push Sentinel" and you don't remember the frequency, you can quickly check. Shift + K to open it in flight. I generally just leave mine on the radio reference page.
    1 point
  45. В таком случае должна быть какая-то база отсчёта высоты (и это НЕ может быть сам вертолёт). Например - высота по барометрическому высотомеру, исходя из того, что на нём выставлено давление на уровне моря. Но сейчас можно барометром хоть обкрутиться, на определение высоты цели это не влияет. Я не знаю, как там в реальной машине, но если вступить в область предположений, вполне логично выглядит ситуация, когда система считает, что барометрический альтиметр настроен на давление на уровне моря, после чего определяет превышение вертолёта над целью, сопровождаемой Шквалом, тригонометрическим методом. Далее разница вычитается (с учётом знака) из барометрической высоты - и вот она высота сопровождаемой точки над уровнем моря. С ПВИ не ввести никак, а вот при помощи Шквала - можно. Тогда собирается в целом логичная и непротиворечивая картина, как оно всё увязывается между собой и с редактором. Метод не без недостатков, конечно - но у Ка-50 и так всё, что касается навигации, из недостатков и компромиссов состоит, так что из образа не выпадаем. Маршрутные точки так не внесём (да и не надо), а вот ОТ и запомненные цели заиграют новыми интересные красками. Повторюсь, я не имею ни малейшего представления, как оно было в реальном Ка-50. "Educated guess".
    1 point
  • Recently Browsing   0 members

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