DocSigma

After playing around with fuzing, I noticed that if you have inconsistent fuzing , etc.. set up respectively, the program x's out and the bombs do not come off the rails. For example, I set up a program to drop 4 mk20's in 2's with an interval of 50ft; I set the mode to ccip, the mfuz to on, and the efuz to vt, which caused an error - mfuz and efuz cant be enabled at the same time or maybe mk20's have no efuz so the program is x'd out. I turned efuz off, and left mfuz on which gave me a ht option to cycle dispersal,, which i set accordingly, and the bombs came off the rails as perscribed and detonated. Still fell way short, which I'm not sure why, but it fixed the bombs not falling off rails issue. In short. check your programs and make sure you're fenced in green across the board before depressing that pickle button.

Thanks Wags. Range and LOS was the issue. Appreciate it. Fantastic module! Eagerly awaiting additional systems and functionality to come online. Great job.

map the left and right throttle lifts to push past the afterburner detent.

I'm not sure if this is a bug, and I don't have a track, but picking up the station seems to be hit or miss. For example, on a mission where I stationed the carrier in eastern strait, I had no issues picking up the carrier; when I ran a mission stationing the carrier in the western straits, I was unable to pick up the carrier despite being right on withing 2 nm of the ship. It was no joy at variable altitudes as well. I checked the tacan station multiple times in the me to ensure the stennis was emitting, or should have been, but was still unable to pick it up. I don't know if this is a bug or a LOS issue.

Behind the stick, in the cockpit, beneath the center MFD, there are two switches. The ECM rotary and the chaff/fare dispenser toggle switch. Just set the dispenser toggle to the upward bypass position and dispense each counter measure individually. If you want to just use the cockpit to do this, the big red button left of the throttle just under the canopy is for dispensing counter measures.

I use the button 5 on the stick to lock.

I wouildn't call the Hornet's HOTAS less capable. Personally, I think it's just right. I have everything, with buttons to spare, on my TWH. It's minimal just enough to be quite functional in it's design. A sensor control crown hat and a weapon selector hat on the thumb plus HAT1 to trim. What more do you need? For my TDC - normally on the throttle - I use my DMS hat instead. The rest of the buttons are pretty obvious: trigger, wep release, nws. Every other button I'd need to engage is in the cockpit.

On whichever key you bound NWS to, just hold it to engage hi gain steering,and release it to disengage hi gain steering. You should see "NWS hi" displayed in the HUD.

+1 as well.

The work. Just assign each quadrant to their appropriate key bind, off/idle, respectively. The issue is that the key bind does not resister on the up pull of the stick, but rather on the back pull, so it's sort of reversed. just do your startup with the quadrants out of the idle position, and when you want to move from off to idle in the cockpit, just physically put the quadrants back to idle at 25 or > rpm and you should be fine. Its a little weird, but it's what ive been doing.

The op is correct. The keystroke is pressed in the idle to off position and not the off to idle transition as it does in the A10. Sent from my SM-G965U using Tapatalk

Tornado would be great, but I do think non NATO aircraft need some love as well. Anything is a privilege, but I'd love to see an SU-24.

@Kayos Those frames seem pretty good for a 970. What are the rest of your system specs like? I'm asking because I'm currently building a new system and plan on using my 970 until the new generations cards hit the market. Thanks.

Just DCS 2.5, and some sort of HOTAS.

I thought z390 was supposed to drop prior to the 9700k in a few months? I was thinking wait the few monts for the z390 - isn't it essentially what intel had planned but unfinished for the coffee lake release? - and pair it with an 8700K then I'll have the option once the 8 core i7 9700k drops to swap.

I said I was waiting for Coffee Lake to drop before taking the plunge, and now that it has matured a bit, it's these two builds that I'm thinking about going with. PCPartPicker part list / Price breakdown by merchant CPU: Intel - Core i7-8700K 3.7GHz 6-Core Processor ($349.99 @ Newegg) CPU Cooler: Corsair - H115i PRO 55.4 CFM Liquid CPU Cooler ($139.99 @ Newegg) Motherboard: Gigabyte - Z370 AORUS Gaming 5 (rev. 1.0) ATX LGA1151 Motherboard ($191.00 @ Newegg) Memory: G.Skill - Ripjaws V Series 32GB (2 x 16GB) DDR4-3200 Memory ($356.99 @ Newegg) Storage: Samsung - 960 EVO 250GB M.2-2280 Solid State Drive ($119.95 @ Newegg) Storage: Samsung - 860 Evo 1TB 2.5" Solid State Drive ($279.99 @ Newegg) Case: NZXT - S340 Elite (Black) ATX Mid Tower Case ($59.99 @ Newegg) Monitor: Asus - PG279Q ROG Swift 27.0" 2560x1440 165Hz Monitor ($741.59 @ Newegg) Total: $2239.49 Prices include shipping, taxes, and discounts when available Generated by PCPartPicker 2018-05-01 12:23 EDT-0400 and PCPartPicker part list / Price breakdown by merchant CPU: AMD - Ryzen 7 2700X 3.7GHz 8-Core Processor ($329.99 @ Newegg) CPU Cooler: Corsair - H115i PRO 55.4 CFM Liquid CPU Cooler ($139.99 @ Newegg) Motherboard: Gigabyte - X470 AORUS GAMING 5 WIFI ATX AM4 Motherboard ($182.14 @ Newegg) Memory: G.Skill - Ripjaws V Series 32GB (2 x 16GB) DDR4-3200 Memory ($356.99 @ Newegg) Storage: Samsung - 960 EVO 250GB M.2-2280 Solid State Drive ($119.95 @ Newegg) Storage: Samsung - 860 Evo 1TB 2.5" Solid State Drive ($279.99 @ Newegg) Case: NZXT - S340 Elite (Black) ATX Mid Tower Case ($59.99 @ Newegg) Monitor: Asus - PG279Q ROG Swift 27.0" 2560x1440 165Hz Monitor ($741.59 @ Newegg) Total: $2210.63 Prices include shipping, taxes, and discounts when available Generated by PCPartPicker 2018-05-01 12:25 EDT-0400 I'm leaning more towards the Intel system for these reasons. 1: Two extra cores for the money on 12nm is nice, but being realistic with myself, I'm not running a server or regularly utilizing applications that require such a large number of cores. Mostly a gaming rig, and IPC's matter, especially in games that utilize a minimal number of cores, which most do. 2: A higher overclock ceiling than the 2700X. Having a decent VR platform is important, and while it's not just CPU dependent, raw MHZ seem to matter. Reasons why i'm leaning towards the Ryzen platform: 1: More for the $30 or so lesser dollars: more cores on 12nm, bigger cache, more lanes. 2: 2k to 4k gaming: the 8700k outperforms the 2700x at lower resolutions, but I plan on going no lower than 1440p and the 2700x really closes the gap at higher resolutions. The reasons why you don't see a vid card are because it's just too late in the cycle to buy a 1080ti worth over half the price of the computer - I think the new cards using HBM2 will be cheaper than the inflated GDDR5 cards now due to higher supply. I plan on using my current 970 and it's 4gb of vram until the new cards drop. Furthermore, I just got a brand new evga g850 psu, which ill use. My current monitor fizzled out, which is why you see the pricey monitor - Gsync is too important so why not get the IPS Asus ROC - since I will not be worrying about VR until the new vid cards drop anyways a decent monitor is important. I also have my current WD 7200rpm 1TB drive I may format and throw in there for additional storage. Another concern of mine is the z370 chipset. Do I wait till Intel releases their z390 boards which should support Ice Lake/i9 and Coffee Lake? I know I'm taking a hit on RAM prices, and can lessen the sting by just getting 16gb, but why not eliminate all uncertainties with regards to RAM and just get 32gb up front. I chose the Aorus board because I run a Gigabyte x58 now that's been good to me so, why not; i'm not opposed to going with Asus if there is some advantage over the Aorus board. Also, they are both WiFi boards cause, unfortunately, it's either snake a tripwire of a cable all the way to my router or just go wireless without the need for throwing an expansion card in the case that disrupts airflow and generates heat - I still may cause I have a 400Mbs pipe that begs to be siphoned from something other than my streaming services and my Android phone. Therefore: 1: 8700K or 2700X? 2: Mainly a gaming rig at =or> than 1440p and eventual plunge into VR when the new vid. cards are released between end of summer and maybe December. 3: Any reason other than RAM prices are high to wait on building now, considering I'm still on an x58 chipset thats 8 generations old running an i7-920 oc'd to 3.8ghz and 12gb of DDR3 1600? I'll always be waiting for the next best thing, but the reality of it is that there will always be something else just around the corner. If I go 2700X I will eventually oc it to 4.2 and if I go with the 8700K, I will oc it to at least 4.9-5ghz, if my cooling is good enough. Really sorry for the long post, but thanks and appreciation to anybody who steers me in a direction. p.s. im not set on buying everything from newegg. I'll buy at the places with the best prices, so the final price will be a bit lower.

I don't think mining is exclusively to blame for the price spike in nvidia GPU's. AMD has to compete performance wise to nvidia chips, which they haven't done in a while. Hopefully Vega will be price/performance competitive in the high end enthusiast graphics market with the release of Vega to maybe drive the price of some of the high end nvidia cards down a bit.

Maybe a bit more power. 500W seems a little low to me for that system. Also, do you need the sound card? May be able to cut a few dollars by using the mobo's onboard audio. Other than that, with the included SSD, that is a really nice rig, especially if it's just for DCS. You can go the Ryzen avenue. Ryzen chips may not have the single core performance I7's have, but they are comparatively cheaper for more cores/threads with a very minimal performance hit in certain gaming applications. With the money saved on a Ryzen system, you could add the savings to upgrading from the 1080 to the 1080ti, which will pay huge dividends if you're gaming at 1440p.

I remember a thread a while back expressing some serious frustration regarding DCS with AMD GPU's. Maybe things will change when AMD releases Vega sometime in the near future.

My system is rather old, and the ram frequency is tied to the cpu bus, so in order to get my sticks running close to the listed specs ( ddr3 1600) I either have to enable the X.M.P profile or adjust the timings and frequency manually in my bios. You're system is brand new and a beast I might add, but I'd try just enabling the X.M.P profile in your bios and that should get your sticks recognized at their listed frequency and timings. Before you do that though, make sure your board supports your sticks - brand,frequency, timings, voltages.

I'm very tempted to jump on this deal. I'm still running an i7-920 system, which I've oc'd to 4ghz - its currently running at 3.7 though. I've got a 970 in my rig with 12gb's of mem., but I don't have an SSD - a single 7200rpm hd - and i'm lacking usb 3.0 inputs. I suppose I can pop in a ssd and install dcs on it and throw in a usb 3.0 pci-e controller for the ports. Just not sure if those upgrades are worth it at this point or are functionally feasible. I may just buy it and just keep it in it's box, collecting dust until I take the plunge and make the long overdue new system build. At the moment i'm torn over which platform to take the plunge with and which platform will yield the most longevity: 1151, 2066, AM4.

Same thing was happening to me. Random reboots, especially under load, are most likely due to a psu issue. Each time I would put my GPU under load my computer would reboot. DCS puts the gpu under load. What I did was had my daughter play a simple steam game and monitored the power draw using gpuz. All was good as my gpu stepped up it's power draw and it's load until the vid card had to up it's load which then resulted in the reboot. Borrow a psu to confirm it's the pus, or just buy a new one. I got a new psu and that remedied my rebooting issues.

+1

There is just too little information as to why the pilot decided to use a MRM instead of another 9X to shoot down the Su-22 - initial load-out, did the only remaining SRM misfire, and probably a plethora of additional reasons.