Draken401

Hello everyone, I am emotionally attached here and have overshot the mark. I sincerely apologize for that! This module is very important to me and in the past few weeks I have been training two new DCS pilots on this module. And I would like to do this as completely and error-free as possible. Unfortunately, I feel that my issue is not sufficiently addressed with the answer Center Zero and SPI and is less resolved than dismissed. When someone then asks me, as a small user, to submit technical documents to support my request, I wonder on what basis this module is being developed. It seems to me as if I were driving my car to the workshop and saying that something is rattling, and they tell me why I think that this shouldn't be the case and that I should show them the manufacturer's manual. But maybe this was just a translation error or misunderstanding. I apologize! If I am so wrong and misunderstood the topic I am addressing, perhaps someone would be willing to explain the following point to me. For my understanding and as far as it has been confirmed to me here, when I move the SPI I create a delta or offset to the waypoint or markpoint selected as the current steerpoint. And only to this steerpoint, not to any other waypoint or markpoint, or whatever! And with Center Zero or TMS down I set the delta back to zero. That is how I have always known it. But now to what I am convinced was not the case two months ago and which makes absolutely no logical sense to me. Please correct me here. - Why does the EHSI (Electronic Horizontal Situation Indicator) show the exact position of the SPI in direction and distance as soon as I move the SPI and create the so-called delta, and not the distance and direction of my selected steerpoint. - And why, if I don't reset to CZ and switch through the waypoints, every other waypoint switched as a steerpoint is changed by the same delta on the EHSI in direction and distance and the position of the waypoint is therefore displayed completely wrong, unless I a.) move the SPI again and thereby create a new delta to the now selected steerpoint/waypoint and then again have this new delta displayed on the EHSI, or b.) press CZ or TMS down and thus reset the SPI and now finally have the correct position of all waypoints switched through displayed on the EHSI again. Why does the delta between SPI and steerpoint affect all other waypoints and markpoints when it should only be related to the current steerpoint? - Likewise, the navigation block on the HUD and on the helmet display should, as far as I understand, show the slant range to the SPI in the third line from the bottom and show the distance to the steerpoint in the bottom line in Nav mode and in A/G mode despite everything. Unfortunately, after moving the SPI, the bottom line is no longer aligned with the actual and actually correct position of the steerpoint. This is what I wanted to show you with the two track files in the original post. Unfortunately, I see my problem here too: if I set 4 mark points and then ripple 4 GBU 38s onto them, as opposed to before, some of the mark points are shifted and the bombs no longer hit. But maybe the cause is something else that I don't understand. I hope you understand my question, despite the translation, and maybe someone can explain this illogical behavior with the F-16C to me. Thank you very much

Hello folks, @Lord Vader; @razo+r; @Layer_8; @BIGNEWY the original post has been closed, the problem is being coldly ignored by ED! Do you have the feeling that ED is not listening? Yes! Do you have the feeling that ED always answers directly: "correct as is"? Yes! The fact is that ED keeps bringing out updates and unknowingly introducing bugs. Often even bugs that have been there before in one form or another. And now back to the topic, and please get rid of Center Zero here! Yes, with CZ you can fortunately reset everything back to zero. But Center Zero is not the problem! As I wrote and as @Layer_8 also recognized, everything is OK on the HSD page on the MFD. Instead, since the patch mentioned, something has been happening in the background that shifts all waypoints to the same extent in the direction in which the TPod (or generally the sensor of interest) is looking. This is reflected, as I explained, on the HUD Navigation Data Block, on the lollipod on the HUD, and especially on the EHSI (Electronic Horizontal Situation Indicator) between the pilot's knees. Of course, an offset/delta forms when moving the SOI, but here before the patch the navigation data to the waypoints remained correct and did not shift. Likewise, before the patch this had no negative impact on setting and using markpoints or using weapons. Please check your product! Please compare with your own eyes the navigation data on the HUD and on the EHSI on the tracks that I sent you with an older video that I found. @Lord Vader your comment: "If you think this isn't working as the real aircraft would, please supply publicly available non-classified documentation to prove otherwise via private message to @BIGNEWY and we will look into it. Unfortunately, we cannot commit to changes based on personal opinions." is an absolutely arrogant audacity!

Hello @razo+r, hello @Lord Vader, Thank you very much for your answers. I understand that when I move the Tpod, an offset or delta is created. In my opinion, however, this should only affect the current waypoint/steering point. I cannot say whether this is or should be visible on the EHSI or on the lollipop on the HUD, also Nav data block on the HUD, but I believe this has only been the case since the aforementioned patch 2.9.9.2280 from October 30, 2024. Nevertheless, unfortunately this shifting of the waypoints, or creation of the delta, does not only affect the selected waypoint, but affects all waypoints at the same time. The same goes for markpoints. If I set several markpoints one after the other, the ones set first move. Thank you for understanding that I am asking this question, as the F-16C is one of my favorite modules since it came out and this "innovation" is driving me crazy. Tpod moves all waypoints.trk Tpod moves all waypoints navblock.trk

Since DCS 2.9.9.2280 - 10/30/2024 Slewing the Tpod moves all waypoints at the same time. When switching through the waypoints, all waypoints are then in the wrong position/direction/distance. Not on the HSD/MFD, but visible/recognizable on the EHSI (Electronic Horizontal Situation Indicator) and on the Lollipop and Waypoint information block on the HUD. The waypoints can then only be reset by pressing CZ-Center Zero on the Tpod/MFD. Markpoints are also moved, which makes it impossible to designate multiple markpoints and ripples GBU-38 at them. You can clearly see on the Tpod that the markpoints are moving and consequently the bombs are missing.

It is not a bug. In the F-16 in Ripple Mode the Pipper marks always the position the middle Bomb will hit. If you have 9 bombs, the 5th Bomb will hit were the CCIP pipper was at release, bomb 1 to 4 hit before, bombs 6 to 9 behind.

It is sale and I wanted to get a new plane. I would have loved to buy the MB-339. But as I found out, this module doesn't even have a flight director. That makes no sense to me! It's just part of a trainer. Will it be included in the module? Otherwise I don't even need to think about buying the MB-339.

It's really sad that such a simple issue is not fixed in 10 months.

Thanks! Since the Last patch in the F-15E it is fixed. But in the Harrier it is not fixed yet.

Yes, unfortunately, at the moment there seems to be no love for the MiG-15. The canopy jettison hasn't worked for a long time. You can open the cockpit manually, but you must depressurize the cockpit first. After this you can eject.

the barometric altimeter is missing the value for 29.89 inHg. It's also missing in the F-15E

As with the Harrier for years, the barometric altimeter is missing the value for 29.89 inHg.

How about a campaign? Hello ED, I am interested in the Mossie, but since I already have so many other modules to fly, it is only worthwhile for me if the Mossie brings a campaign with it. Are there any efforts on your part? Thanks a lot for an Answer

sorry, unfortunately this is currently not possible. please try it by yourself Version is DCS 2.5.6.55960

Hello, if i pre-cool the IRMV i know i need to wait 3 minutes for the RDY sign...and i think in AG Mode and on stores Page 1 time the IRMV selected it starts and the counter runs thru (and i can do other things until the countdown is done) -> but if i select another page or another Mode or another Weapon the counter stops and i need to go to AG Mode/SRS Page and unselect/select IRMV a second time and the counter starts new. i have checked this with a kitchen clock, it took 3 minutes again... so i think this is a bug

Precooling... if i pre-cool the IRMV i know i need to wait 3 minutes for the RDY sign...and i think 1 time in AG Mode and on stores Page the IRMV selected it starts and the counter runs thru (and i can do other things until the countdown is done) -> but if i select another page or another Mode or another Weapon the counter stops and i need to go a second time to AG Mode/SRS Page and select IRMV and the counter starts new. i have checked this with a kitchen clock, it took 3 minutes again... i think this is a bug

i tried a little something and in my opinion the following AWLS Channels works in Persian Gulf: AWLS 12 --> RW 19 --> Khasab AWLS 7 --> RW 30R --> Dubai Intl AWLS 14 + 15 --> RW 29 --> Fujairah Intl AWLS 4 --> RW 27 --> Al Minhad AB AWLS 2 --> RW 30 --> Al Maktoum Intl AWLS 16 --> RW 29L --> Shiraz Intl but, of course, this is not what the kneeboard looks like. i hope Razbam update und correct the AWLS in PG and Syria as soon as possible...but well, we know Razbam...

I edited my post for better understanding. Please try it out

Hello Razbam, - if i have selected Sensor Select FWD INS Mode and slew the TDC in HUD with joystick buttons (4-way-switch) --> the x-axis and the y-axis are inverted/mirrored. (With TV, IRMV and TGP it slew correct.) - if i want change a Waypoint per TDC with buttons on EHSD DATA page the y-axis (TDC fwd + TDC aft) are inverted/mirrored. - on the altimeter the window where i can adjust the barometric pressure has no 29,89 inHG --> after 29.88 follows 29.90 THX for fix this