Slug72

Srsly? If it's electronic then failures are inevitable. Nothing is perfect. Personally I've had two NVidia failures... an EVGA 8800GT that was 2mths outside warranty when it started artifacting even in 2D (a dry solder issue mitigated by regular "roasting" in the oven until I could afford a replacement), and a Zotac 2080Ti Amp! that decided to stop doing 3D after 3mths (replaced under warranty by the retailer with my current GPU). The bottom line is.... nothing is infallible. ;)

Yup, understood. DCS is using F:/Users/<username>/Saved Games, as are all my other games, as that's the correct Windows location. The "Saved Games" path in DCS Updater for my OB build is defined as F:/Users/<username>/Saved Games. However the Updater created its folder in C:/Users/<username>/Saved Games. As noted it doesn't affect functionality so I'll ignore it.

This seemed strangely familiar... yup, he had a similar experience here with BF5 a few months ago. Since the common factor is an otherwise-stable system crashing an FPS game after 12+hrs unattended use, the obvious solution would appear to be... don't leave FPS games running for 12+hrs unattended. ;)

When I built my current system I moved <Saved Games> to a discrete SSD (F: ), and configured that within DCS Updater Utility when I installed it. The app however uses my system volume (C: ) for its own <Saved Games> folder... is this expected behaviour? To clarify.... the program functions perfectly as-is. I just need reassurance that I haven't screwed up. ;)

What I did was just get a feel for VR using the stock settings, noting the fps and frametimes as I tooled around with the graphics settings to find what worked and what didn't in terms of detail. I then experimented with both "auto" and "motionvector", finally settling on the latter with SteamVR SS @ 150%. This gives me a very fluid experience with my chosen level of detail. N.B. if (like me) you have a discrete drive for Steam installations, then the default.vrsettings file will be found in "<drive>\Steam\steamapps\common\MixedRealityVRDriver\resources\settings". ;)

Have you tried a repair? (Start Menu/Eagle Dynamics/Repair...) edit... OB here, and 'Axis Assign' definitely works.

As above, DCS will only appear in the list when it's actually running in VR.

For the F-16C MFDs, try this mod. Note: if used in 2D then your EHSI will be rendered effectively unreadable.

Post-It Notes are a godsend! I hand-on-heart have one stuck to my monitor bezel with "VR?" in block caps, to remind me to actually connect the bloomin' HMD before trying to fly. :lol: VR is an addictive money pit though; one week in and I'm already considering PointCNTL and an FSSBR3 base to further enhance the realism. I need help. :helpsmilie:

Apologies... it previewed okay before I posted. :( It does indeed, so I use OvGME to disable it when I go back to 2D.

I've had the "device not recognised" error twice in the week I've had my Reverb, but reconnecting it after boot appears to have cured the issue. IOW I unplug the HMD from the umbilical after each VR session, and do not reconnect until the system has rebooted to desktop. I'm running it from a USB3.1 Gen2 port. I'm using SteamVR SS 150% setting and it makes the F-16C cockpit switchology noticeably clearer, so thanks for the tip. I also use this mod to increase MFD visibility. Thanks @Holychocmilk.

There's an entire sub-forum here. There are also a couple of Iraqi/Syrian MiG-29A liveries in User Files.

Then choose an F-15C if you need more spamramms. The Viper is not an air-superiority fighter. They can approach that if they're deployed correctly i.e. launched closer to RNE than RMax. That however requires (a) patience and (b) tactics. The "sensible" amount determined by the USAF for the F-16C Block 50 was six i.e. STA1/2/3/7/8/9. Each on single-rail launchers. That fancy YT video? Means squat unless it's been flight-tested. Sure it looks cool but the drag ratio will cripple performance... I'm guessing that's a CATIII loadout? Plus it's not an F-16C Block 50 so wtf do we even care?

Phase 1 Early Access: BDU-33, BDU-50LD/HD, Mk-82LDGP, Mk-82AIR, Mk-84LDGP, CBU-87 CEM, and CBU-97 SFW unguided bombs 2.75” rockets LAU-68 and LAU-131 AIM-9L/M/P/X Sidewinder AIM-120B/C AMRAAM M61A1 20mm cannon Phase 2 Product Sustainment: AGM-65D/G/H/K Maverick AGM-88C HARM GBU-10, GBU-12, GBU-24A/B laser-guided bombs BRU-57/A Smart Rack CBU-103 CEM and CBU-105 SFW Inertially Aided Munitions (IAM) GBU-31/A and GBU-38/B JDAM AGM-154A and AGM-154B JSOW ALE-50 towed decoy (source here) At least one in the Phase 2 list isn't accurate for "our" Viper but was included by ED due to pressure from the community.

Nothing in \Saved Games\DCS is deleted by Update/Repair/Clean operations. ;)

ISTR a post some time ago that indicated that ED intends including liveries for all period-correct USAF units, with a strong hint that they'll also include some foreign Block 50 operators. We'll have to rely on the many talented community artists to provide for our non-Block 50 needs. Given the current selection available in the User Files section, even at this stage of development, I'd say we have little to worry about. ;)

Both (plus much more) are available here courtesy of the 476VFG.

The individual liveries should be extracted to ...\Saved Games\DCS.openbeta\Liveries\F-16C_50. They will then be available for selection in the "Loadout" tab in the ME.

As Joe Bill so eloquently put it, "the idea is not to be Joe Cool by reaching over, engaging the MPO switch, and then trying to make the stabilator actuator white-hot by wildly pumping the stick" The F-16 doesn't take kindly to being handled roughly... she prefers a gentler hand. You have to get 'in phase' with the pitch oscillations e.g. pull until the nose begins to fall, then push until it starts to rise, and repeat the cycle. Once in phase, you should recover in 2 or 3 cycles i.e the "fluttering leaf" effect will stop and the nose will remain where commanded. Then it's throttle as required to reach 200KIAS, MPO=Norm, and business as usual. ;)

What will be your primary air frame? I currently have the TMWH on MonsterTech deskmounts, but am contemplating converting the stick to a chair mount as I'm concentrating on the F-16C atm. The chair mount is simply better-suited to the F-16C. MonsterTech have you covered. :) Check out the MonsterTech site.... they have accurate mounting templates for all popular chair-mount options. If you're building your own mounts these can guide you. FYI DXRocker chairs use the Form1 3-bolt pattern... tested and confirmed.

Maybe, but most of us civvies don't have access to current F-16C flight manuals due to OPSEC and have to go by what ED say in the in-game manual e.g So, does that mean when the 370Gal wing bags are empty, CAT1 is safe? I'm sure I'm not the only person transitioning from another F-16 sim to DCS who had to drop wing tanks before switching to CAT1 to avoid damage. I'm not arguing, just pointing out that most of the DCS player base don't have access to the same info that those privileged to serve do. I very much appreciate your insight, but you have an advantage. :)

My file path is as follows: <volume>:\Users\<username>\Saved Games\DCS.openbeta\Liveries\F-16C_50 However, in addition to the add-on livery folders I also have a "default" one containing only "description.lua" file. I think this originated with the 22FS skin from @Don Rudi that is my default (personal reasons... 22/23FS were regular visitors to LFA14 back in the day.) I can freely change between the default 55FS, the 22FS, the RNIAF 323Sq "Diana" and the USANG 157FS "Swamp Fox" skins

Because trimming the jet for an asymmetric loadout e.g. after dropping a single GBU-12 is almost impossible. The lightest "tap" of the trim hat results in over-compensation, It's not like this in the F/A-18C, nor in other F-16 sims that I flew in a previous life. Erm... nope. I want realistic behavior in SIM mode. If the current trim response is confirmed as accurate by ED and their F-16C SMEs then I'll accept that, but until then it's "broken" imho.

Which CMDS program are you using? The default programs are, to be polite, gash.:P Until we can program via DED, I suggest manual editing of the "...\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\CMDS\device\CMDS_ALE47.lua.

The Block 50 is still in active service with the USAF/ANG. However ED have chosen to model a USAF post-CCIP Block 50 from 2007 for reasons of accuracy due to available data. An F-16V Block 70/72 is available to order from LM, but (a) so far it's only been ordered by export customers and (b) performance details of the AN/APG-83 AESA radar and upgraded MMC will be highly classified.