Vakarian

It doesn't matter, you are using SC ATC (some parts of SC ATC got through to the non SC users AFAIK), and it's not working yet with the pattern the Harriers are using. Also, Tarawa landing operation has been not really working for a while now. The "best" thing you can currently do is fly the pattern with out comms at all until that gets fixed.

Harrier is still not supported by Supercarrier

I literally don't care about the new features to the Harrier while we have bugs that are festering for years without any hint of them actually being looked at. In my opinion, all these new shiny things (nobody asked for in a first place) are just a tactic to make community look away from all those broken and half-implemented features

Wouldn't hold my breath for this. We are all witnesses on how the current "simpler" Harrier, the N/A version is doing and how it's development is progressing...

Seems like you missed a video on Mav boresighting. Watch that one and then Mavs should look where the TGP is pointing at

You are 99% still in INS mode. You need to press Sensor Select depress x2 quickly to transition to TPOD mode and that will let you take control of the TPOD and slew will be as intended then.

After the North Arrow on the TPOD gets fixed, that should get you rough idea how you should align yourself if you want to i.e. do a snakeye run at the convoy. Also, if you do a WINC long when the TPOD is looking at the convoy, you will get a target mark on EHSD. By using your location, target location and the approximate knowledge of where the TPOD is looking (left, right, behind,...) you can plan out a rough attack pattern

I do believe FM is in the .dll files (haven't checked for Harrier, but for other modules it is) so you can't really change it as that's compiled C++ code. But yeah, FM does seem weird sometimes as Harrier manages to pull off something that logic says it really shouldn't be able to. Thanks for sharing the info from the Discord. Too bad that the forums is the last place RB posts their info, if they post it here at all

@Bbow Thanks a lot man for the testing. This basically proves my hunch that even if the Pegasus is really powerful engine, it is still not that much powerful as I saw the other day. I mean, I climbed (although not at the constant rate, I did 2 stage climb) to a FL400 and had 7000lb of fuel when I got there. So 700lb of fuel spend for a climb from Nellis to a FL400 with a not so light bomb load... @RAZBAM_ELMO Can engine performance / FM get another look on? From the testing done, there is enough discrepancy to warrant another check. We are not talking about 5-10% difference from a real thing but a way much more

@WiskyThanks for this info. This thing is more powerful than I thought then... I expected to have some issues climbing up there with this kind of loadout, but apparently it's close enough to the real thing that it's fine my me.

Ofc, 102% max contionuous, and also watch out for the JPT. The "max" I wrote was in regard to the Wiskeys comment that higher altitudes allow the engine to go too fast, and I understood it as it might go over 110%

I mean, I know that the air is thin up there, but M0.88 seems a bit fast as I wasn't in clean config. Didn't see what was the max speed there as I went for the bombing runs, but I will try to replicate this in the next couple of days. Yeah, for the RPM, I did test the maximum RPM and it didn't go over 110% which is what I thought was the max. I am aware that this engine is a beast and it can climb a lot, but this seems way too easy. Also, as you can see, I mostly type "seem". I'm not sure it's a bug, so I'm trying to see what all of you think of this. I'm always open to learning new things and would like to be corrected if I'm wrong.

Yesterday in my squadron we were goofing off, so I thought to give a Harrier another chance after I gave up on it with the frequent breaking of working things and implementing stuff incorrectly. Loaded 10 Mk-82 AIRs (singles on station 1&7, doubles on stations 2,3,5,6) + gunpod and wanted to see how high I can go. I got to FL380 without much issues and settled there at M0.6. That seemed fine, but then I started to accelerate as I leveled off. Next, as I got quicker, I started to climb more and got to FL450 and when leveled off there I got as quick as M0.88. So, M0.88 @ FL450 while having 10 Mk.82s and a gunpod. That seems a little bit too powerful, something seems off. I did a little checking in NAVAIR 00-110AV8-4 and nothing there suggests that this should be valid, as service ceiling with only 6 Mk-82s + gunpod is at FL331, combat ceiling is FL364 and I got 10000ft higher with a way draggier aircraft. Did anyone else notice anything similar?

Guys, how can you not see it. Kiowa it at Bell, so they can't take any images to use them as SOTW and they have to keep silent about it. <wishful thinking only, don't take this seriously>

Just a note @BIGNEWY maybe lock this thread? Otherwise this could easily turn into the same argument that was present in more than a couple of threads before

Is it too much to ask some proper customer service and proper bug management? Why does it matter how much has anyone spent on any product? Let's think of it this way. How much hours have any single of bug reporter spent trying to reproduce a but? Are you @Mr. Big.Biggs gonna pay my hourly wage? I would rather either play something I enjoy or do something else than bug hunt, but I do it did it because I wanted to improve the module and give my feedback to the devs about what is wrong. When I get treated like this, that's when I stop investing my own time to help someone else. It's either mutual benefit or none. We have bought a product, enjoy using it up until every effort to improve that module gets met with a stonewall.

Do you hold weapon release button or just do a quick press? If latter, that's the reason. You need to hold weapon release button long enough for info of the target to be transferred to the JDAM and then it will release

Well it's blatantly obvious. If every single aircraft has the same issue, yes, then it's the ED issue and it affects every aircraft out there. However, if any issue is related to a couple of aircrafts or less, you can't say it's ED issue and ignore the problem. There is no way that sounds logical at all and is really insulting everyone who tries to raise any issue

Oh, I totally missed that part. That would then be a no. Seems like RB made some fixes to the mission and should be released soon. Try to edit the mission and add ammo and fuel truck so you will gain access to the ground crew.

It is known issue. Current workaround is that if you forgot to remove chocks before startup, connect ground power and turn on the APU. Then shutdown engine, remove chocks and start up again. Your alignment will remain, all weapon, waypoint and other settings will remain in place

Harrier has so much thrust at idle that the it starts to roll. That is the reason chocks should be in place before you actually start to roll or you hold the brakes. Once ED sorts the issue the chocks will fix this problem

Oh, sorry. The OP was a little ambigous. I just went through the controls and it seems like there isn't bindable option for that (HMCS Power On/Off switch), so we would need to ask ED to add it.

Did couple of tests yesterday and I can say it's miles better than before. I can now confidently take out stuff with the gun, so I'd say it's fixed. Now, as the gun did get fixed second time now, can we please get to keep it that way?

UFC brightess knob does either 100% illumination or 0%, there is nothing in-between. That is what the OP is trying to say

From todays' changelog: Fixed: AG Gun gunsight boresight Hmmm, I thought it was correct, and we were all flying the attack pattern wrong... Oh well, time to test this later today