Search the Community
Showing results for tags 'correct as is'.
-
CCRP not dropping bombs; I hear at tone at the right time but they don't drop. Made lots of attempts, pitch and altitude were appropriate. This happens often but I don't know what triggers it. dcs.log debrief.log dcs.log.old bug test.trk
-
The last line of the bit test shows "RESTRT", didn't know if it's a typo or acronym.
-
What did I do to remove crosshair (and point track box) when I enabled XR in TV mode? I still had it in IR mode and regular TV mode, it would just disappear in TVXR mode. Pressing TMS down long only declutters while held, but I lost it completely and couldn't get it back. I just checked the manual to see if there was a declutter toggle that I may have used by accident, but the only declutter it mentions is the one while holding TMS down.
-
correct as is f18 gbu 10&12&16 cannot guide through TGP laser
Ddg1500 posted a topic in Bugs and Problems
Hello, i found out recently when i was training to use various laser bombs in f18, using the TGP(litening for instance) with gbu16 or 12 or 10, The bombs cannot be guided with laser when was set to the same laser code(different from the orignial code when loaded by ground crew) on both TGP and bombs in MFD on ground or in the air(and yes I arm the laser) It sometimes could only guide properly when the the bomb laser code was edited on "Rearm &Refuel page" on ground, editing the bomb laser code through MFD after loading doesn't work, even in the air, it won't guide through the TGP laser. I think it is a bug, here is my trackfile f18 GBU12 success .trk F18 GBU16 laser .trk f18 GBU12 fail .trk -
As per the title, the right outer tail light of the Mig-29 is missing. See attached photo.
-
Hello, Shouldn't there be a runway at this airport? or is it because of my computer's poor performance with this map? best regards, Michael Khost.trk dcs.log
-
.thumb.jpg.cdb90e96acdbb4116f7acd67a662445e.jpg)
correct as is Texture, Unit Of Measure, and Language Issue
Gustav960 posted a topic in Bugs and Problems
It seems that there is a conflict with textures, selected units, and language on the analogue gauges in the MiG-29 Fulcrum. Settings: Gameplay - Avionics Language = English Settings: Gameplay - Units= Metric Settings: Special - Cockpit Language=English When set as above, the Mach meter reads with NM and the RAD ALT also has a texture that reads in feet. The needles themselves are not reading the correct altitude or speeds. It seems to be the incorrect texture. When settings are all in metric and the cockpit in in "Default" all the gauges work as expected and the textures have metric graduations. The HUD appears to be correct in all modes and settings. I hope that is helpful. Please reach out if you need more information. This is my first ticket and I don't have a background in troubleshooting software. Great module! Good luck. -
Basically, if you hold your brakes in the MiG-29 during takeoff while running up your engine, and then release the brakes the moment you hear your afterburner activating, the MiG will try to rapidly raise its nose, resulting in a tail strike. mig29tailstrike.trk -
You are not able to move the ramp if the gunner is sitting on the ramp. The ramp remains in the ground position and can't be moved in the middle position.
-
When you set the range for the gun to automatic by clicking left TSD B6 on the WPM page to choose the range and then typing A in the keypad and pressing enter, it will not maintain automatic range if you disarm and rearm. That is not the behavior with the rockets. With rockets you can arm and disarm without losing the automatic range setting.
-
Hi all! Since the last patch, the HAFU symbols in the AZ/EL are missing. Only by designating the contact it appears in the AZ/EL display. Does anybody has the same issue?
-
Im not sure what causes this, but when i do a controls wipe (move the stick around on the ground) the TO/LOG CONFIG warning lights up for 0.1 second occasionally, along with a WARN in the HUD. Is this as intended? I have observed this in both CAT I and CAT III F-16 CONTROLS WIPE.trk
-
Summary of Issue The newly implemented Terrain Avoidance (TA) radar mode in the F/A-18C appears to lack inertial stabilization. The radar beam orientation remains fixed relative to the aircraft’s body axis (pitch) rather than being INS-stabilized relative to the horizon, which causes erroneous terrain depiction when the aircraft is not in level flight. Observed Behavior When the aircraft changes pitch (e.g., climbs at +10°), the radar beam follows this change: The scanning pattern shifts upward, no longer referencing the terrain ahead as relative to the horizon. The TA page under-reports or omits terrain elevation returns, particularly those that were previously marked as dangerous (lime color for terrain above aircraft). This creates a false sense of safety, as terrain hazards may disappear from the display simply due to the pitch angle. Expected Behavior In real-world terrain avoidance and following systems: The radar scans with beam angles stabilized against an earth-referenced frame, using INS attitude data. Terrain is detected and classified based on its absolute elevation relative to the horizon and current aircraft altitude, not pitch-relative attitude.
-
I've been out of the Hornet for a long time - maybe a year. So this may be a "me" issue. I have a video and a track shared so others can maybe clue me in as to what I might be doing wrong. Since I haven't see this posted anywhere I suspect this isn't a defect, however. Any help is appreciated. I can't get LGBs to track the laser from the ATFLIR unless the code is set to 1688. If I try and change the code (in flight or on ground) using the weapon/flir MFD pages, the numbers are updated on the jet, but it just doesn't work. So far I've tried using 1687 and 1588 as codes and the LGB never "sees" the laser. Based on the recorded track, it doesn't appear the laser fires at all (even though its armed). Anyone gotta a clue for me? Oh ... and this is completely vanilla (no mods) running latest unified version of DCS. Thanks. LGB Test.trk
-
Is ECM implemented yet? Cannot find any binding keys for ECM
-
While re-learning the Su-33, I was able to retract the nose gear while on the ground:
-
As title. I can't grab a track at the moment but this is easy to replicate. Recenter the right seaters ADI and the pitch / roll AP turns off. I can't imagine that this would be the intended behaviour.
-
correct as is Options for alternate AI escort behavior
funkyfranky posted a topic in DCS Core Wish List
Situation: Fighter (F/A-18C) gets task to "Follow" or "Escort" a B-52 bomber. The bomber has task "Bombing" a location on the map. Result: Fighter follows bomber as expected. Once the bomber starts the "Bombing" task, the fighter stops the follow/escort task and proceeds to its next waypoint where it orbits until the bombing task is accomplished. Question: Maybe this is intended but I see no reason why the fighter would stop the escort when the bombing task is active. So is the the intended behaviour and if so, is there a way that the escort task is not "paused" while the bomber attacks? -
There are two problems with the hack time start/stop and reset logic: Using DED Increment to start hack time progression. DED Increment again stops hack time progression. Pressing DED Increment a third time causes the hack time to continue counting as if it was never stopped. It should start counting from the value it stopped at. Using DED Increment to start hack time progression. DED Increment again to stop hack time progression. At this point it is impossible reset hack time with the progression stopped. It is only possible to reset the hack time with the progression running. It should also work with the hack time progression being stopped. Refer to page 114 of the DCS: F-16C Viper Early Access Guide (Version 20th December 2024). Track is attached. hacktime_logic_issues.trk -
The manual says: However in the jet: 1st press = Start timer 2nd press = freezes the timer DISPLAY, but the timer continues to run in the background 3rd press = unfreezes the timer DISPLAY, and shows the time elapsed since the 1st press F18_TIMER.trk
-
The clock in the cockpit is 3 hours early. For example, when it is 7 PM, the clock shows 4 PM.
-
When in this training mission it seems like the green gates end somewhere around half way of the runway point on the downwind leg. After which there is no more guidance for the the rest of the approach or landing. Does anyone have any ideas if this was fixed. Is there another way I can practice my overhead break approach and landing? -
The mission editor and new DTC function incorrectly label the COMM 2 as the ARC-222. The F-16 does not use the ARC-222, it uses the ARC-186 or ARC-210 as the comm 2. I believe ED does not intend to implement the ARC-210 so it would nice to get it corrected in the menu to ARC-186. Thanks
-
Hi, I just find something strange today. When approaching M0.84 the roll rate is slowing down a lot and continue to accelerate will increase the problem. Is there any limitation link to the roll rate by the FCS?
-
Hi, after the last patch, or patch before .... I lost Spyglass option in keybinds. Are they present still? Cant find it ....
