Search the Community
Showing results for tags 'correct as is'.
-
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!
-
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
- 1 reply
-
- tedac
- brightness
-
(and 1 more)
Tagged with:
-
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
-
IHADSS failes to boresight. Screen grab shows alignment prior to B/S button press via grip ENTER. Then obvious failed boresight result. Link to YT video showing boresignt alignment procedure. This is a fail. IMHO on developer's end.
-
The apkws from the Harrier often hit trees on the way to the target because instead of lofting like the mavericks do, it drops in altitude a lot while tracking the target then comes onto the approach to the target nearly horizontally. I was wondering if this was correct behaviour? I will try to get a track if it doesn't sound right.
-
Steps to reproduce: 1. Select SA format 2. Select EXP mode 3. Push STEP button. Expected behavior: step through the non-friendly trackfiles. Actual behavior: doesn't work. Remark: STEP correctly works in non-expanded mode.
-
Hi, since 2.7.7 I am having issues working with pilot - gunner logic. I ask Petrovich to look at an area where I expect a column of 3xIVFs. He looks there and locks up IFV without asking - no target list to select IFV 1, 2 or 3. Once target is locked I get constant launch tone although I am not aligned at all. In the track I overfly the target to present how the launch tone is constantly present without valid shot conditions. Maybe I am doing it wrong now? Thanks. Track is for Marianas map. BUG CHECK.trk
-
Copilot ADI is on even with the FDI switch is off. Seems that the FDI switch in the copilot cockpit is not tied to the "element copilot ADI" and is commanded only using the pilot cockpit switches. Attached screenshot. Thnaks in advance.
-
In the hornet, if you are in AG mode with a bomb selected and configured for CCIP release mode then designate the waypoint as a target, the HUD symbology switches to CCRP. I am not a real hornet pilot, but I feel that this must be a bug. If I configure CCIP, it should stay CCIP until I configure another release mode. Having it switch automatically every time "target designate" is selected is so inconvenient that I cannot believe the real jet would do this. Another hint that this might be a bug: the configured mode on the MFD still says CCIP:
-
Would somebody confirm if the periscope is now working as it should, I'm having problems getting the zoom to work and fear it may be a key binding issue - thanks
-
Just took off for the first time in the mossie, and she's a beaut (tutorial with the horrid takeoff assist doesn't count ) After taking off and climbing (I was probably aorund 2000ft, but wasn't paying attention) there was an ear splitting whine to the left of the pilot. This occured somewhere around when I turned north up the coast, after passing back over the airfield. I couldn't obviously figure out what it was, and it was nearly painful. Is this a weird bug, or have I miseed something that I can turn off / down? I turned on the VHF, but left the rest of the radios alone, so unsure what it could be. Only had this in a multiplayer mission, so track is too large to upload herer, but have attached a drive link if you're happy to use that. Thanks! https://drive.google.com/file/d/1DaRmcuUomCJ0o_AAG3qYCQsX8vAzbrAR/view?usp=sharing
-
I'm using the provided Startup tutorial for the Mosquito and it seems to stop at Prime engines. Is this a known issue? As soon as I instruct the ground crew to prime the tutorial doesn't give any further instructions. Am I gouing wrong somewhere?
-
correct as is Radar relocking targets even if lock is dropped
TobiasA posted a topic in Bugs and Problems
The radar automatically relocks the last target if you broke lock on a target in RWS <3nm. It is impossible to break the lock since the radar locks the target again, even without a valid track file. I have seen also cases where it is possible to relock a target that does not have a valid track file with TMS up on an empty scope. The track also shows the AIM-9 returning to "WARM" if you switch to dogfight mode. This is the latest OB update from today. F-16_radar_relocking.trk -
at around 08:23:30 ingame time I plan an approach to an airfield with an 122° magnetic course, setting up autopilot to hold the course, then decide to change the aircrafts degree mode from magnetic to true wich results in an immediate right turn and the COURSE NOT ALIGNED WITH THE RUNWAY ANY LONGER!!! the aircraft tried now to fly 122° true heading which is a complete different approach bugflight.trk
-
correct as is hsi hsel not affected by magnetic/true changes
Coding posted a topic in Bugs and Problems
at around 08:05:40 I fiddle with the hsel option from the hsi page. when changing the aircrafts heading mode from magnetic to true the hsel value is not changing and it stays in magnetic mode. bugflight.trk