Gizmo03

It‘s been pretty long since i tried it on the right eye just to see, if it works. But when i tried in both seats i did it just as it is written in the manual. That worked perfectly for me. I‘m short in time at the moment but next time i can test it again with the right eye.

Sorry for my late reply. The right eye is not an option for me. The left eye is the dominant and the vision is a notch better on the left eye which makes it even more uncomfortable to use it on the right eye. I would do everything needed to change that if i would fly this aircraft in real life, but definitely not for a computergame especially if we have the option to use it on the other eye. But yes - of course i tried it on the right eye. Just to see if it‘s just me doing something wrong . Tbh: there is nothing easier in this aircraft than just boresighting the IHADSS and if you do it in VR on the right eye according the manual it works perfectly. But it‘s still sad. That was the „WOW“ - feature of this aircraft for which it was really famous and well known back in the 80s and it‘s not working (or at least not without a stupid workaround which doesn’t even work always) on the left eye in DCS.

No problem at all I noticed that i might took the wrong thread for my question - there is another thread about this issue specifically for the use of the IHADSS in VR on the left eye and both eyes. And it's not such a big deal - as long as i do the boresighting as in the screenshot everything is spot on. But it shouldn't be like this in one of the most complex ED modules in DCS I thought the same already. Maybe it was always off for me because George is not boresighting the IHADSS with the left but with the right eye. I never tried to use the IHADDS on the CP/G seat without boresighting it while using the right eye. Only while using the left eye. When i use the right eye, the boresighting works perfectly. But i just prefer to use it on the left eye - that's why im struggeling

No guys - it's not the range setting. It has nothing to do with the range. I know how the range is calculated in Auto Mode. Engaging a target at 12 o clock with the wrong range would lead to impacts in front of or behind the target - short or long. But that is not the problem. The problem is, the impacts are all way off to the left (same distance). Also - as i said - the PNVS and the TADS are completely offset. The boresight procedure according the manual works fine..... as long as you use the IHADSS on the right eye. But on the left eye it just doesn't work - at least at the CP/G station.

I think you didn't understand the problem. If i do it as you said and as it is writen in the manual it just doesn't work at all. The impact point of the rounds is up to 50m to the left of the aimingpoint. Furthermore the PNVS and TADS are completely offset. The screenshot doesn't show the way i'm doing it while wondering why it's not working. The screenshot shows how i do the boresighting in order to get it working. Only if i do it like in the screenshot i have the canon precise as it shoud be and the PNVS picture fits exactly with what i see outside. I always switch to the Auto mode after boresighting - otherwise it wouldn't make sense . That's interesting because if i did so in the past my IHADSS wass completely offset and useless. That's why i did it always again. Was there a change? Maybe i have to give it another try - thanks.

I have to say i'm really fed up with this. I mean even though in the real aircraft the IHADSS is monted on the right side we have the option to use the IHADSS on either - left or right - or even both eyes which is great for everyone whose left eye is the dominant one or whose right eye has poorer vision and i really appreciate that but it doesn't help if it doesn't work. I am using VR and the IHADSS on the left eye. Starting in a cold and dark cockpit i can boresight the IHADSS in the pilost's seat according to the manual and when i'm aiming with the IHADSS the gun hits almost perfectly on spot. On the CP/G position it's just a disaster. I had a nice little workaround which seems not to work anymore. Now i always have to be offset while boresighting the IHADSS which is really annoying. I even don't fly very often with the Apache just because of this. And this makes the whole situation even worse because after one month not using the Apache i always forget how much offset i used the last time. So everytime i want to use the Apache i have to do one flight just to find out the offset again by boresighting - firing - observing the impacts - boresighting again ... until it works. I did that just now and noticed again how annoying it is. Then i decided to make a screenshot everytime i'm boresighting and the final one - which worked goes to my AH-64 kneeboard now. On the screenshot you can see how i "boresight" my IHADSS in order to get it work properly. But this can't be serious, can it? Another question is: if "George" uses his IHADSS already properly during a flight, why do i have to boresight it again when i switch to the frontseat? Shouldn´t the IHADSS be aligned already?

Same for the JF-17. The problem with the CBUs was already there before this dispute. Last summer (already during the problems between RB and ED) there was an update (11.07.2024) where this problem was fixed - also for the Harrier. After this update it worked for me. But a later update broke it again. I think if they were able to fix that without the help of RB in july last year, they should be able to fix that again. I‘m really not sure and i might be wrong but i think there was a post in which one of EDs CM wrote that ED doesn‘t want to put their hands on the RB modules while these legal things are going on (which would be understandable) but it could also be that i just missinterpreted that post. Unfortunately i don‘t find it anymore. EDIT: i think this was the post i‘ve read. And maybe i really missinterpreted it but i still think it‘s like i said:

Puh guys ….. you have to change the title. When i‘ve read „Su-25A Announced“ i was really celebrating just to find out that it‘s „just“ an update to the FC Frogfoot and it will be for free in the future….. i was always dreaming of a FF Su-25A and for a very short time i thought it will come true. That was a pretty disappointing experience….

I have to say, i'm a bit disappointed. I tested the remastered version and i think this should have been a free update to an old module and not something we have to pay for. I was expecting a bit more for 10 USD....

FIRST go to EHSD - DATA - AC. Enter the coordinates and the Variation. THEN switch the selector to GND. Make sure the UFD rotary is on "bright".

Hast Du mal probiert die Zuweisung nur zu löschen, nicht neu zu belegen und danach dann das Spiel neu zu starten? Danach konnte ich ganz normal belegen.

„Einstellungen“ (also das kleine Zahnrad oben im Hauptmenü, wo du auch reingehst um z.B. die Grafik oder das Gameplay einzustellen) - dann den Reiter „Verschiedenes“ und dort den Launcher deaktivieren.

Hatte das selbe Problem - mit einigen Modulen und betraf jedesmal die selbe Achse. Neustart allein hat nichts gebracht. Erst die Belegung löschen, dann neu starten und dann neu belegen hat bei mir funktioniert. Ich habe die F-4 noch nicht installiert. Gekauft ja, aber ich warte noch etwas, bis ich mehr Zeit dafür habe. Daran sollte es also nicht liegen. Das Problem wird in einigen Unterforen und auch im internationalen ED Teil bereits diskutiert - bist also nicht alleine. Das rote Ausrufezeichen habe ich so auch noch nicht gesehen - hab mich auch gefragt, was das bedeutet. Es weisst auf jeden Fall auf irgendeine Schwierigkeit hin

I have the same problem. But i don't have FC2024. I have FC3 and it always says i can install it but when i do so it just restarts the game with the same message but the problem still exists. EDIT: looks like it's not only with the KW. Same with the Hind and the Throttle of the F-16...

Auch verschoben.