ArcLite

For those willing to use a workaround, I’ve been doing this with 95%+ success: 1. Start in AUTO and designate the target as usual. 2. When the release timer hits 15-20 seconds, switch to CCIP 3. Immediately pickle, then lase. Allows you to maintain level flight and drop in the same manner as AUTO mode, just with an couple extra button pushes.

What’s the preferred technique then to make sure your bomb gets there before you 180 the pod, throttle back and S-turn?

So yours doesn’t stop tracking the vehicle when the pod 180s?

I was using “latching” as referring to using point track to lase a moving vehicle. Latching = When it “sticks” to the vehicle and tracks it.

Laser latching is working fine for me, but I have one question: when I’m latched onto a moving vehicle in point track mode, I lose my latch on it when the TGP flips 180 when going over top. Is this realistic behavior? As for the auto mode, yeah, not sure why some of us are having this problem and others aren’t. My release cue doesn’t drop until I’m literally like right over top of the target causing an overshoot.

This was in SP - hot start, that I tried it this morning. Obious: Looks like they changed it now so you just click it on and off. No need to hold it anymore.

No. Just tried them after updating and the release timer is still way too late.

One of my favorites so far:

Multiplayer in a server running a dynamic-type mission will bring you a whole new level of what amount of fun you can have in an hour.

Hey guys, Been a while since I’ve focused on the Hornet and what I’m trying to do is shore up my startup procedure for multiplayer. I know how to do the full, by the book start, but I am trying to whittle some of the unnecessary “fluff” out my checklist. One question I can’t seem to find an answer for is, will there be any adverse effects if I skip the FCS bit test? (the one where you hold the switch and press the button on the DDI) I know this is a silly thing to make a thread over, but I just want an answer from you smart guys before I get myself in trouble. Thanks for any replies.

I thought I double checked the CBs, but maybe not. Thanks, I’ll keep my eye on them. .

Guns not firing Maybe there is some kind of operator error going on, but since the last update my guns and cannons do not fire. Note, this is in multiplayer only. I did not check to see if the same problem exists in SP. Anyone else?

Yeah, the dark view out the front is about enough to make me pick the 109 every time instead (multiplayer), despite how much I like this plane otherwise.

I didn't see it last night either.

FlyingIron’s P-47N is great if you have XP11. No combat really, but a good option for familiarization and flying while we wait for the DCS version. *Apologies if this comment violates rule 1.15. Not sure where the line is drawn when suggesting something like this.

Okay, I just registered on Discord and downloaded the app. I’m in the BS server, so then I just join the axis or allies voice deal and start DCS (or visa-versa)? I set the push to talk in Discord as one of my HOTAS buttons, that’s all I need to do to talk in game then?

I’m in agreement with you. Just wanted to see if there was an “official” stance on it.

Quick server etiquette question: is it poor form to attack enemies on the opposing base, be they parked, taking off, landing, etc? I know it’s risky because the AAA seems to be pretty dangerous, but is it douchebaggy or who cares, have at it?

Good gravy. Well I finally gave multiplayer a go in the server tonight. A lot was learned very, other things a little more slow. After my first takeoff I spent about half an hour flying in the wrong direction - All the while checking the score tab to ensure there were in fact other people in the server. After I got myself straightened out and refueled I managed to find some enemy ground targets and got shot up - Then of course a Mustang appears, first enemy plane I’ve seen, and I get all excited and fly into the hillside. Next I take off again and can’t get my Anton’s gear up but head back into the mix anyway. Mustang guy must have been amused by this and rather than blowing the snot out of me from behind, buzzes past me and then flies around all but throwing up fly balls for me but I can’t hit him - Too busy stalling, which ended in me finding a fiery parking spot in the woods. Anyway, it was a fun first learning and I look forward to seeing you guys in the air. Cheers (and I’ll quit writing lengthy nonsense posts now :))

Thanks for the responses guys. I’ll give it a go soon and see ya out there. Is switching between allied or axis forces any time I join the server okay or do most people pick one side and always stick with it? I have the P-51D and the Fw 190A-8. And since I play in VR do I need that SRS program or something to talk to people?

Hey guys, I’ve never played multiplayer before and am thinking I’d like to. I fly numerous planes, but due to the nature of the dog fighting and my love of old warbirds, feel that WW2-era multiplayer would perhaps be the most fun. That said, hopefully it’s okay to ask these questions here even though they’re not exactly BS server related (but I’m interested in playing on your server for the aforementioned reasons): The biggest question I have is this: Will I get completely dominated playing in VR? As others who have gone VR can attest, there’s no going back. However the main issues and potential handicaps I see are both a result of visibility. I know spotting other aircraft is hard enough as it is, but it’s REALLY hard in VR. I mention this because in the videos I’ve watched from the server it looks like no type of labels are used. I imagine It’ll be very easy to get bounced often. Second is the difficulty in checking your six. Again in videos, I see guys on monitors using a key or whatever to quickly, easily, and clearly check directly behind them. This is harder (although more realistic) in VR and potentially a major disadvantage. Perhaps I’m looking too hard into it all and should just jump in and try. Thanks to anyone who read this far into my rambling and for any responses. -Chris

Just picked her up last night. Been watching plenty of YouTube and read through the flight manual this morning. I’m excited to get some hours in this beast this week and have some fun! So I’m currently reading “Fighter Group: The 352nd Blue Nosed Bastards of Bodney” and in it it’s mentioned that the 190 had a tendency, in a flat, high-G turn, to unexpectedly stall and violently wing-over in the opposite direction, resulting in a near unrecoverable spin. Just curious, before putting her through the paces myself, if this characteristic is simulated in game?

I appreciate you taking the time to respond, FragBum. I looked into the things you mentioned and kept diving down more forum rabbit holes and trying different things. That said, what ultimately fixed my problem was NOT OVERCLOCKING MY GPU. Some guy mentioned in one of the threads that his crashing stopped when he just ran his card at stock throttle. Interesting that DCS has some kind of bug going on here, being my OC is plenty stable (proven in other games and stress tests). Anyway, thanks again. Just wanted to post this in here in case it helps someone else out.

Also, here's my settings, if that makes a difference:

Hey guys, I'm relatively new to DCS and lately nearly every mission I fly the program is crashing. Might be before I even take off, might be when switching to weapon view, might be on my way back to land over open ocean...Doesn't seem to be associated with anything in particular. I've attached my crash and game logs (FYI, I only fly in VR). Seems to happen much more with the A-10C than with the F/A-18C. Here's some system info and what I've tried already: i9-9900K @ 5.0 1080ti 11GB 32GB RAM Oculus Rift Using VoiceAttack w/ latest version of Vaicom Pro A-10C Mods: Bummer's cockpit textures, Strobe brightness reduction -Updated to latest Nvidia driver -In Device Manager, un-ticked "allow computer to turn off this device" for all USB ports -In BIOS, changed DRAM Freq from 3200 back to AUTO -In Windows Defender, made sure firewall allowed DCS and DCS Updater full access -Tried running DCS "as administrator" I've been reading all the posts in here and am about out of ideas. Maybe try "repairing" DCS? Is there a way to do this without resetting all my game and control settings? Any help is appreciated. EDIT: Two missions in a row now DCS dumped when watching a CBU in weapon-to-target view right before/as it explodes. Mission before that, is was while sitting on the runway editing weapon profiles. Still not sure what to make of this... Log.txt Crash.txt