Alighierian

Not required. As hmleao also pointed out, you can transfer licences from Steam to DCS via DCS home page - Profile > Edit / Delete > Steam Account | [GET LICENCES]. Given your steam account is linked, it'll retrieve any available licences, and give you the option to transfer. I've bought a number of modules via Steam for the standalone version that way, as I didn't have easy access to a credit card.

I did as much ('Tagged the Perry' in m01 = trigger zone for 7nm out, at which point Jester speaks up), and I also went through the normal steps for non-SC inbound/request landing. However, the vanilla carrier comms are still rather lacking, and like airfield ATC comms, basically revolve around 'just call inbound and request landing, and ignore holding patterns'. The main problem I had, basically related to expecting that 'charlie'-call, which is apparently part of the SC module, not the mission.

After quite a while I decided to try out this campaign in solo mode, non-SC. Almost right away in mission 1 I ran into that communication snag, however. I could contact Stennis, but only the usual 'Inbound', 'Request Azimuth', and 'Request landing' would show up. Didn't matter whether I used the easy communications or not, no other options showed up. I also tried staying in the holding pattern for about an hour, to the point I was basically running on the fumes of fumes at 1k, and even the tanker had already landed. Didn't do anything. For the next attempt I just ignored the communication for 1st landing step. After I tagged the Perry and initiated the 'Inbound' for good measure, I just landed. It progressed as normal after that, and the mission was completed with 100pts, allowing me to continue to the next one.

Such is life. Best of luck, and thanks for the help.

I experienced the same issue, non-vr. So far I've had two instances of taking some damage, and Jester being Jester, bailed out to inspect the ground up close. In cockpit view the canopy looks as if it's raised, whilst in F2 it's gone. I am using mods, though, including Drunken Sailor's F-14 cockpit mod, although that only edits the consoles' visuals afaik.

From the top of my head, as I haven't flown for a while now (new 1440p monitor and old GTX970 do not agree about DCS, still waiting for new GPU to actually be available): - take a long enough approach, so you're not cutting things short with last ditch drops - steady flying - ~400kts so you can impart enough energy - not sure about altitude, but 10-15k is fine for level flight JDAM dropping (lofting is also very possible, but a different ballpark) - go through the appropriate targeting setup steps (MA on, AG mode, JDAM's selected, fuses on, target(s) selected (depending on PP/TOO) - let the LAR% tick up to 100, and then a bit beyond (for a long drop), pickle around the 70-ish (not entirely sure on the value anymore, as, again, I haven't flown in a while) - repeat as necessary In regards to LJDAMing moving targets (very fun), it's basically the same as TOO, but for terminal guidance the TPOD laser (or other source) is used instead. Do note: the laser always overrules the GPS guidance from what I've noticed, so whilst you can do a multi-drop in TOO given you're nimble enough with the controls, that's not an option with laser designating a target, be it a normal GBU or a LJDAM. I had the most success dropping whilst flying on the same trajectory as the moving target, so I had the longest amount of time to keep the laser on target. In that situation, you have to drop long, as the normal GPS TOO marker will be outdated pretty much as soon as you drop, resulting in not enough energy to catch up to a moving target if you drop on 100 LAR%. As for lofting GBU-38's, something I've done quite a bit to deal with pesky long range sam systems, I basically follow the following method: - approach on ~the same level as the target if possible, so generally on the deck - once closed in to 15-10nm, kick the engine into just shy under full throttle (as to avoid the 15s engine burnout) - around the 5-4.5, start a rapid 45° climb, and pickle around the 3nm to target on HUD - turn, chaff/flare, and hit the deck again to avoid AA/SAM's - admire the explosions Obviously it only works with PP mode on known targets, but given you know the location(s), it's a fun way to hunt sams.

Having had Elmo show me how it's done, and some more practice regarding it, I think it's partially user error, and partially terminal impact behaviour to blame. The lighter JDAM's are either more lenient in their funnel, as Longiron phrased it, or they simply have more energy to spare compared to the GBU-32's. Given normal approaches are used, I never had an issue with the lighter JDAM's when dropped at the first instance of 100 LAR percentage number on the HUD. They basically behaved as if I was dropping normal dumb bombs via CCIP, with a relatively minor deviations based on target location, especially noticeable when doing Pre-planned multi target drops. That said, I don't think it's directly a bad idea to drop them long, even more so when using the LJDAM's against targets moving in the same direction as you are, so the bomb has enough energy to get a proper angle. It just requires mentally setting a different value to drop at, rather than the first time it ticks to 100. It would still be optimal if we could change terminal impact properties, though. I wouldn't be surprised at all if that would also solve this.

Is it similar to the issue I described here: https://forums.eagle.ru/forum/english/licensed-third-party-projects/razbam/av-8b-n-a/problems-and-bugs/7120826-reported-tdc-slew-button-inversion-after-firing-agm-65?p=7129318#post7129318 ?

Issue When deleting entries in the MPCD - CAS - RCALL page, you can CTD Reproduction 1: set up at least 2 target points via markers on the f10 map 2: load the target points into the harrier via 'Check MAP for Target Locations' 3: go to the CAS - RCALL page 4: select the 2nd or lower target point in the list 5: press the ODU button listed as ERASE until no further target points populate the selected slot 6: press ERASE again and DCS crashes on the spot So far it has a 100% replication rate on my end. It doesn't happen when deleting with the first target entry selected, however, only when done from one of the other slots. Video (video embed seems to malfunction for me at this time) ${1} dcs.log

You can always go through the steps again, especially if you for whatever reason doubt the accuracy, but it's not outright required with the new system. I have noticed that the accuracy can be a bit off with multiple TOO drops in a row, but against stuff like trucks and BTR's, it's still plenty accurate. If you also have tanks you need to kill, take the GBU-54 Laser JDAM's. The laser seeker head allows them to be used like GBU-12's and such, most likely including buddy lasing. At the same time, because they still have the JDAM GPS guidance, you don't need to have the laser active if you got the target set. The laser is simply there for moving targets, improved accuracy in general, and buddy lasing.

The 'multiple' aspect refers to not having to go through the whole target selection process again when dropping multiple bombs in a row, as it keeps updating what it will send to undropped bombs. Following the steps Recluse linked, you can more quickly and easily drop multiple JDAM's in a row. For (near) simultaneous drops, you still need to use the pre-planned method.

I can't open your replay for some reason, and it doesn't show up when I place it in my dcs OB tracks folder, where I still have another replay, which I do see in-game under Replays. After some more testing, I'm not sure why it's happening. The issue isn't that they consistently drop short every time, only when I use TOO-targeted drop at the optimal launch distance, as indicated by the hud. However, even then I have had instances where it does land on target. I modified one of the missions to start further away from the target zone, so I have plenty of time to set up for attacks. Even with this controlled setup where I don't have to turn, I keep getting them land short. I've tried to keep my speed around the 360knt, alt ~10k. The video is from a run where I still had a few visual mods active, but disabling those to redo the tracks had no impact on this. ${1} AV-8B GBU32-3.trk AV-8B GBU32-2.trk

I should probably have updated the initial post as that was an earlier, and partially incorrect, assumption. What I noticed: The IRMV sensor window (both D and F) should, as far as I know, only have slew enabled when the sensor mode is set to IRMV. In INS the slew and target lock are unresponsive. After certain actions, the IRMV sensor view ended up with inverted slew commands, both in X and Y. Initial thoughts: I initially experienced it after going through a firing cycle, that being: acquire via TPOD - uncage - lock - fire - uncage - acquire next target with IRMV view - lock - fire, which is what I thought it was related to, as mentioned in the first post. Further testing: After seeing another post about INS map slew being inverted, I went back and checked what mode the sensor view was in, which was INS. Some more testing resulted in the following: Using the TPOD and pressing TDC Down (action) to lock on to something, as you would with the IRMV's sensor view, and then uncaging an IRMV, resulted in it activating in INS mode with slew commands active and inverted. I've not had it happen with the DMT TV sensor so far, only with the TPOD. Switching to a different sensor mode and back disables the IRMV window INS slew again. edit: some further and slightly more systematic testing: DMT-TV mode, DMT freely slewing Uncaged IRMV window displays TV, and follows the TV target point, updating only when slewing stops [*]TPOD-TPOD mode, TPOD freely slewing Uncaged IRMV window displays INS, and follows the TPOD target point, updating only when slewing stops [*]TPOD-INS mode (didn't even know that was a thing, tbh), the TPOD doesn't slew until after TDC Down is pressed. TPOD slew inverted and slowed down, Y significantly slower than X (horizontal flight, terrain ahead as target) Uncaged IRMV window displays INS, inverted slew, faster than TPOD-INS slew, TPOD slew follows IRMV-INS slew, resulting in a faster TPOD slew. In all modes setting the sensor to IRMV enabled normal IRMV slew behaviour (non-inverted, TPOD/DMT-TV not following IRMV slew) I'm not entirely sure how the TPOD-INS mode fits in, as the normal TPOD slewing updates the map marker. Please to correct me if I'm wrong on this, but is IRMV-INS meant to be used with the EHSD for map location-based targeting? I'm wondering if that's the case since when I have the EHSD open and an uncaged IRMV set to INS, it follows the map cursor slew. That just makes me wonder what TPOD-INS is for, and why it activates when the stores page/IRMV sensor view is on the other display. At this point, I don't know how much of this is user error / me misunderstanding certain functions, or if parts are potentially not working/interacting as they should.

Ah alright, hadn't found that function yet. I'll think I'll be fiddling around with it, as the default yellow/green has pretty poor contrast against the moving map. That was actually the reason I couldn't figure out how to operate it back when I first tried the AV-8BNA...

After reviewing it again, I've noticed it's linked to the INS mode and the TPOD. The Mav sensor should not be slewing when the target mode is set to INS, and doesn't do so normally. However, when using a TPOD for targeting, pressing TDC Down and then uncaging will enable INS with inverted slew in the maverick sensor view. The same happens when you target something, fire a Mav at it, and then uncage.

The symbology turns red when you're in the EHSD - Data page as of nov 4th patch, so that part is normal afaik. It goes back to yellow/green when you click the DATA button again.

The testing I did yesterday whilst learning the new operation method was mostly with the normal JDAM's and the laser version, which is showing the LAR on the EHSD now, so I slightly forgot about the mk83 JDAM. I'll give it a whirl and see if it's still bugged. Edit: Just tested it with absolute coordinates (pre-loaded via map markers), and I might have slightly messed the first one, so that was partially inconclusive, but still appeared to be dropping short on the 2nd marker, which was correctly placed. For the next bomb I used TOO targeting, using the laser for additional accuracy of the target location, and it dropped ~0.15nm short at optimal launch distance. It does show the LAR circle on the EHSD now, though, so that part is functional. ​ Locked target: the tank closest to the water. This angle is from after the strike, so it's furthest out from this view. Impact crater is visible between the crosshairs and the waterline.

Indeed, it's nice it doesn't just outright fail to join or crash your game, that's for sure. It would still be nice, however, if the message in-game was tad clearer about it. The 'You are not authorized to land' sounds a lot like 'Go around, runway occupied' in a way. Having it mention you need the SC module would aleviate that. For example: 'You are not authorized to land: Supercarrier datalink module not installed.', with 'datalink' being optional for thematic flavouring. Although it's only a small thing, it would make it pretty obvious why interacting doesn't work, without first having to ask around or google it, if it's not mentioned beforehand somewhere.

Thanks for the heads-up, it's nice to know in advance something like this has to be updated as well this time.

On another note: I just tried A2G - Infantry assault and the Chinook ended up unable to land, hovering ~10m above the ground. In an earlier start, yesterday or something, it was in the same area as far as I recall, and it did land as intended, if you ignore the power lines it kinda flew through, that is... ​https://i.imgur.com/i1CtnAQ.png https://i.imgur.com/P7iNDZ7.png

Yea that would do it. A bit annoying it doesn't allow any interaction with 'plebian' (non-SC owner) players, though. It would be nice if you could still use the very basic CV features, those being TACAN beacon, catapults, and the wires, whilst other people in your session get the full supercarrier experience. Edit: Seems to be what the issue was. I put it on the CVN-70 Carl Vinson, which isn't part of the SC bundle, and it plonked me right on the deck, as intended. Edit 2: The Carl is very much outdated, so I swapped it to the Stennis (which is listed in the SC dlc, but w/e), and it's working as normal now

Nope, neither repair nor deleting that folder worked. I guess I'll just stick with land-based starts for now, and maybe a future update will fix whatever is causing it, as it seems to be something wonky I might not be able to fix on my end. (edit: A bit hard to say for sure since I still kinda suck at deck landing a non-harrier, but it also appears as if it's not catching the wire. I just did a similarily crappy approach and landing in the instant action, where it did catch. Will need to try it some more and do a normal landing to see if that's indeed the case)

Issue: - GBU-32(V)2/b, the mk83 JDAM, drops ~0.15-0.2nm short at HUD optimal launch distance - The EHSD is missing the JDAM viable launch range circle (side note edit: further testing on my end showed the GBU-54 LJDAM is also missing them, but the GBU-38's still have the range circles) - fixed as of nov 4th's patch Replication: Step 1: Equip GBU-32(V)2/b's Step 2: Set up JDAM targets (mark on map, load into computer, select desired targets) Step 3: execute attack as normal Result: - No visible EHSD viable range markers as the GBU-38's have - Launched at optimal range (100 on the HUD), the GBU-32 drops short of the intended target. Track and clip: I dropped two as comparison, one a tad late around 88 (earlier test was at ~100, also dropped short), and one around 50. The second one slapped the intended target with no effort, the first one tried to glide over but ran out of energy, dropping short. Also added the log, but not sure if that part is done properly. ${1} AV-8B GBU32.trk dcs.log

Currently running the latest OB version (2.5.6.55960) and already tried reinstalling the F-14. Will probably have to give the repair/clean a shot as well.