Sn8ke_iis

I have mine set in TARGET with the press and hold option. You can also set the interval in pulse.

If you delete the page you might not get data for your carrier trap cards. I followed the advice of the developer and commented out the pertinent lines with a -- I still get trap data the 3rd page is just transparent. https://forums.eagle.ru/showthread.php?t=234838 Relevant post https://forums.eagle.ru/showpost.php?p=3839902&postcount=37

The F-14A/B was probably the last US fighter cockpit that was so analog. You have to remember these were flying and in service in '74 or '75, I can't remember off the top of my head. The F-15 that was developed a view years later still was all analog but with a better HUD. I was very surprised myself that the airspeed isn't displayed in the HUD in air/air or cruise mode. Over the course of the 70s a lot of improvements in cockpit design if you look at the F-14 to F-15 to F-16/18. Lots of labor saving and user friendly upgrades that cut down on the pilot's workload were a major priority for the engineers.

I was getting this same crash 100% of the time. I couldn't see the trap card on my first traps. C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F14\Cockpit\KNEEBOARD\pages\3.lua I added -- before every line of code in the file per the developer. I then added a modder's checklist into this path I created. C:\Users\*your user name here*\Saved Games\DCS.openbeta\Kneeboard\F-14B You have to create the "F-14B" folder. You may also have to create the kneeboard folder if you have not added any kneeboards before. The nomenclature conventions for the files are a little tricky. Works now :pilotfly: (the 3rd page will be transparent)

When I do the cold start at Nellis and use the shortcut it does the same thing to me. When it goes into INS alignment I don't touch anything. It counts slowly up into the 60's and 70's and finishes the start. Then you can touch switches or pull up a menu.

It's a form of variable geometry for the shape of the wings but may not be as intuitive as wing sweep nor is it automated. It is also not just for landing. It generally changes the lift, stall, AOA characteristics of the wing. Watch the indicator just above the landing gear handle when you lower flaps, raise flaps, and play with the DLC/maneuver flaps. In DLC mode you can see the small pair of spoilers move. I've flown just about every aircraft in DCS except helos. It's a new stick and rudder skill for me too. I'm accustomed to controlling glide and descent with power/throttle. It's absolutely amazing how maneuverable this big a fighter is. I put 10gs on her last night without ripping the wings off. There's no fly by wire governor for g's.

Default keybindings for all essential HOTAS functions ie trim, wing sweep, throttle detents, etc. I use TARGET with the Warthog set. Although the default joystick function bindings that shipped seemed very useful to most players, people like myself have default TARGET profiles with a standard layout and modifiers for views, zoom, kneeboard, time compression, TrackIR, and general consistency between aircraft. Although I'll probably be spending most of my free time in the F-14 for the next few months (it's really good guys), I spent the better part of my first evening with the aircraft just creating keybindings and fine tuning a profile specific to the F-14. Now I'm more than willing to share my TARGET profile of course, but that would also entail the added complication of adding in keyboard callbacks precisely the same as mine or having to copy over a configuration file. Better to have the same default key callbacks for everybody. TARGET can output joystick buttons, so I might make a profile emulating the default joystick buttons but I've always done it with keyboard callbacks. I'm not sure TARGET can emulate all the different joystick device buttons, it might be limited to the 32(?) in DirectX from the "combined device" that TARGET emulates. I attached the keyboard bindings that I came up with. They are mostly logical and do not conflict with the default layout. Keyboard.html.zip

Huh? No offense man but how old are you and how much real world business experience do you have? You sound like that one guy who thought he was going to revolutionize the HOTAS controller industry with 3D printers and put Thrustmaster out of business. So you're telling me, you think you would be able to provide tech support to a non tech savvy person who doesn't understand troubleshooting methodology and who bought a computer from you and/or prevent all those issues I just illustrated? Right... There are professional companies that provide similar services for pilot training and commercial aviation, that's a little bit out of the price range of most DCS players.

Whoa, whoa, if you have custom missions, skins, mods, etc. that's where they are kept. I have mods and work built up in that folder that would take weeks to replace. I keep it backed up on a separate share drive as well. Deleting FXO and metashaders folders are fine though.

When my wife saw that I was showing some visible frustration because I just wanted to fly and not trouble shoot - I have very limited leisure time lately - I remarked that even if I called Geeksquad or some tech service I don't think they would even be able to help much unless they are a DCS fan. Nvidia Inspector downloaded from the right link on Github...compatibility bits, power settings, drivers, ...Process Lasso, multiple background programs like TARGET, TrackIR, Geforce Experience, Discord, Teamspeak, Afterburner, etc...Registry edits for USB power settings...it never stops...And that's without even getting into BIOS and overclocking. Then, there's the calibration settings for my display that I would never have been able to learn myself except for rtings.com...if you want peak performance than you have to do a custom cooling loop...OSDs and fan tuning to keep up with temps... A lot of my issues stem from keeping my panel on a cart and watching movies, etc. If it was dedicated to DCS I would not have to disconnect USB and HDMI ports which causes issues with TARGET and the native Samsung settings like Game Mode. Definitely not plug and play, you have to manually change a few settings and the panel tries to autodetect the graphics card but doesn't know what it is. You want a trouble shooting nightmare? Try RGB Aurasync. Spent more time messing with that than building my custom loop and it still won't recognize the SLI bridge. I think it's the first time I've ever given up on a PC puzzle. $4000+ on my build and defeated by a a couple $ in LED lights and bad software :huh: Try explaining all that over a chat with a typical tech support person. :huh: I can only imagine some of the help tickets ED must deal with. I've been doing this for a while and like to solve puzzles. It's more than understandable that the typical Noob would get frustrated. If I didn't love the hobby and aviation so much I would probably end up playing Steam games with an Xbox controller. All I can say is it's worth it. Even with the extra cost of good peripherals. Especially DCS since the release of 2.5, don't fly anything else anymore. It's still less maintenance than a Cessna. There's a guy a couple hours from here that rents out his tandem Spitfire. It will cost you more than my rig for a couple hours of flight time. So it's :joystick: for me.

If you aren't interested in helping the developers troubleshoot and test why are you playing an Early Access module on OpenBeta? I play at 4096x2160p with almost everything maxed except the cinematic stuff. I turned down my mirror from 1024 everyframe to 1024 and lowered my MSAA setting from 4x to 2x. Not a big deal it's the first day.

C:\Users\*your user name here*\Saved Games\DCS.openbeta delete entire FXO and Metashaders2 folder. DCS will recreate the necessary files when you restart and load a mission. I have no idea how it works. I think it has something to do with shaders, textures, and other esoteric 3D graphic stuff loaded into your video memory. I could be completely wrong though. I do it every time I switch modules or maps. Seems to prevent a lot of problems.

Wow guys really? I've gotten a few frame rate drops as well with TrackIR. I turned down some of my settings compared to other modules. This is normal. She's not going to come out of the oven perfect on the first day. We might get a hotfix before the next update, but "2 weeks" definitely applies here.

No keyboard callbacks for trim inputs on the input layout. Only took a few seconds to add them in but might confuse new players.

Not a priority right now, but can you guys hire an artist for a proper wall paper? The photo is low resolution and looks like excrement on a 4k big screen. Not a good first impression for a new player.

Same issue here, but with Target. I rebooted, restarted TARGET, and DCS a few times. So far so good.

Delete your FXO and Metashaders folders.

Guys there is an "Update DCS World Open Beta" in your start folder. It only checks automatically every 24 hours or so. No command prompt necessary. Edit: I might have misread this but there is no need to force an update regardless, it's in the Eagle Dynamics folder of your start menu. Just keep it simple stupid (KISS) and download the .exe from the DCS website and let it do the work for you. That's the way Yeager would've done it. Having to use the command line might have been true at one time but ED updates their updater with new features.

You DO NOT need to use a command line, I have both builds installed. The Updater automatically copies over any redundant files you have currently installed from release to beta and vice versa. The OP could have done this in less time than it took to write his post. The Open Beta is there for a reason and ED has the reasons plastered all over their website when you buy their products. I don't see how they could make this any more clear without forcing you to acknowledge it every time you open DCS World on your computer. He'll probably come on here later today complaining about bugs and crashes in the wrong forum without including any useful information to diagnose the bug.

Had to LOL at this thread. The primary purpose of my build was DCS, with secondary general gaming, Blender, and Avid Media Composer. I'm not sure we can get this hobby to plug and play status. Just last weekend I lost a couple of hours of fun time to troubleshooting. A case of the dreaded stutters. Not really a micro-stutter, it was more stuttery than that, almost like a control input stutter when you don't clear out the axis profile in the DCS controls page and there is a conflict, more of a hitchy stutter-stutter than a micro-stutter. Went through all the usual steps, turn off OC, TARGET, TRACKIR...nope, still there. Spent another hour chasing Gremlins. I was worried about SLI. Could there be a new conflict with known good compatibility bits and the new OpenBeta build? Nope, turned off SLI, still there. Turns out it was a setting on my panel. Some Samsungs can do a neat interpolation trick up to 120Hz and it usually works very well. Smooths out TRACKIR panning. It was causing some weird artifacts in the latest build. When my wife wants to game, she picks up her PS4 controller, powers on, and starts playing. I love to tinker and build PCs. Sometimes, I just want everything to work like it's supposed to and just fly. That's usually when I have to troubleshoot a stutter or an unexplained FPS drop. It never stops...

"DID YOU ORDER THE vCODE RED?!"

Good one dude, you actually had me going for a minute. Oh wait, you're serious...good luck with that.

Used to play this: With this: Loved the reference to Jet. Brought back lots of fond memories. We've come a long way, keep up the great work!

:cheer3nc: Rejoice!!! You've made me very, very happy M3. I can't wait to shoot down some Yankee Air Pirates and then hop in the F-8 to return the favor. We really need a DCS: 'Nam map.

Concur for the key call backs for TARGET. I use custom profiles with modifiers. With the key call backs I can integrate the default setup into my usual layers and default view and a UFC. If they end up changing a few keybinds in an update I'm OK with that. It usually takes me awhile as well and is part of the study and familiarization process. If they already posted the documentation, why not the key callbacks?