Search the Community
Showing results for tags 'correct as is'.
-
Hello everybody, This is an old bug but still present. Every time you ask for a rearm and refuel and you select external tanks, if your current configuration already have the external tanks mounted, at the end of the operation the new tanks will remain empty and your total fuel will be about 7000lbs.(cant remember exactly the number) The workaround is: ask for a first rearm and refuel with no tanks, then ask for a second rearm and refuel including tanks. That way your total amount of fuel is correct. Thanks!
-
nullAs the picture showed. After I landed on the carrier. Then I take off again, the gear became like what the picture showed. And the alarm sound played. At this situation, I cannot fire the missiles. But I can extend the gear and take landing. Is that because I land on the carrier too heavy so the gear doors was broken?
-
Since 2.7.14 update the Supercarrier ICLS localizer needle is offset left by a substantial amount. Probably related but BRC also appears 3-4 degrees off. Never mind. Discovered I had weird mod installed. All good now. Hornet Needles Offset.trk
-
Does anyone know how to fix the glass? It appears to only be the CPG's side windows and top window that are far more cloudy that the others.
-
The bug with the non-functional Tacan navigation is still not complete fixed since the last update. With the update stable version the tanker is only visible if the A/A mode is deactivated. I think this behavior is wrong. I tested it in a mission with coldstart from the supercarrier. Maybe someone could confirm this. Thanks.
-
The 'two arrow key' on ICP is not switching waypoints/steer-points anymore either on DED or HSD. The only way to change these is to set '4' on ICP and put it manually. -
I was again testing radar, amraam and some evading maneuvers (but thats not important here), I`m more concerned about my radar loosing track while I already got it. Check out my track. Interesting stuff, never seen that befre f16_dogfight_jf17_5_no_Contact.trk Tacview-20220504-215633-DCS-bvr_vs_jf-17.zip.acmi -
Just as the title says, with a target point designated the IMAV seeker will not slew. This makes following the AGM-65F employment procedures in A1-F18AC-TAC-300 impossible. In the track you can also see another issue as the HUD designation is not being made from the point of the VV. MAVF.trk -
Sometimes vehicles give this message and will not rearm again. Can anyone tell me what causes it?
-
I own the A10C but decided to try the Flaming Cliffs trial, and that has the A10A module in it. It installed, and it flies, but nothing in the cockpit is clickable. The mouse cursor appears normally when you LAlt+C, and the mouse cursor stays yellow and never changes to indicate that something is mouse over and can be interacted with. This does not happen in the A10C, only the A10A. I see other forum posts about various planes/modules doing this in DCS apparently it's a DCS bug that's been lurking for years. DCS 2.7.6.13436, Win10
-
For example, a Fulcrum is detected by your ownship radar at 47NM, but you are unable to lock him (STT) until 39 miles. An A-50 is detected at about 95NM, but you are unable to lock him (STT) until 80 miles. STTLock2-7-11.trk STTLockA502-7-11.trk -
Editing the mission file in the mission editor shows that the helicopter should be on the destroyer, but for some reason it is showing up in the air (and it is impossible to complete the mission since you need to refuel/rearm)
-
Last night I decided to load up the Viper and try some GBUs out. However, in my unfamiliarity with the MFDs, I managed to "lose" a page. When you hit the A-G master mode button, the right MFD pops up with what I call the "stores" page. It's where you can select CCIP, CCRP, etc as well as displays what current ground store is selected and cycles through available ground stores. I started pushing buttons and somehow I "lost" that page and couldn't get it to show up again. It wasn't one of the MFD buttons, it didn't come back when I hit the A-G master mode button again, etc. Whatever pages I had selected when I got out of the A-G master mode were saved, so it wouldn't reset when I hit the button. This is not the SMS page as that one I can find and display no problem - this is a different page. The only way I got it back was to restart the mission. Is this a bug, known or unknown? Or am I doing something obviously incorrect?
-
When missiles are dropped in the TOO mode, some of the missiles do not hit the target... The number of disgraced missiles in different situations is different, but in this case only 1 missile flew at the target, and the other three flew off in an unknown direction. SLAM bug.trk
-
Here are two tracks from a generated fast mission. First, I use the mission as-is and start airborne. I go into a stable hover, engage attitude hold, and take some shots at the ground. The aim is fairly close with manual range set to the default 1500, then I turn on auto ranging and the aim gets much better. Everything works as expected. https://drive.google.com/file/d/10oFmdQXqs_vEOJJEQb8IZ0EBTTOm9S2K/view?usp=sharing Then I edited the mission to start cold, from the ramp at an air base. I go through the cold start. I wait for the INU to do it's thing, then I go into a stable hover and shoot at the ground. As you can see in the track, the aim is way off, even with auto ranging. I mean, it's not even close, and it's a night and day difference from the mission where I did a hot start. In case you think I forgot to turn on the radar altimeter, you can see on the HUD that it is working. Also, the radar altimeter is now on by default in cold starts. You don't have to turn it on manually. https://drive.google.com/file/d/10qJQsJL2SJKrWzSak8HKh3XPqczDuwAM/view?usp=sharing Here's the mission file, in case it matters. https://drive.google.com/file/d/1161nKSRN3YE8V65H23_FV-G9Nl1_K7_Z/view?usp=sharing
-
correct as is Vertical resolution of Azimuth/Elevation format
Jak525 posted a topic in Bugs and Problems
The vertical resolution scale of the Az/El format is incorrect, similar to the issue I reported for the Attack format except it's elevation angles and not range obviously. Currently it is referencing the top of the dugout as the top of the elevation scale. The bottom of the dugout should instead be the reference. So for example, if +/- 30 degree elevation scale is set, then the point that is 30 degrees above the horizon should be the very bottom of the dugout, not the top of it as it is now. This is demonstrated in the .trk by scan center position value. When I set the scan center to below the dugout (cursor, correctly, won't let you set it above the dugout), it indicates 26 degrees, whereas if I set it to the bottom of the tactical region itself it indicates -30, correctly. Image attached for demonstration. As per it, note the actual horizon line on the Az/El (0 degree point) needs to be shifted down. Also, the vertical tick marks will have to be adjusted. Another thing is the radar FOV should cut off at the bottom of the dugout, not the top as it does now. TL;DR dugout is considered part of the range-resolved tactical region. It shouldn't be. Entire tactical region needs to be vertically shrunk slightly. AzEl dugout scale bug.miz.trk -
I wanted to fly the Apache after a week or two of a break, went through the cold start, accelerated to crusing speed hit trim and let go as usual (center trim). Except this time the Apache imediately started to pitch up a lot. I was going somewhere between 90 and 110 kts. I checked bindings, all fine. Exited and launched the IA mission hot start on runway Caucasus. It's the same. The control indicators UI Overlay shows the trim get's registered. It seems it's simply not acted upon by the helo. The second mission is where the track is from. AH64 Trim bugged.trk
-
correct as is F18 tacan on/off switches dl on/off instead
rooster328 posted a topic in Bugs and Problems
Please see the track. DL on/off doesn't seem to do anything, instead it's the Tacan on/off that affects DL. dl test.trk -
AH-64 Test.trkThis happens sometimes. First 3 moving tanks are destroyed, last one parked, missile doesn't track at all.
-
When using GBU 31 on the Hornet in TOO mode, the MSN page of the JDAM doesn't reflect coords on ATFLIR. This problem seems to be recent, as it did work before. Other GBUs work as intended, only the 500 pounders are affected. Work around seems to be to set up markpoints and use weapon designate. This process is slow when compared to just using TGP.
-
In this track I loose the primary data link track to one of the targets for a reason I do not understand. Can somebody explain? I also fail to lock the Mig 29 that is right ahead of me. Can somebody explain? radar targets not shown.trk
-
Lots of issues about JDAM TOO mode, but I have not found this one articulated. In both VVSLV and in WPDSG targeting mode there seems to be no mechanism to update or refine the target coordinates using the TGP. This makes locating and targeting an object in TOO extremely difficult. I also note that Chuck's Guide states that in VVSLV mode TDC DEPRESS should designate the ATFLIR target with a diamond symbol. I can only designate target with SCS RIGHT (to right TGP DDI). I am not a real Hornet pilot, but I fly one on my PC. So I do not know whether these are features or bugs. JDAM TOO No Update.trk
-
Green dct track line does not stick to aircraft in flight. See attached track file DCT.trk
-
I encountered this with the AH-64 specifically. One example: RHG MAN TRK Controller. It's found in AH-64 CP/G - Axis Commands. But searching does not bring up the two axis commands. At least not for me. I encountered a couple of others instances but did not keep track of them. Thanks. -
Hi guys, yesterday fly on multy-palyer session and all pilot of F18 found this problem: Datalink when turn on Datalink not funcion, but if you turn on TACAN, Datalink go good. so thanks for your attention
