Flagrum

The current implementation of the tracking modes seem a bit unintuitive. For one, you can not slew the reticle in neither point track nor area track mode. This makes especially locking moving targets in point track mode overly challenging. And, for two, the point track mode itself is strange: wherever you switch to PT, the reticle stays there. Even is there is nothing beneath it - like the ocean or the desert sand - where it could get a contrast lock. So, the PT mode, if not locked to anything, why can't it be slewn? Or the other way around, why is it even possible to switch to PT mode if there is no object beneath the reticle? More intuitive would be, imo, if PT gets only activated if an actual lock can be aquired. Then it would make sense, that you can't move the reticle - as it is locked. But if you fail to get a proper PT lock, perhaps the TPOD should default to area track instead - preferably slewable? Thoughts? (This is not meant as a wishlist posting. If it is all bonkers what I wrote, then "it is what it is". But perhaps, maybeeeee? the current implementation is not yet perfect and if a dev reads this, he might consider re-thinking the current solution?)

rocket recoil? is that something similar to bullet backblast?

Does this happen only when "pulling G" or do rather when you deflect your stick far enough? Maybe it is a hardware problem of your joystick, some broken wire that gets shorted when you move the stick too much?

+1

There is hope!

Afaik you spell american names letter by letter as they are meant as abbreviations to separate words. I.e. F=Fighter, F/A=Fighter / Attack Plane. So it is Eff Ay Eighteen, not Fa Eighteen. Russian names are shortened manufacturer names, like Su = Suchoi (sp?) and it seems more natural to pronounce them as such. Also, as they are the beginnings of actual words, it makes it possible to pronounce it as such - which might be not the case with some obscure collection of more or less random letters.

By using his magical AI powers. Or were the guys that pushed back the aircraft just wearing good camo?

YES, THANK YOU. I was just about to check this as well. This happens if you get a new rig and have to install TIR (and mess up to backup your TIR profile first). One would have thought that after half a year something like that would have been noticed a bit earlier? Aaaanyway, all good now, it works! Thanks for the quick reply!

I am stumped. My F7 view to show the ground units of my coalition does not work.... F1 - F4 works ok, theat one which cycles through the air fields works, too. Anything between F5 and F8 do nothing. I tried it as Player/pilot, as Tact.Cmdr and GameMaster. I enabled all Map View options. There must be something very, very obvious that I am missing here.... what else can I check in order to get a usable F7 ground unit view? :cry: edit: All F-keys are mapped, using the default settings, in the "General" category. Deleting the Saved Games Config Input folder did not help either. edit2: Ran also a repair ofc. Still nothing ...

I'd only want to add the missing two things to that list, as we are already at it: * End the hunger in the world and * Peace on earth I mean, I would totally pre-purchase this, even as beta!

Probably roughly related: https://forums.eagle.ru/showthread.php?t=281179

With a LG82 selected, the SMS format shows the CODE function at the left bottom push button which allows you to set the PRF code for the weapon via the UFC. Since last patch, this push button function is also active at the SMS main page (i.e. without any LG82 selected). Selecting different weapons shows it's respectife SMS format correctly (i.e. without CODE push button). But it gets somewhat problematic, if you just select GUN. Then the very same push button is assigned one of the two possible ammo types - while still also being assigned the CODE function. The displayed text is mixed up / overlayed over each other. The CODE function seems to have priority, though. Whenever it is selected, you can even set the PFRF code for the LGBs, without having them selected. edit: SMS main page CODE.trk

No, you pre-ordered it.

Try hitting a moving target with it.

It would probably collapse into a relativistic singularity ... taking the whole universe with it. I.e. it is not possible - or would require "different" laws of physics/mathematics/etc. than we have in our world. If you want to make something look bigger than it is, you have to take that part of your picture (i.e. what you currently see) and stretch it in all directions. And that is effectively changing your FoV. The only other way is to get closer to the object you want to see bigger. But what you see then is not really "bigger than it is", because it IS that big then.

Could Triggered Actions in the Mission Editor do the trick? Afaik there is an Action that can set cockpit args ...?

So, ED said, they would focus on bug fixing. And you heared "we are focusing on F-16 bug fixing". Did I get that right?

I bought the F-16 as well and I am, as well, not happy with the state it's in. But what I don't get is, why ppl are now angry that this patch doesn't help that much in this regard. It was clear that ED would focus on bug fixing - supposedly, and as it seems, in actuality - all across DCS:W + modules. That the F-16 would not get an extra treatment here was clear, imo. Perhaps you should have voiced your concerns in regards to this update earlier, when ED announced it. Something like "Uh, no, please no bug fixing! Just some attention for the F-16!". Maybe you would have found supporters and would have made ED to reconsider that decision .......

The situation with the F-16 is clearly far from optimal, but seriously, what did you expect to happen with this update? That the F-16 will be brought up to at least FA-18 level? I mean, when ED clearly stated that they were focussing - and rightly so, especially after the last update - on BUG FIXING. What the F did you guys expect would happen!?

I read somewhere something about PDU / Pilot Display Unit (https://forums.eagle.ru/showthread.php?p=4348166#post4348166). Is that the same as ODA?

No, the pylon stores nothing. But the SMS can only address pylons, not individual weapons on the pylon(+BRU-55). So you tell both bombs that TOO1 is coord-x and both bombs that TOO2 is coord-y. Then you drop the first bomb on that pylon using TOO1 and the second bomb using TOO2. It is all a bit weired and very unintuitive and that makes me believe that this behaviour is actually not 100% like in RL. Either we need a different software version of the SMS that can address individual bombs on a BRU-55 - like Swiftwin said - or we perhaps should not be using the BRU-55 as it is not completely compatible with our current SMS software version ...

Have you set the bomb fuzes correctly?

I never got it to work reliably, but I tried it now once more after reading this thread (haven't flown the sabre for ... well, years now). At first, it was like it always was: unreliable. In only 1-2 of 10 run-ins I was able to get an auto release. Then I sat down and started thinking ... and I think, "I got it" now. I think, the key factor here are the sight gyros. If I banked over to get my nose down at the target, it usually did not work. But if you do it exactly how it is worded in the manual, push the stick forward to get into a dive, it works much better. My theory is now, that smoothnes is of utmost importance. If you jink the stick, roll the aircraft around and do all kind of "extreme" maneuvers, the gyros get upset. Maybe the system already senses the "below 1 G" criteria already while you are still trying to get your nose down and haven't yet consented to the weapon release. Or maybe the gyros just get out of whack in general. If I now push the nose geeeeeeently over, don't have to jink left and right to get my pipper placed correctly, then I usually get a release - and I get the bombs even quite close to my aim point! Perhaps even banking over to get into a dive might work - I would need to experiment more here. But if it works, I would assume that the whole maneuver needs to be very smooth. And probably will require a few seconds to keep the pipper steady to allow the gyros to "re-align"(?). Just my 2 ct - maybe something to ponder about.

is this issue being revisited? I believe the [no bug] is not valid. thanks!

bump - track is provided now, could we get an updated [tag] that this is being investigated/reported, please?