Search the Community
Showing results for tags 'hud'.
-
As the title already says, the hud lines and fonts have been in bold for many years. To this day it has never been corrected. Razbam did something on the Mirage 2000C that I corrected, but on ED modules and others the problem persists. I usually reduce the resolution of the DCS to leave one side of the monitor 21:9 to create missions. And on the other side to use watching videos etc. In reduced resolution, all HUDs are correct and easy to read. Please ED, fix this issue. Ask how razbam solved this problem with the Mirage 2000C and apply it to your modules. Thank you very much!
-
The position of target indicated on HUD is not corresponding with its true position. Target is marked by external laser designator (FAC) and picked up by LST (ATFLIR). Am I doing something wrong? ?
-
Very Simple Question. On the Velocity Vector on the Hud, when especially landing, what does it mean when the Velocity Vector Flashes or is not constant? It acts as though it is sensing not enough velocity. When I increase power, it does return to a constant symbol. I ask this because I could not find anything about it, and sometimes it does not act as though it has anything to do with too low of velocity, in other words, the plane may stall. Can someone explain?
-
The F-16 HUD has the lines and fonts in "bold". Is there a solution to look like Wags video? My monitor is 21:9. Maybe it's incompatible with 21:9 monitors? Does it only work correctly in 16:9? This happens with the A-10C, F/A-18C etc. The only one that works correctly is Mirage 2000. Thank You!
-
Not sure if this is a bug. I've never had this happen before in 2D. Tried the KA-50 for the first time in VR today and am getting the TV display duplicated in my HUD. Hoping it's something I can disable. Appreciate any help you may offer.
-
As the title says, when selecting the master arm switch to SIM there is no HUD lettering for that status. if intentional then please disregard
-
Speed Bar for airspeed, compass, height, time scale ?
jackd posted a topic in New User Briefing Room
A general Speed Bar for airspeed, compass, height and Time Scale .... Can you get them to show up in the main game view? And how can you get rid of that friggin' FPS frame counter in the upper right corner, probably set by NVDIA .. -
The HMD automatically rejects most of its symbology when looking through the HUD, but when we have an A/A target locked, it displays its TD box anyway in the HUD area. Therefore many times we see two TD boxes in the HUD: one drawn by the HUD itself and the other one by the HMD. This situation is very confusing for me, because most of the time they do not even match position due to field of view limits in both displays. Is there a way to prevent the HMD from displaying the TD box in the HUD area? Is this behavior even correct? It seems so weird and confusing... PS: sorry if this has been discussed earlier, but I cannot find any post about it. Thanks for your help -
Hi. This issue exists for a long time really. When I press HUD button on MFD-Cougar, my 8" TFT screen displays really heavy blurred HUD. It has been there for months, maybe more... I may be wrong but I remember that I've opened a thread or written on a thread about this, but couldn't find. So, opened again. Is there any move on this issue? Thank you.
-
UPDATE: Habe nun herausgefunden, wie es richtig geht..... Guten Abend! Ich habe mit der Mirage, mega Probleme! Für das INS habe ich mir dieses TuT zur HIlfe genommen: Mirage 2000C: CHANGES To INS Alignment & Approach Symbology - April 2021 | DCS WORLD 2.7 - YouTube Und ich befolge es strikt! Nun zum Problem: Ich gebe die Daten manuell ein (Die entsprechende Option des auto Ladens, ist im Menü aus) gelegentlich funktioniert es und mein HUD arbeitet entsprechend - nach dem "Booten" VAL und den umstellen auf NAV und [N]. Aber, regelmäßig, geht mein HUD nach Beendigung der Eingaben und den "Booten" des INS sowie den umstellen auf NAV + [N] wieder aus, bis auf den Kompass und ein + der wird im HUD gezeigt- obwohl das gesamte Flugzeug hochgefahren ist, auch in anderen "Stellungen" mit Batterie und Bodenstrom und den nur nötigsten. mit und ohne Bewaffnung, Radar an, Radar aus, Radar STBY... etc. Es nervt mich langsam gewaltig und ich frage mich, ob es wirklich an mir liegt? - oder liegt hier ein gewaltiger Bug vor? Nun ja, Verwende ich dann im rechten Pannel den einzelnen 3 Stufenschalter, für den Virtuelen Horizont und stelle ihn auf AN - nicht auf den NOTModus, so kommt im HUD "Horizon Secures" und ich kann nichts mehr machen. (also den Schalter brauche ich nicht, merke ich ) Ich weiß noch im Winter, da konnte man per Windos+POS1 Autostart machen und das INS lief prima. Jetzt mit Autostart geht das INS nicht automatisch - ja doch schon, aber halt das oben genannte passiert. Ich habe kein Pipper, keine Schnecke, kein Fadenkreuz Keine Horzontalanzeige keine Grad +/- NIX - außer der Kompass und ein + Zeichen..... Achso, Gunsight auch nicht Hoffe man kann mir helfen Grüße
-
Anybody else? After installing 2.7.x the reflections on the HUD not only show part of the dashboard which is not possible - but the reflections are too strong. It is very difficult to spot aiports & runways. Unfortunately the 'Clear Glass Mod 01' does not seem to work anymore. What about adding 2 options to the Main Setup (Tab 'Special') of the Su25T Reflective HUD Clear Glass HUD Thanks for any feedback HarryDeere41
-
Hello, I noticed that the steering marker (aka "bug") is subject to true heading correction. In practice, if the MAPM -> TRUE option is boxed the "bug" is moved according to the magnetic variation, thus resulting not aligned with the selected Waypoint. I noticed this yesterday while trying to line up correctly with a taget point (T0) for a CCIP release. Sorry if I don't attach .trk and screenshots but at the moment I'm in the office and I can't do it, for now I just wanted to know if others have the same problem. Thank you.
-
Please. With normal gamma settings some of the HUDs specifically in the hornet and viper can get down right unreadable on a sunny day. This is a real life issue and not a bug and the real life solution is a pair of shades. I'm thinking like, an in game button to put them on. You could even have an option for the frames to be visible on the edge of the screen FOV like with the apache helmet display in setting or something. The MiG-21Bis has a helmet visor that can be put on via click box. Just need something like that for all the modern jets with bubble canopies and open glass HUDs. Please would improve Quality of life beyond imagination for me.
- 5 replies
-
- 8
-
-
- brightness
- gamma
- (and 4 more)
-
In the (beloved) Smoerebröd-UFO the HUD-Glass can be raised via a lever. This is both possible via cockpit-interaction or keybind. As for the cockpit-interaction (ingame, in-cockpit) of the module, the mousemap for the cursor seems to be placed wrongly. Instead of being placed at/on/over the LEVER, the mousemap is situated at/on/over the HINGE. This results in a rather finnicky mousemapping interaction from the standard cam-position and/or creates the necessity to lean sideways to be able to raise the HUD-glass. While easily manageable with a mouse this can be extra tricky if fe a mouse-thumbstick on a HOTAS is used. The green marker shows the current mousmap area (oversized) while the red marker shows the actual LEVER where the mousemap should be placed. No trackfile needed, reproduction possible 100% in all instances and situational combinations.
-
In open beta, after Sidearms lock on, the reticle projected onto the HUD no longer centers on the emitter (it does in stable). For me at least, the weapon itself seems to be acquiring, locking, and homing as expected, both caged and uncaged. I'm attaching a track file. I do appreciate that waypoints now display on the HUD in A/G mode! av8bNA_sidearm_debug_OB.trk
-
I remember someone had reported something like this of F/A-18C hornet. When using Track IR or VR to move your head, there will be a "non-transparent bar" that block some important HUD indications or texts. Especially when your view angle in cockpit is high. Sometimes, for example during landing, even the FPV can be blocked at a specific angle. This is quite annoying and unrealistic because I know how real HUD works. The fix is actually quite simple, but the problem is that modifying the exact file (C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\HUD_AVQ32\indicator\Pages\HUD_base) will fail IC in servers. ED please fix this bug since F/A-18C launched, thank you!
-
because the real life hardware different than commercial HOTAS systems it means that some of the things in the plane are not usable as they otherwise would be. the HUD cursor sensitivity is one of these things, we have the option of making the DDI cursors too slow or the HUD too fast meaning the hornet in AUTO HUD designation is extremely hard to acquire a target. So the ability to set different sensitivity settings for the HUD would solve this issue.
-
hi! Like in the F-5, I would love to see the sight camera available for other aircraft like the F16 and F18, 'tape to the hud' adding also the MFD recording as option if available on that aircraft, like in the F-18. Then also make it available externally on our saved games folder as movie file. Ideally having a datacard, save it there. I believe it will increase squadron debriefs quality, and help creating promotional/marketing videos for DCS as well. Also, not having it mandatory shown when flying could be an option, even if saving the file. Thanks for the passion and dedication Diplomat
-
- 1
-
-
- sight camera
- f-18c
- (and 5 more)
-
So, I was unable to find an answer by searching. I found that when I create Waypoint ID names in the editor, that those names do not show up in the HUD of the plane when flying! I ultimately found that I had to extract the .miz file, and go into the CDU folder and edit the settings.lua with the names, about a 10 character Max, and then replace the original settings.lua file. Shouldn't the editor do this automatically?? Does anybody know how, manually is a pain!
-
Hi, does anyone know anything about the following: How long does it take for the F-4E INS alignment to complete? How many waypoints can the F-4E Nav system handle? Can the nav system manage offset points for loft bombing runs? Can the nav system calculate ToT and show cues on the HUD?
-
Needing a LUA expert, I think. Wanting to alter HUD only view to remove the DDIs and AMPCD. I have searched forums and guides and YouTube videos… so many directions are outdated, or don’t work, etc. Anyone know how and can help? Only for F/A-18. Thanks.
-
Hi, the FPV display in the HUD seems very buggy. I do understand that the Viggen does not have a modern HUD with 10 degree segments of pitch ladder, but currently it also displays the FPV in a very incoherent buggy manner. The manual says : "Flight path vector (FPV) Indicates the direction of current flight path vector in a 3-dimensional space in the form of a stylized aircraft symbol. Wings stick out of the circle at the 9 and 3 o’clock positions. The “vertical fin” at 12 o’clock is the airspeed deviation indicator. Level flight is attained with wings of the FPV lined up with the horizon. If the FPV is centered in the gap in the artificial horizon the aircraft is on the commanded course from the navigation system." There is no mention of any limitation, so I take it, as long as the aircraft's actual flight path is within the HUD area as viewn from the pilots point of view , the FPV should be displayed / visible in the HUD. To best illustrate the problem you can set up a flight, where you start airborne at a high speed of 550+ kts and take two RB24 or 74 as loadout, ( stay in mode NAV , switch the weapons selector to IR-BB , but don't unsafe the trigger ( I'll get to why) . Now pitch up 90 degrees to pure vertical. You will see that the FPV disappears already when passing 30degrees of pitch (as shown on the ADI) When you are at 90 degrees pitch up and still have enough forward airspeed , the aircrafts actual flight path is pure vertically upwards, which means, you should see the FPV in the HUD. But you don't in DCS. If you unsafe the trigger, you will see the IR missile symbology (just to prove the HUD is technically able to project something at any pitch attitude) . Now the funny thing is , if you now safe the trigger again, the FPV magically does appear correctly in the HUD. Very odd. The same also goes for significant pitch down attitudes (where the correct display of the FPV should be even more critical) I tested this some more. It appears the FPV incorrectly disappears when passing 30 degrees pitch up or down (on the ADI) and oddly reappears only when the pitch is reduced to 20 degrees up/down approximately. With aircraft pitch or more precisely aircraft flight path between 30 and 90 degrees from the horizontal the FPV is wrongly not shown inside the HUD. With my above "workaround" you can force it, but it works only until the next time you exceed 30 degrees pitch. Sorry for the long explanation, I tried to make it understandable and reproducable. In summary : the FPV incorrectly incorrectly does NOT show flight path or better put, is not visible despite flight path in HUD FOV between 30 and 90 degrees pitch attitude approx, when the aircrafts actual flight path is within HUD field of view. Some pics to illustrate: 1. Pure vertical and still forward speed for vertical aircraft flight path. (weapon selector in IR BB) 2. unsafed the trigger for RB24/74 , correctly symbology shown, in other words, the HUD is generally able to project . Now 3rd pic, after putting trigger back to safe, the FPV is now finally correctly displayed/calculated : Kind regards, Snappy
-
I've tried Su-25T after some time and I've noticed that there is one too many г - one of them obviously instead of K.
-
Just a quick sanity check.. (LOL...that's dangerous where I am concerned...but I digress....) When turning on a TACAN and selecting TACAN steering in the HSI, I still get the pointer (Heading Command Bug) in the HUD pointing to the selected Steerpoint NOT the TACAN. Is this CORRECT AS IS? OR did I forget some setting. I get all the TACAN steering information in the HUD DATA block and the TACAN location and either CDI or PLAN CRS line in the HSI, only the HUD indicator is pointing elsewhere. Thanks.. EDIT: OOPS!!! RTFM!! (this is in the ADI section, but I assume it applies to the HUD as well) P age 217
-
i noticed that in some times when i start the plane it shows radar cursor range instead of compass heading and want to know where can i toggle this behavior
