Search the Community
Showing results for tags 'correct as is'.
-
I created a mission where a MQ-9 is working as AFAC, designating a bunker with its laser. Laser code in the mission editor is set to "1735". During the 9-Line briefing the laser code is reported as "1688", later during the run, the laser code is also 1688 instead of the one set in ME. The task assigned to the AFAC was "FAC - Assign Group", Group was the bunker, Weapon "guided", Designation "laser", Laser code "1735" -
At certain ranges and angles the sight moves out of view in the HUD, even with head tracking it becomes impossible to use.
-
nullSun reflection on the cloud lastest OB update not sure if its a bug.
-
This. AI F-18 doesn't rearm AT ALL in rearming-refueling WPT on Carrier only F-16 F-18 rearming refueling bug.trk -
Bonjour tout le monde ! Voici mon problème, lorsque je crée un waypoint au sol dans l'éditeur de mission il apparaît toujours un peu au dessus de la cible où je l'ai placé. J'ai essayé dans la même configuration juste en remplaçant le F-16 par le F-18 et le waypoint est sur la cible au sol, cela montre que c'est un problème propre au F-16. Quand je lâche un JDAM, malgré ce problème, il atteint la cible mais quand je lâche un JSOW, il impacte toujours derrière la cible (probablement parce qu'il explose l'endroit du waypoint plus haut que nécessaire et se déplace) à moins que je m'approche suffisamment pour créer un marquez le point directement sur la cible, ce qui annule l'avantage tactique du JSOW. Explication du parcours : Dans l'éditeur de mission je mets une cible sur une plage de la carte Normadie pour qu'elle soit au niveau 0 du sol, quand je passe au point de pilotage de la cible (2) en mode Air-Sol, le TGP pointe toujours au dessus la cible, j'ai orienté le TGP et fait un CZ avec le TMS AFT qui revient au dessus de la cible pour démontrer le problème. Si je crée un point de repère directement sur la cible, au point de direction 26 et que je fais un CZ, le point de direction 26 sera également un peu au-dessus de la cible. Je précise que j'ai désinstallé et réinstallé le F-16 avant de créer ce sujet donc le problème ne vient pas du mode MFD jaune ou d'autres modes Est-ce un bug ? Est-ce que je fais une erreur ? Avez-vous également ce problème ? j'espère avoir été clair Merci pour vos réponses -
Hello all, I have a quick question. In reality the F-18 can sustain a vertical climb almost indefinitely due to its high thrust to weight ratio. However, when I try any steep climbs in DCS I quickly lose speed and eventually stall. Am I doing something wrong, or is this a bug maybe? Any ideas would be really appreciated. Thanks for your help!
-
In the attached track file, I launch two HARMs, targeted via the HTS, at a Tor (SA-15) that is being controlled directly by my friend. When the missiles entered the terminal portion of their attack (7-10 seconds before impact), he would turn off his RADAR. To be clear, only one Tor turned on then off. We performed this mission to test whether HARMs fired from the F-16 in HAD will intertially guide onto an emitter if it turns silent. Instead of flying via INS to the last known target position, as real HARMs do, we found that they simply fly off ballistically. This is a well known and critical capability for the HARM - it's bizarre that it has been omitted and, unfortunate that it will likely go unresolved for a long time. Bignewy or Nineline, please see what you can do about this. Track file attached for your convenience: server-20220404-222714.trk server-20220404-222253.trk -
HMD->ALIGN cannot be initiated with cage/uncage button unless ground power 3B is active when doing HMD aligment on ground pre-cranking. Is this bug or do you need to have FLIR bus powered for cage/uncage button to work for HMD alignment?
-
As the topic states, the (Lshift+J) camera jiggle effect only works when aircraft is in motion, then clips off/on hard when aircraft stops or starts moving. It used to move consistently, regardless if the aircraft was moving or not before DCS 2.8, I believe. It makes making cinematics a little less enjoyable, especially when starting to taxi. Does anybody know how to fix this, or @BIGNEWY if this is a bug, can you guys look into this when you have the time? I will upload a .trk file as soon as possible. Much appreciated! -
I thought that wasn't supposed to happen? -
So many bugs here. I didn't see this one right off. MT. Keep getting MFD images overlaying each other. Is this already a known issue?
-
Hi, I noticed that the BRT Button on the TEDAC Frame affects the TEDAC Image brightness when the IHADSS overlay is active and affects the IHADSS overlay brightness when the IHADSS overlay is inactive. I believe this behaviour is flipped, as it would make much more sense if the BRT button would change the IHADSS overlay brightness while the overlay is visible and the monitors' brightness while the overlay is disabled. I´ve attached the relevant track file. Note that I only demonstrated this with the BRT button, but the contrast button, the symbology button and the reset button also have the same issue. BRTControlSwitched.trk
-
There is no pylons on 4 and 6 station. If I don't select remove pylon, the pylon seems to be ripped off. Running on MT. pylon.trk dcs.log
-
I'm not sure if this is a bug. I cannot find in the manual how it is supposed to work, but: In the HSI, when you select "Mode" and then select "DCTR", your position is placed at the bottom of the display. However, there is no way to put yourself back in the center. I would expect to press DCTR again, but that doesn't work.
-
Hey guys! I don´t know if this is really a bug but or not but I just tried setting functions like radar bar setting, range, azimuth, etc. with the TDC and I saw that after each selection I made with the TDC my TDC went back to stowed position. Is this "correct as is" and intentional? I find it hard to believe it works that way in the real jet as this is actually more than inconvenient. Can someone please clarify if this is correct behavior or if this is a bug?
-
I only tried this in Caucasus-map for now, but since the update of may 20th 2021 the map in the HSI is gone in scale 80 and 160. Works fine in 40, 20, 10 and 5. I already deleted FXO and MetaShaders but that didn't work.
-
According to the supplemental budget in FY 2007 this capability was only requested to be funded in 2007: https://www.secnav.navy.mil/fmc/fmb/Documents/08pres/supplemental/FY07_Supplemental.pdf page 251. This would put it outside the 2005 timeframe.
-
I was doing some testing of the SLAM ER missile on the F18, fired missile successfully in TOO mode and hit both targets in Fire and Forget. I did not use any STP's I then attempted the same targets again, this time in PP mode and entered the WPNT DATA for the required WPNT held on the HSI DATA PAGE into the MISSILE MSN PAGE, again in FIRE and FORGET MODE, without STP's, both missiles missed the target by a considerable distance. I next tried using the LAT LONG co-ords obtained from the F10 MAP in PP MODE and this time in FIRE and FORGET MODE without STP's, successfully hit the targets I then thought I had made an error entering the co-ords from the HSI DATA page so I tried it again in PP MODE but noticed that the co-ords in the DATA PAGE differed from the co-ords I had got from the F10 map by quite some margin. I decided to do a quick test and set up the missile using TOO MODE and compare the TARGET INFORMATION on the STORE MSN PAGE to the WPNT information in the HSI DATA page. As can be seen from the two pictures there is a difference from the co-ords on the MSN PAGE and that on the HSI DATA page for the same WPNT. I then checked the co-ords as close as I could using the ME page and found that the LAT LONG in the HSI DATA PAGE differed considerably from the co-ords of the W/PNT in the ME page, strangely the GRID co-ords where very close. Also the co-ords used by the MSN page where very close to the ones on the ME map. Just noticed too while checking post the O/S GRID line on the HSI DATA PAGE the first digit of the GRID is overwriting the "D" on O/S GRID
-
When you try to enter a laser code in the DED before the TGP is ready, it will not accept input and default to a blank field. When the TGP is ready, the laser code will then appear on its own when you return to the DED page. I think at least the later one is incorrect, but I think that not accepting the laser code input is incorrect too. Also, pressing return on the ICP with the keybind sometimes does not return to the main page.
-
I have no idea how it is in the real hornet, but I know for link 16 DL the nets are labeled 0-126 for a total of 127 nets. Currently the hornets DL nets are labeled 1-127. I don't think that's accurate based on Link 16 standard being the common operating picture for aircraft, and materials I have read saying the net naming is 0-126. Further # 127 when set as net number should be turning the TDMA function off for the DL. On a side note the Viper can do net 0 but it also gives 127, thus creating 128 nets, which is also not in line with the link 16 standard ( *Viper is correct, but #127 should turn the DL capability off*) Cheers
-
resolved [solved] Skins of AI Aircraft not shown in Multiplayer
thornx posted a topic in Multiplayer Bugs
Yes I know skins are client side > read first: Skins that were used on AI aircraft (like Tanker, AWACS, Rescue Heli ...) are not displayed to players in Multiplayer. Reproduce: Set up an AWACS and a Client plane in a short mission. Assign a fancy Skin to it. Like the NATO E-3A Skin: https://www.digitalcombatsimulator.com/en/files/645407/ Run the Map on your machine > Skin displayed Upload mission to dedicated server and connect > Skin NOT displayed Bug or Feature? -
The radar now has a frame storage feature that causes each radar contact to have a stream of faded contacts behind it from previous hits. For some reason, there is no way to control how many frames are stored, unlike other us aircraft. Additionally, there is a separate time setting that wipes the entire radar picture. Based on how other radars in the game work, the current implementation in the F-18 seems unlikely. The radar frame fade on old bricks seems to have its own time settings, but those get over-ridden by the timer setting if the time is lower than whatever the frame store time is. So at low timer settings, the frame storage is pointless because the radar gets its entire scan wiped in a time less than the scan (for example a 4 bar 140 scan with 2 or 4 second timers) If the time is set to 8, 16, or 32 seconds, the extremely long radar frame storage causes the entire screen to be saturated by old contacts. This makes it extremely hard to interpret the display. There is no way to set the radar up in a reasonable way. If the timer is set too low, the screen is erased so fast its hard to keep track of targets. If the timer is set higher, the radar becomes so brick saturated that its unreadable. What would be desirable, I find it hard to believe the real jet does not do this, is to have the frame storage adjustable so that the frame storage can be set very small (1-2 frames) but where the timer to wipe the display is set to a time equal to the scan time of the current bar and azimuth configuration. This is how it is on other jets. On jets that do not allow adjustment of one of these settings, it is set so that the above condition is the one implemented.
-
Version 2.7 Steps 1. takeoff (with 2x370 gal tanks) optional 2. list-2 -> fuel Bingo set , when change e.g into 7200 i get fuel warning indication in HUD.
-
Hi, No matter the selected FLT height (low, medium or high), the AGM84E seems to fly the same: First the SLAM tries to hold it's launch-altitude until the target is roughly 9° below the horizon line, at which point it'll pitch down to also roughly 9°. (In case the target is lower than 9° below horizon ON LAUNCH, it'll immediately descent at ~9° pitch down) The SLAM will keep holding those ~9° nose down attitude until it's ~10NM away from it's target (no matter the selected DIST setting), at which point it will level out. Flying level until ~4NM from target, at which point it'll go into it's terminal attack phase. streamable link of ONE slam launch (FLT set to high, DIST to 15NM): https://streamable.com/fmon9t Note: (obviously) i did not at any point adjust the course of the SLAM. Track and tacview file attached to this post. IMO it's obvious that at least the FLT parameter is broken, possibly the DIST parameter as well: At least according to chuck's guide (Part 10, section 2.11.1 (page 499)) the flight profile should look as follows: (SLAM going terminal upon seeker activation, which would make aiming the SLAM a LOT easier, considering one does not really know at the moment when the slam is looking at it's designated target location until impact, see streamable video above) That being said, it could very well be that chuck's guide is wrong in regards to the DIST parameter. slam_broken-flt_high-dist_15.trk Tacview-20210505-220230-DCS.txt.acmi
-
Hi, at WAGS video he said the picture freeze whenever you designate and only then you can slew the cursor. In this video - it seems like the cursor can be slewed to wherever you want before the designation and picture freeze. Seems like when you press the designate - the picture will freeze and the actual command transmits to the missile. So, you can slew freely and then designate (picture will freeze). Or press designate, then the picture will freeze and you'll be able to slew. Both ways possible. The slew cursor movement not bound to pressing TDC.
![[HOUNDS] CptTrips](https://forum.dcs.world/uploads/monthly_2022_03/CptTrips_lrg.thumb.png.070ce2de79756547bd11112ed28ed366.png)
