Diesel_Thunder

Image 2: (front panel with master test in lights position) Image 3 - Front panel with master test in FIRE DET/EXT position.

Here's a couple screenshots I took last night in a daytime training mission I had made. The first two are with the master test switch in the lights position. The third one is with the master test in the fire det/ext position. I can't even tell if the fire lights are lit. Image 1:

Had this happen tonight, and have had it sporadically before as well in all three versions of 2.7 so far. dcs.log-20210512-021227.zip

Thanks for the insight Snoopy

A friend of mine is building a A-10 simpit and decided to use the Button Box Interface, model BBI-64, for his switches and buttons. The issue he ran into is that he's having to cycle a toggle switch twice in order to change the state of the switch in the sim. I know you have to edit the lua file to do this, and I'm new to it as I just recently got a TM Warthog, and only started getting in to modifying lua for it's toggle switches in other modules. The lua structure on his BBI isn't the same as what I would find in doing the same for my Warthog. Here's an example from his fuel panel for one of the boost pump toggles: And the same line without the spacing: Not what I expected to see as there's not an UP/DOWN or DEVICE ID. The controller works in the sim, and toggles the correct switch, just have to cycle it twice each time he wants to toggle that switch in sim. What needs to be added/changed on these lines in order to make it act as a normal toggle?

I've often wondered this as why the DCS Hog only has the 7 rocket pod (LAU-68/LAU-131), and does not have the option of using the LAU-130/LAU-61 19 rocket pods? The Viper gets a LAU-3 19 rocket pod, and the Hornet has the LAU-61 19 rocket pod. Can the Hog not support the 19 rocket pods? Could these be used on the real Hogs?

As the title says, I am having a hard time seeing any of the caution and warning lights when they are lit. I've only recently bought the Tomcat, so I don't know if this problem was a thing before 2.7. This is in both the front and back seat that I notice this. Night time isn't as bad, but they are very difficult to see light up in daylight. I fly using TIR and a 27" monitor. I don't have any problems with lights in the other modules I own. I recall the A-10 had this same issue some time back that was later fixed.

I had a hard time on a night mission recently in MP. Friend of mine was in the Tomcat, where I was in a Hornet. He could see me fairly easily, while I had a very hard time finding his lights, unless very close to him. He had launched from the boat a few minutes before I did, and I couldn't find him at all to join in formation, even with relative bearing calls. He eventually joined on me as he could readily see my lights

I’ve never loaded a GUA-8, but have loaded the M-61 (CIWS). The ammunition is shipped with it linked with steel links. The loader delinks the rounds and feeds them into the drum, while the links feed out of a seperate chute still linked together. If I recall, we saved the links as we could reuse them to unload the drum and not deal with loose rounds.

Burt? You mean this guy?

You don't have to use TMS forward short, but it is useful on distant low contrast targets. The seekers on the D and G model Mavs seem to have an easier time locking targets on their own if you are closer to the target and there is good thermal contrast between the target and its surroundings. When I'm at max range, I have to use TMS forward short more often, usually also with china hat forward short to narrow the FOV. I've worked with FLIR systems when I was in the military, and they have a much better time holding a lock when they are closer to the target object as there is a much better thermal contrast for the IR imager to work with. I operated gyro stabilized FLIR on ships, not IR seekers on missiles. The principles are the same between the two though.

TMS forward short with Mavericks as SOI is the track command. If the crosshair gates aren't closed on the target, then you'll have to TMS forward short so the missile can attempt to establish a lock. At that point the crosshair should close (if it locks a target) and you can launch the missile. If there is a high contrast target in view when the Mav stops slewing, then it generally will auto lock. If not you'll have to fly a bit closer and TMS forward short to command the Mav to initiate a lock. That's the way it's worked for the past few years since I've been flying the DCS Hog (both the Warthog and Tank Killer). More info in the A-10 manual, page 588-589.

I ran a mission last night carrying 4 D model Mavs, and had no issues. All my shots tracked in and destroyed T-72’s. At least two were aimed with the TGP SPI (china hat fwd long), and one for sure aimed manually. No problems and all targets destroyed

#128263 Texas,

I've been wanting a Warthog HOTAS for some years now, and finally bought one recently to replace my 17 year old Saitek X-45. Aerial refueling and precision flying was no easy task with the X-45, and never once was I ever able to connect to the tanker in any aircraft. My first night with my new Warthog, I was able to connect on my first attempt! Stayed hooked up for about 10 seconds, and hooked up twice more. Quite happy with my new stick! If anyone is on the fence about upgrading to a better stick, be it a Warthog, VKB, or Virpil, I recommend it if you can. Flying is even more fun now!

Had a full crash last night while flying single player and trying out my new Warthog HOTAS. I attempted to load one of my A-10C II missions for aerial refueling and while it was loading, it had a CTD, and then wanted to run the dxDiag tool. I'm running 2.7.0.4625 with no mods. Prior to this I've had random issues with either DCS not wanting to load at all (stuck at initial splash screen), or locks up the program when loading a mission (gets stuck at loading World Objects 1/60) For last nights crash, I let the dxDiag tool run and grabbed the zip file to upload here. Hope this helps resolve the 2.7 issues :) dcs.log-20210429-023600.zip

I had asked this very question a few days ago in the Huey forum, and BigNewy replied in that one:

Was playing with a couple friends on the NTTR map last night. Everything was running smooth, did some Huey multi-crew plus ran an F5 and F16. I was the server host, So when I had my CTD, they stayed running but were kicked out to the multiplayer menu. None of us were running any mods, all on open beta 2.7.0.4625. The event that preceded my CTD was I had loaded into an F-16, and used the ground crew to change my loadout. Once they finished is when I had the CTD. Didn't give me any warnings or errors, and with the way it crashed I did not get the opportunity to save a track. Here's my DCS log, dump, and crash file. dcs.20210417-025852.crash dcs.20210417-025852.dmp dcs.log

Nice! I did a similar flight the day 2.7 released. No combat, just a solo flight surfin the new clouds. I was flat out impressed with that experience and it looked great on my older gear (1080p monitor on a GTX 980).

I bought it last year and have not regretted it at all. Just flying it, no combat, is quite fun in and of itself. For me, it was also my first high performance aircraft as my only modules then were the P-51 and A-10C. Lot of fun for me to push that throttle up, hear the afterburner light, and fly the hell out of it. Cloud surfing in 2.7 is a blast too! I don’t mind that it doesn’t have all the features yet. In some ways it can help you learn other things that you normally wouldn’t do often. Like last year when the T-POD had issues and it was very tough to drop LGB’s, it forced me to practice CCRP and CCIP modes with dumb bombs. As a result my skills with manual drops improved (good tip here is to use full racks of BDU-33 to get the most out of your bomb practice). IMO it is worth it, especially where it is at now compared to last year. And it’ll get better and more features added as time goes.

Not sure what you're running but the reflections effect works on my old GTX 980.

I don't recall anti skid working in 2.5.6, as I was always leaving skid marks on the runway when I hit the brakes after landing (both mains). That was with anti skid on or off. Now in 2.7, I landed and after the nose came down from aero braking I applied the brakes. My right main squealed/skidded for about 5 feet, and that was it. Both mains appeared to be rolling as I was braking. I don't have pedals yet so my brakes are on a button, and it's all or nothing unless I tap the button. It seems like it's working. I didn't see anything in the patch notes, but is anti skid working?

Can't speak for the Hog since I didn't fly it last night, but I did see the reflections in the Viper's canopy during my flight.

Thank you for posting that! Didn't realize I could click that box for the new clouds until I saw your post.

I too am enjoying 2.7. Flew for a few hours last night in my aircraft. No combat, just flying. Absolutely am loving the new props on the warbirds, and the new clouds! My favorite flight was setting broken clouds in a morning flight, and then taking my Viper up and flying in the cloud layers. Even on this older gear (GTX 980 on a 1080P monitor) it looked amazing! Bravo Zulu ED!!!