Flagrum

Which trimmer mode do you guys have configured under special options? And do you have FFB enabled or disabled under general settings?

How is all this "Community News"? o.O

p. 85/86, copy&paste error:

Yes, thank you! And yes, you were right, I was using "Enable Action / No Action = Yes". This probably confused me the most as I was used to the "gamey" TDC when I last fiddled around with the Harrier a few months ago. Now, after a couple of hours, I seem to get the hang of it again. Still had some situations with what I would consider unintuitive behaviour, but at least it seemed to be more consistent.

If TDC is assigned to HUD, the slew rate of the HUD reticle is ok vertically, but horizontally it is 2-3 times the rate as vertically. (Yes, my TDC X and Y axis are set up identically) Why?

SSS Fwd --> TDC->HUD Designate spot under velocity vector with TDC Depr. Slew HUD reticle SSS Aft --> TDC->DMT/TV, HUD reticle changes to DMT rectangular reticle Slew DMT reticle, but when I let go of TDC slew axis, the reticle jumps back to the point where I had slewn the HUD reticle to, right before SSS Aft. Why?

Since the most glaring problems now seem to be gone(ish), I figgured that I'll give it another try. And yes, I try to do baby steps... So Lesson One: switch TDC between HUD and DMT. Situation: directly after Master Arm: on and A/G: on. Left MFD=EHSD, right MFD=EW SSS Aft --> DMT/LST SSS Aft again --> DMT/TV TDC: slews DMT/TV reticle. Cool. now SSS Fwd to assign TDC to HUD: DMT goes to DMT/INS, no TDC slewing of DMT reticle possible, no reticle in HUD, *confused* SSS Aft --> DMT/LST SSS Aft --> DMT/TV, but it looks at god knows what. My attempt to slew something while in HUD seems to have moved the invisible reticle to somwhere in the sky. Now back in DMT/TV I can't seem to move it anywhere else. UNDESIGNATE: DMT/TV slews to velocity marker Not. Intuitive. edit: ok, I learned something now. At step 4, the missing reticle in the HUD - I have to designate a target with the velocity vector. Then I get the reticle and the DMT is slaved to it. From there I can toggle the TDC assignment between HUD and DMT with SSS Fwd. and Aft. So, ok, cool! Now I can even Undesignate and still get the TDC slewable reticle in the HUD after SSS Fwd - even if I unbox the EHSD DESG. Why the difference between "before any designateion" and "after an undesignated designation"!?

There are several ways how I can designate a target and I can use severak sensors to do it. I am able to designate a tgt, but I am struggeling with the "workflow" - or rather the switching of different modes that happen if I switch between sensors. It seems to me, that if I designate a WP at the EHSD, the TPOD is slaved automatically to that designation. How can I now "sweeten" the designation? The TPOD always jumps back to the WP? And if I undesignate, then the aircraft switches to HUD designation? I don't know, I probably recall it wrong, but almost everything I try seems to result in inconsistent or at least unintuitive reactions of the systems. So, I'd love to have some sort schematics, a workflow chart of some sorts. Like, you start designating with this sensor. If you do that, these sensors will do so-and-so. Now you are in mode blabla and from here you can do this. Which components are affected (sensors, weapons) how, If I am in designation mode X with sensor Y. Which options does it then provide me to use other components with that designation? Does something like this exist?? Thanks, --Flag

Also the special option works only when starting a new mission. If you respawn within a running mission, you always get the indicators, not matter what the special option says.

I just found out, that RPG dudes shoot at helos now! This must be relatively new? I always wanted them to be a threat - thanks ED!

... if it goes super sonic. ^^

The new 3D Model for the Blackshark 3 seems to have functional avionics access panels on the fuselage. A few other aircraft have already something similar as well. It would be great, if those panes would be clickable if in F2 view (plus weight-on-wheels) and could be opened and closed by the user! That would allow - to some extend - to pretend that we virtual pilots perform a proper walkaround. Really nothing fancy in terms of simulating anything, just for the visuals experience. If there is already detailed 3D modelling present, why hide id 99% of the time behind closed access panels?

Yes, perhaps. But different people might be, well, different. But whatever, lets just lock everything and eventually and finally get rid of one of DCS' best features - it's moddability (mod, as in modification/altering stuff).

Yes, software runs on hardware and therefore if hardware fails, software is always involved in one way or the other. But it is the responsibility of the OS and it's drivers to allow access to the hardware within it's specifications. Regular applications like DCS have no real way to make the PC hardware work outside it's safe parameters - aside of user(admin!) errors and hardware issues.

This kills half of the comunity mods, which people might enjoy in singleplayer. Why can't this be enforced by the IC check for multiplayer?

Getting worse and worse? That sounds more like a hardware problem which is worsening over time. Maybe a failed fan that causes overheating? Or something wrong with the PSU. Software can not "progressively" damage your hardware.

Chapter "LITENING II TARGETING POD" / "Designating Targets Using the Laser" "When set to MARK, the laser designator will fire. This laser is invisible to the eye, and provides a firing solution for laser-guided munitions like the GBU-12 and AGM-65E." --> replace MARK with LTD/R "When the emitter is set to PTR, the LTD/R fires an eye-safe infrared pointer. This laser pointer is visible at night when wearing night-vision goggles, and is used to visually point out targets." --> replace LTD/R with MARK

This is already reported, according to BigNewy:

Was ich merkwürdig finde: ich sehe in den Logs nicht, dass ein Joystick oder Ruderpedale erkannt worden wäre. Nur Maus, Tastatur, etc. Was benutzt du da und kannst du bestätigen, dass das Gerät funktioniert (anderes Game, Windows Control Panel)? Ansonsten scheint irgendwie der Grafikkartentreiber zu crashen. Sind die Treiber aktuell - oder hast du die Treiber vielleicht gerade erst aktualisiert?

CTRL+Z, CTRL+Z, CTRL+Z ¯\_(ツ)_/¯

Thanks for your reply. But the main reason for my question was that I am worried that my interpretations were correct, specifically in regards to the differentiation between "As intended" and "No bug". Unfortunately you now seem to have confirmed my worries. To summarize: [AS INTENDED] means, the feature works as Razbam want it to work and does not plan to change it's behaviour. It does not mean, that the feature necessarily works as in the real aircraft. Different reasons for this could be: technical limitations, (lack of) available documentation, and probably many more ("comercial business decisions"?). There are quite a few bug reports tagged as "As intended" - and that is, what worries me. It means, that those features most likely are not working as in the real machine. A better understanding of why Razbam deviates from the DCS gold standard (most realistic sim, etc.) in these cases would help a long way to mitigate such worries. Therefore I politely suggest, that you explain in the respective bug report the reason of tagging it as "As intended". (Quite similar to, for example, cases of "User error" where you explain what the pilot did wrong.) Thank you!

What does it do if i tag someone by prefixing his nickname, i.e. @Flagrum? My assuption is, the person gets a notification that he was mentioned in a posting? Well, let's see ... edit: No, does not notify me - at least not for self-tagging. Could someone else please tag me here to check? Ty!

tagging@RAZBAM_ELMO - could you please chime in? Thanks.

A very broadly used feature here was to use links to other postings to point the reader to similar topics, related content, etc. Help requests were linked to already posted answers, bug reports to already found solutions, and so on. These links were just the respective URL of a posting, copy and pasted into the editor, of the form https://forums.eagle.ru/showthread.php?t=nnnn ALL these links were not converted during the forum migration, as it seems! They are now all dead links! A massive amount of information is now lost. I hope this can still be corrected...

Wayback machine only works, if the old posting is old enough and was already indexed by Wayback machine before the forum changed. I.e. how do I get to https://forums.eagle.ru/showthread.php?p=3552954 ? If an automatic redirection is not possible, maybe we can get some sort of tool (accessible directly from the 404 error page?) that generates a clickable link when a old topic or posting number is entered?