viper2097

ED, you did an awesome job on the new cockpit. By far the best looking and most readable cockpit in VR so far! Well done, thank you.

Deka, could you just update it to those values? They work perfect. No more effort needed. Thx.

Is a hotfix planned for the CTD wingman issue? I hope that this should be fixed over the christmas holidays :-/.

Thanks for that awesome amount of bugfixes in that short time! JF-17 is done outstanding. Outstanding support after release. Keep on doing that great work!

Lol, Deka fixed in two weeks more bugs then Razbam in two years. Fly the Harrier if you really want a reason to rant.

I have reported dozen of bugs and things which are done wrong. They just don't care about and ignore it. Take a look at the bug section. If I would start to report everything that is wrong according the Tacmanual, then this would be a full time job. For what? Even more ignorance? I guess they know on their own what all is wrong, but as I said, they just don't care. For me it seems, that Razbam does not have the intention to make any real good moduel in the context of what DCS stands for. They are just makeing casual modules with only as much effort so that the people don't get full crazy about what they spent their money at. Take a look at whats happening now: The bug section here is FULL of game breaking and unbelievable annoying bugs which should be fixed since years(!). One thread after the other comes up with the same question: "Why is the Harrier in such an awful state and why is nothing happening?". But no, Razbam is not interested in fixing any bugs, they decided to do now some JDAM implementation. Since 4 months. It seems like that they feel that quantity is much more important then quality, if they even work on anything. We will see to what this leads to.

The Tac manual is the "official" manual of the Harrier how the weapon employment works. Similiar like the NATOPS is regarding normal flight operations. You want five things? I give you fifteen: In my mind I have: 1. Bomb drop line when fuzeing is set to safe should blink. 2. Sidearms symbologoy is wrong (symbol on HUD looks different then we have it in DCS now). 3. Sidearms cage/uncage is not modelled. IRL you need to uncage it first that it is able to lock on a emitter. 4. Complete timer functions are not available (TOT, TTT etc.) 5. As long as the AGM-65 is not locked, the FOV/undsignate button should change the FOV. It does not change the FOV, it always drops you back to boresight. 6. LSS function is missing on the TGP. 7. Whole wind compensation is missing in the ARBS. Then I opened the Tacman and scrolled to the AGM-65 section: 8. Uncage of the IR-Maverick should also work during the 3 min. cooldown, but will, however, deliver a fuzzy video feed. 9. Pressing DTC while slewing should move the Maverick seeker with twice the speed. 10. Waypoint incr. switch should toggle polarity when in slew mode with the AGM-65. 11. HUD Symbology for Maverick is wrong. While in slew mode, its a quite big box. With a lock, the box should get as big as the target. 12. When IRMAV is boxed in the HUD, it only indicates that the Mav sensor itself gets slewed. At the moment it indicates a lock. 13. If the slewed target is outside of the keyhole, the HUD indication should start to blink. 14. IIRC, the small crosshair blinks when it is locked in DCS. This is wrong, it should only blink if it has a bad lock. 15. Again AGM-65: The aiming cross itself should be closed in the center while selewing. If there is a lock achieved, the aiming cross should open as much as the target is big.

Hey devs, please consider a little detail: Its an unwritten law how the switches behave in DCS: Right click -> Switch forward / up / clockwise Left click -> Switch backwards / down / counter-clockwise Most of modules, especially new released modules respect this and are working like this. You have it now upside-down in your module. Maybe you could think about to get in line with other modules. Would be a big help if this is constant in all DCS modules, thank you :thumbup:.

At least it fits quite good to the current state of the Harrier. :( Unfortunately Razbam does not see any reason to listen to anyone here, or to improve / fix important things. :noexpression:. I give you a good advice: Never ever take a look in the Tacmanual. Every single thing I studied from that yet is modelled wrong in our Harrier in DCS.

DCS bug. Since ever. No one care about. https://forums.eagle.ru/showthread.php?t=245206

Thanks for the reply. One thing we forgot to show in the track: If I'm lasing the moving target myself, the GBU hits spot on. If I'm lasing for my buddy, it gets trailed as in the track.

Somwehere I read, that the host of a mission needs to spawn on the Tarawa, and then it works also for all others. No idea if that is still true.

Also a keybing for the throttle cut-off / idle detend would be needed, to use it with the WH Throttle. (Button pressed -> Throttle cut off / Butto not pressed -> Throttle idle)

So are there any news about that? Issue is present since a long time, I guess ED is fully aware of it. I report it. Even that ED is fully aware of it, I'm asked for a track file. So I, and my buddy, invest the time for setting up a mission in the editor, fly it, gather all the tracks together and report it. I post it here as it was demanded. Since a month only silence. Even I asked if there is something else needed. I don't ask for a fix within a day. Only a "Thank you for providing those data. We have been able to look into it and replicate the problem. We've added it to our bug-tracker and will fix it asap. Thank you for helping us and spending your time." would have been nice and more then enough. But just ignorance and silence is not very polite.

As by the reply of Grimes on September 20th, it should have been fixed already. Its now 3 months later, still present. Any news about that issue?

As stated in the updated pocket guide (as far as I can see, all other chapters remain the same, with the same state from initital EA release, so the update only means a new cover picture and the added JDAMs/ATHS), the TGP is needed for laser ranging. So far, the laser raning was not modeled in the Harrier yet. The target coordinates stay the same before and after the use of the laser. In oposite to that, the coordinates change when useing the Laser in the A10c. So is the laser ranging effect now also added to the Harrier or is it still missing? Is the TGP slew with axis now also fixed? Have all the core issues regarding the TGP now also been fixed, or will they stay still the same? Especially, the suddenly not anymore working laser could be affecting the JDAMs useage. After there have been silence for more then four months (I guess for the JDAM/ATHS developement only) on the Harrier, will you now start with bugfixing for the year long known bugs or whats the plan? BTW, and just my personal opinion: Your signature is quite rude and not polite to your paying customers. Especially as there are many mistakes and typos in the "updated" pocket guide, I assume that the coding is done more carefuly.

Interesting to read. In the german language, we do not use the word "Teufelshund" every day but regulary. We don't use it in a bad way, more the opposite. We use it for someone who did something very brave with little to none chance of success. No matter if he's a good guy or a bad one. I don't have any idea about the historical meaning, its for us just a normal word we use. Edit: Still need to think about it and found that: https://www.google.com/amp/s/www.urbandictionary.com/define.php%3fterm=teufelshunde&amp=true So is it really that bad to use the word? Would have never thought that, as we are useing it more in a positive way... Will try those, thanks :thumbup:. Sounds good, me and my squad like that :pilotfly:.

Try the pitching deck mission. Not as good, but also very good.

Aber um zurück auf den supercarrier zu kommen: Das klingt ja schonmal besser. Zwar nach wie vor keine Aussage ob EA release oder final release, aber immerhin...

Das bouncing wurde gefixt, das sliding ist seit jeher gleich...

Dann lies den Thread mal fertig. Zitat Nineline auf der nächsten Seite: Ich habe um Aufklärung und eine genaue Aussage gebeten. Mal sehen ob es die dieses mal gibt oder ob man lieber wieder Leute bannt... Ich verstehe die Aussage von Nineline jedenfalls so, dass das Decksliding generell gelöst werden soll und somit nichts mehr mit dem supercarrier, oder dessen release zu tun haben wird. Entsprechend DCS Historie würde das wohl (pessimistisch gesehen) heißen, dass man jetzt mal den supercarrier rauspusht, in 1 1/2 Jahren dann das Decksliding löst und der Carrier in 2 Jahren EA verlässst.

Die wichtigste Frage für mich ist, ob sie das Decksliding fixen. Solange das nicht gefixt ist, werde ich den Supercarrier nicht kaufen.

Sorry, I don't get it. Wags said: Which sounds for me, that the deck sliding needs to be fixed prior the release of the supercarrier. Still not answering if release means "EA release" or "final release". You say now: Which sounds for me that a "fix" will be "released" to adress that issue in generally, and fixing that issue has nothing to do with the supercarrier or its release directly. Please be so kind and clarify if: The decksliding will be fixed prior the supercarrier will be released in EA. The decksliding will be fixed prior the supercarrier will leave EA. The supercarrier will be released in EA either the decksliding is fixed or not, because it has nothing to do with the module. Thank you. Especially for me, and maybe also other people, the question if decksliding is fixed is a very important factor on the question if I will buy the supercarrier, because I see it as Wags wrote: Its a must.

As Wharthog user I would really need: A-A Mode / else NAV A-G Mode / else NAV To use it with the boat switch (Fwd: A-A, Mid: NAV, Aft_ A-G) Flaps up/ else neutral Flaps down/ else neutral To use it with the flaps switch on the throttle base(Fwd: Flaps up, Mid: Flpas neutral, Aft: Flaps down). Gear up Gear down To use that also with the Throttle base.

Honestly, I'm fine with changeing lasercode through the com menu. All Pylons -> all digits -> enter code, fine. I would only suggest to make it only possible to change the Lasercode AFTER rearming, and BEFORE DTC insertion. At the moment, you can only change it after DTC insertion and read in. That feels a little strange when the laser code on the MFD changes magicaly.