XCNuse

Unless that has changed; it's been a hot minute since I've had to actually reset my alignment (aka, several months at this point). It seemed to always work though; and by work I mean... that's totally not realistic, but INS aligned and DL came back correctly it seemed. I would hope they've fixed it by now at least, as that's definitely incorrect behavior! @ OP again, if you do a NORM align you MUST CONFIRM the LAT, LON, and Elevation early during the INS alignment procedure, they're put in for you automatically, but you still have to confirm them by clicking enter on the UFC.

Just tried it again. I realize what you did wrong OP; you indeed did a standard INS alignment and did not confirm the LAT/LONG/ALT in the DED. And I know this because I was able to just do it, and at 240 I see bulls and the AWACS. The fact your screenshot does not show bulls, means your INS is wrong. If INS is wrong, your datalink information will not display correctly. And I know you did it as a standard align, because of the time and accuracy numbers on the top of the DED.

at least in OP's picture, FCR was actually off-off, not in standby off. He has MIDS on, so they SHOULD be getting DL info, but again; there's nothing off the nose in the mission except the AWACS itself, which SHOULD show up, and did for me. Side note OP, the far right top and bottom switches around avionics power don't need to be flipped up (I think it's DL and MAP). Datalink is over the MIDS. Either way, you should get datalink with the FCR off completely, so it's weird to see not even the AWACS visible. OP out of curiosity, did you do a standard align or a fast align? Reminder if you to a standard INS align, you MUST select the location and elevation on the INS page on the DED and accept their location with the enter button on the UFC. With a stored heading alignment you don't select and confirm the location. Other than the FCR thing (at work so I can't test), the only thing I can think is the INS was borked in some fashion by doing one of those things incorrectly. Generally speaking; there's no need to use the standard align... really ever in DCS. Even if you move, it seems that stored heading will update. That said, the only reason again you should be resetting INS is if you lose all power and deadstick a landing and repair or something similar. But again; with nothing actually off the nose of the aircraft in the mission... the only thing that we'd be seeing is the AWACS anyway; until you take off at least.

In theory the only thing you should be getting at all is the AWACS anyways; as there's nothing else off your nose that you have in the mission to see. Also worth noting at times you can lose datalink tracking information depending on line of sight.

Whew! Ok LOL Obviously was having one of those moments "it's me, it's gotta be me!" Thanks for the follow up and links!

Huh... I wonder if this is the issue I was having back during OP flight then; I couldn't figure out what it was because I don't remember the circumstances.

Was flying Liberation mission yesterday; got caught up in a merge with some non-friendlies, spat out some Sparrows, had entered dogfight mode to get some 9Ms (specific era fight), after returning out of dogfight mode; my radar page didn't show the typical full bar scan like I'm used to. Aircraft stayed like this for a few hours later; I could pick up targets, but not 100% sure if it was because I swept them with the nose or not. But it was and would pick up some targets (unsure if it was picking up everything as normal or what; but I was focused on ground attack so didn't spend much time on this). In essence, the azimuth scan bar was bumping left/right basically like you'd see the altitude move around as it did its passes. Instead of showing full left/right sweeps; it just showed a vertical line (a MOVING vertical line, but it never moved 2x pixels outside centerline) I've tried finding anything like this in all of the guides but couldn't find anything. Replay is obviously too long to figure out what I did anyways. But I'm 100% assuming it hit... something. But I know I wasn't in a DF mode. Obviously going back to A2A after A2G flights, it was still displaying like this. TLDR: Radar wasn't showing full azimuth sweeps, just 1-2 pixels right, 4 pixels left, (2px from centerline), showing the standard "sweep", but not displaying angles. All azimuth scans would act like this, after this shot I took it down to the lower (30?) degree azimuth and same thing, never showed the standard left/right angle sweep.

worked no problem for me; you had nothing to look at though, unsure why you didn't see AWACS, but tossed in some SAMs and Mig29s and they showed up right as I went into NAV. Only thing I see different is my FCR is on; which in theory shouldn't matter. Side note, you had -AWACS enabling twice on the AWACS. That also may be why; it may have been turning itself off? When you put down an aircraft set as a type, be it CAP, CAS, AWACS, Refuel; you don't need to put in that task again; it's already preprogrammed in.

that was tried as well multitude of times, nothing was able to launch the rockets unless they were the only things loaded onto the aircraft.

Ended up managing to get it to work basically first try the other night. Maybe I'm just not used to how little the search radius is on this versus the other aircraft.

If that's what that is, then I've had it work once or twice, but it was doing that mess. No other module acts that like nor does that, and I swear I've had other modules with LSS be able to find a laser MUCH farther away, and find the spots instantly.

So that's great and all but; is it not a big deal that it took the Viper literally 40+ seconds in that video to actually go to where the laser was pointed; aka the target? Clearly this is incorrect behavior. In SinglePlayer it went to the location instantly as it should. This video only kind of proves further to me that there is definitely... absolutely something wrong in multiplayer with LSS on the Viper. Don't get me wrong Skip, I hugely appreciate it, but ED needs to see this; because there's DEFINITELY something up; this behavior is 100% incorrect!

Yes, I've tried everything. I would really love to see someone else prove to me it works in multiplayer with other aircraft because I'm beginning to think it doesn't.

So I've managed to get it to work in SP, still have yet to get it work in multiplayer. Not altering what I'm doing. Interesting difference I'm seeing though; in SP the LSS will search a MUCH larger range, I can see it sweeping around quite a lot. in MP, it won't sweep but 2-3 degrees, it barely moves anywhere

This is entirely it. HARMS, as according to what BN and others have stated, usually stay above the targets and explode above them, versus running straight into them. And while it's great DCS "models" this........ DCS' damage model on vehicles etc. can't make sense of how this is supposed to function. This is where ED and what happens IRL need to be written up on a drawing board along with a few other things; where, it doesn't make sense to simulate one aspect, but the game engine itself doesn't function with said simulation; thus.... breaking the entire simulation aspect.

Would be like 30 minutes in, and file is too large to do it from where I am I'll attempt to set up a quick mission to test it tonight though; but unless everyone can prove me I'm wrong and that it works, I'd love to see it or give me details beyond what I could possibly be doing wrong. DED-misc-lasr both show 1688 TGP shows 1688 below LSS buddy or jtac lazes uncage TGP goes gray and wiggles dot around forever. I've had TGP zoomed in, zoomed out, EXP mode, no EXP mode, next to targets; viewing targets... etc

Tried again last night; buddy in JF17. Set the codes in UFC, DED confirmed 1688 across the board, TGP on MFD showed 1688 LSS .... no dice. Even pointing TGP right near the target, it failed to find anything at any point in time. LSS was pointed on flat ground in middle of desert, no trees or objects in the way. Really would like ED to respond how this is meant to function, because I can't get it to work.

Hey wow it works! Just don't forget to shut that door LOL So glad I ran into this thread, I was always removing the pylons and re-adding them!

It might be this; but isn't it by default set to 1688? Definitely know for a fact I was in range, but if it's not set to LSS same code as laze code by default then it's possible; I've probably gone in there and noticed LSS code before in the DED but haven't bothered to check it since I realized the viper COULD LSS. I suppose it would make sense that you wouldn't want to LSS for 1688 and then laze with 1688, but it also seems equally as weird that literally everything in the game defaults to 1688 and it wouldn't.

I've now tried I don't know how many times to get the TGP on the F16 to find a buddy laze via LSS, and I've had no luck. A10 and Harrier will find a buddy laze no issue very fast; but no matter what with the F16, no matter my range, I cannot get the LSS function to find a buddy laze. I'll admit I have not tried finding a JTAC laze, but I imagine it would have similar results. Last night alone I was looking within 0.1 degrees of a target, and the TGP after uncage and LSS search mode it still wouldn't find the target that I could see on the screen before going into LSS mode. Am I crazy, or am I somehow missing something. I feel like pressing the uncage button is a bit difficult to end up with "user error" if that's all there is to it.

Confirming tonight this bug still exists; that with ANY bombs attached the Dora can NOT fire rockets of any type.

I have a very early generation of the HD8 (it's I.. believe 5, maybe 6 years old now), and it runs this just fine assuming you have the google play store installed!

Nothing runs in background; all information exports via scripts.

I don't know if it's possible either, but I don't think I would be opposed to the buttons on the MFDs being... larger; larger than they should be, unless you have some weirdly massive tablet I think the visual accuracy is being more of a hindrance in this case. I also agree with the others though that some sort of feedback if we clicked beyond the green flash, like a click sound, would be HUGE. On the MFD thing from earlier; I feel like it would be nice even if it was just locked in the settings menu so we didn't have to choose it each time we open that page. ie most people will have their tablet set up the same way each time, so little risk of them using the tablet inverted from a previous time (probably...) I'm not sure what the general consensus would be, while I appreciate the accuracy visually of the MFDs, and obviously the other menus pretty much need to look accurate... The MFDs tiny clickspots means I really have to look away to make sure I'm clicking the right thing with some precision finger pointing. Still loving the app and what you're doing, obviously not trying to pressure you into anything I know I'm throwing quite a lot out lol, just throwing out my impressions thus far.

For starters however, the pairs seems to be broken; it always seems to shoot pairs. This thread was supposed to be able selective jett breaking rocket launching but at this point I'm not sure what I did last night to cause it. This track does not show that, other than me being an idiot and not putting external stores back into rockets. I'm unsure if this track will show this, but last night when I was trying to figure out what was causing this, I noticed it was shooting random amounts each launch, I don't know what's going on with that or if it's visible, but wanted to point out that I THINK there is an issue here as well. SO, changing this thread.... rocket quantity is for sure broken. The single rocket firing rate however still seems to be an issue. edit - CORRECTION: it's worth noting in the track file it may APPEAR that I was trying to change the ripples; this is NOT what I am referring to; (I didn't know track files would show me opening the kneeboard let alone TrackIR). I am aware you can only change this on the ground. But in track file you can see kneeboard shows firing rate of singles, but in the track, all pylons seem to shoot pairs or more. Hopefully however this gives enough information to show something somewhere is wrong, and at least with rocket firing count, but also possibly with selective jet switch F5 can't launch rockets.trk