tekrc

I too would love cartridge starting. just an awesome sound

did a few more flights and noticed something. the error in where shkval points does seem to be related to the elevation in my case. syria elevation is pretty up there so its really far off but the marker on abris is in the right place and I can manually slew the line over to it and find the target. additionally the shkval IS tracking a point not just following the nose in turns etc but that point is way underground. so I thought my issue here is elevation related as well. this changed on the Caucasus map. using the small disused airstrip with targets for a reference as this is close to sea level, I did the same thing. the point no longer slewed the shkval to an underground spot but went off horizontally and no longer matched up with the abris position. this is where I first suspected drift but the behavior is the same once it slews over so could be a mix of altitude and drift for the actual cause? its just horizontally off in this one though and looks like more like drift compared to what we saw on syria so it could be something else entirely. same mission settings as the syria track. included track and mission. (side note but you have the mission if you have the track. just change file extension. that way you can try the syria one too) nav error CS.trk target practice beta new stk.miz

I can do that yeah give me a few. this happens in a few different missions across different maps so Ill do it in another for cross comparing and send that one. reading through though I never tried the included instant action missions so Ill see what it does there as well and report back. the weird thing is I never pressed a mode key on the right side of the PVI. I'll go slower around the pvi this time and see if that makes a difference

as far as I understand if the DISS is done you start getting the speed readout on the hud as a number? in which case mine is done before I start up. as soon as I lift I have mine and thats doing the fast alignment. if thats not it im not sure where I would check it but if it is I dont think it takes that long

was just a fast align so it isnt wrong. but the result wasnt changing doing a norm or precise align and was having a bunch of issues trying to get heading set up correctly and its not well explained. every tutorial I saw seems say to use a different reference for twhat to put in the dial and im not sure what im supposed to use. also this is with "No alignment and fixtaking needed" in the ME so it shouldnt be needed regardless

far as I can tell (my best guess. not claiming fact here), its fine in those examples because youre doing it still on and around the pad just after scenario start. but after flying around for not even 10 mins the ins drift has gotten so bad coordinate entry is useless and as a result, so is datalink. still have to rely on marks saved by yourself on the dl panel and cant use a nav tgt or target sent to you past referencing the abris. even saving your own they dont stay good for very long as drift error drags them out pretty quickly. in my case if I do start and takeoff or just scenario start hot, fly out to a target area (in this case target is a building at an airfield 10km away) and then try to pull up a target I had saved as a nav tgt. it looks fine on the abris but shkval is way off when it is uncaged (always tries to slew down almost to where the heli is it feels like). NOTE: if I grab the nav tgt position from the shkval it works fine. I believe this is because of referencing own navigation instead of from coordinate but I didnt do a position comparison here finding the target manually with the shkval, storing it, recalling it works fine just nothing coming from another aircraft or stored through pvi coordinate entry goes to the right place for me. makes me think its related to drift error because its only really noticed when using references from outside your own nav system after being in transit for a bit NAV TGT track.trk

If I try to launch with vr (standalone using the shortcut with modifier to force enable vr), DCS will launch as it would if it was in vr. it has the skewed aspect and the offset view like it is trying to use my headset position. but it is not displayed in my headset nor does it react to my headset moving (valve index). Tried installing steam version and dcs not recognizing the headset there either. headset enabled in settings but only launches in 2d even with vr already running. normal DCS standalone version (not mt) DOES read my headset normally and vr functions fine

So BS1 didnt actually have training MISSIONS it had a set of videos. Those videos no longer exist as they have been replaced by the BS2 ones. So the ability to download the bs1 videos is gone. However youtube being what it is you can likely find everything you need either using the BS2 video guides or finding a BS1 tutorial upload from back then if you really want to dig for the legacy stuff. BS2 should be nearly the same with minor differences and more than enough to work from.

glad I could help out!

As many seem to have trouble with this, Imade a video here showing the usual problem and 2 methods to get LOAL to work. specifics are in the description. it works for me every time. this should be enough to get people going or at least enough to work with so others can make a proper tutorial and explain things better than I generally can.

its off topic, but here, I made a video demonstrating this does work. follow along in the description for what I'm doing https://www.youtube.com/watch?v=P7V-y-Bj4pk

it doesnt have problems it works like it should. just need to understand how george is set up if you store the point he doesnt use it. george only uses his tads as acq. if you want to use a point you entered, you have to shoot then tell him to switch to hellfires in lobl so he can start lasing or have a buddy do it. if you want george to lase his own shot you have to be far enough away, have george spot the target, be low if not using direct. command shoot, then pop up so he has line of sight. if using direct you just have to bring your nose down toward the target more than you would in lobl. he will auto lase when missile is part way to the target

Ive done this too. for anything other than dir fire you have to be pretty far away. but it does work. process is the same for all trajectories. get george to mark the target (select it in the menu) when he stores it and you get the tiny box. steer towards the target area and command fire (need to hold it sometimes) and he should shoot the missile and automatically start lasing. if not back off past 5km and try again. if you have a jtac or buddy doing the lasing, select hellfire manually and set a target point at the target area yourself as your acquisition source (VERY IMPORTANT if you dont set a good acq source the missile wont come down when its supposed to and can overshoot the target area)

my in cockpit seat position is too high. I have to scrunch down or slide my chair back to get proper alignment here. even on 2d mode with TIR. really wish they would just fix the seat positions for all aircraft so that center was actually where I should be sitting and looking from my eyes and not staring down at a fire handle with the seated position too far forward and/or high for good operation (see a10 for a good example of way too far forward). seat position mismatching has been an issue for a while and its a bit irritating with newer modules having to try and boresight from a bad position. my back and neck would appreciate better default positions and hud scaling.

ok so in short, george is lying to my face. not cool, george.