tylero68

I run AMD Ryzen so my input on specific motherboard models would be useless, but you can’t go wrong with an MSI or ASUS board. Look up the boards using your required CPU socket on Newegg and check out the reviews. Building a computer is not difficult, but it does require a bit of research and learning. There and more than enough YouTube videos to get you where you need to be as long as you are willing to take the time. As far as DCS is concerned, I’m not sure where this computer programming thing comes from? I have numerous modules and fly VR. The extent of my troubles have been with having to uninstall and reinstall 2 modules due to corrupted controls, manipulating my graphics settings to get desired performance, and my VR headset software being a pain in the ass once or twice (rift-s). For the vast majority of things, it is indeed plug and play. But you may have to search the forums and troubleshoot from time to time. Well worth it for the experience, in my opinion.

I haven’t seen the block diagram but I was suspecting something to this extent. Where all other aircraft in DCS have a normal mechanical stick input with a 1:1 input to output to the flight controls (I stand to be corrected), with the Viper that is not the case. I would imagine that the pressure on the stick vs output to the flight controls in the viper IRL is not linear, and this is being reflected in the game. This is all just a guess, so don’t shred me too hard.

It is covered there, but it isn’t working for me either unless I’m missing something

Proportions look fine to me on my rift s. Everyone keep in mind that the f16 cockpit IS tiny. Clarity of the mfd text is not as good as on the hornet for me, but could be due to font type/size of the displays.

First, and primarily, I just want to say thanks for all the hard work on these training missions. They are absolutely fantastic, and every module should have them. You have set the bar, sir. As a side note, I was doing the CASE I training today and the TACAN seemed to be incorrect. The TACAN was not directing me to the ship. It was near the ship, but several miles off. Also, is T/OS not working correctly? Thanks!

Thank you!

As the title says..is this possible? Edit: Also, besides the angular location displayed on the TPOD screen, is there any situational awareness to know where the TPOD is pointing? Like in the A10 on TAD?

I believe it stays to one side until the tanks have been balanced out. At least, that's how it works the whole time I've flown it. Whether this is correct to actual A/C, I do not know.

Thanks! Did it during lunch. Downloaded about 12 updates and will give her a go when I get home.

Not quite sure what that is. Please, enlighten me.

I have had a vastly different experience. The flashes persist. The first night my headset refused to recognize that it was connected. And, there is some stuttering with head movement that I have never experienced before.

Every new plane i hop into is like flying for the firs time all over again. The A10 is leaps and bounds better in VR than on a flat screen when it comes to lay out and proportions. Its also yuge. And the mig21 is amazing. The sizing of everything really drives home how tiny it is in there. Was already my favorite module to fly around in, and it just got better. Been too terrified to hop into the 14. my pc might explode.

So. I just bought a Rift S today as I had never tried out VR in DCS before (I know, an expensive way to try something but I did some research and didn't think I would be disappointed.). And I have a few thoughts to share with those on the fence and a few questions for the seasoned vets. Background about how I have been playing before and about my rig if this provides any insight. R5 2600 OC'd to 4.1 ghz, 16gb 3200mhz RAM, EVGA FTW3 1080ti. 27" 1440p monitor, TrackIR. Initial Thoughts/Impressions: 1. Holy Sh!7 the scale. By far the largest impression made was just the scale of everything. The depth. The size of the world. The coziness of the cockpit. All of it. I initially spawned on the carrier and was blown away. Was not expecting that. (for additional laughs at my expense, I freely admit that during the Rift S demo/setup I was by myself giggling like a little girl in my living room). 2. Its going to take some getting used to. The ease of turning around and looking behind me in TrackIR is much different than ACTUALLY having to turn all the way during a dogfight. Got a little dizzy a few times. 3. I ran FRAPS during the second go round and I was averaging 41 FPS. with a max of 80 and a min of 30. I'm sure this will change as I break it in with more rigorous missions. 4. Did I mention the scale? A mig 21 flew by me in a dogfight and the lil' ol' mig looked massive. It was bad. ass. 5. I can fit my standard gaming headset over the headband, and I have a good sized noggin. For those wondering. I saw elsewhere in reviews this was an issue. Non-issue for me. Questions: 1. Speaking of the Mig fly-by, it was not smooth. Neither is when I do an F3 fly by. Is this due to the frame rate? settings? When i normally play one my flat screen the frame rate varies wildly from 40s on up, with an average of 60(i'd guess, I crank the settings up), and Ive never experienced that before. 2. The mouse following the head around and leaving a white dot. How do I get rid of this? i keep thinking I'm seeing one of those darned UFOs. 3. Importance of IPD settings in Oculus app. Big effects? I have no Ideal what my IPD is.. 4. Static reflection of the cockpit on the F18 glass. whas dis? 5. Multiplayer Performance: should I expect a huge hit in performance when I go online? 6. The text/gauges are easily legible in the 18. However, is it usual to have a relatively small focal point in a VR headset? or is it me? Please let me know if you have any questions. And for those that provide some answers, thanks ahead of time. TL; DR VR is a game changer.

2 questions about mission 13 on the campaign. 1. Laser code for the mission brief is 1688 but the JTAC calls back 1668. Which one is supposed to be used? 2. Any tips for getting the IP offset to be closer to the targets? Its been way off every time, even with the alignment at WP 2. I'm using 9.0 miles at 037 degrees. Delta_Alt = -761, per the briefing. Thanks.

To clarify, I have never experienced this with any other module.

I posted this here because I wasn’t sure if it needed to go here or in the bugs section. I have been flying the mirage a lot lately and have been making my way through the campaign. However, at certain times during my gameplay I drop frames to an unplayable rate. I generally get 90-130 frames depending on the situation, but in some instances I get dropped to the 10s and even below. This usually happens during landing when I activate APP and whenever I activate the radar gunsight. It has happened at other times randomly but these are pretty consistent. Mainly, I want to know if this is a mirage specific issue or if I need to dig deeper, or if there is a way to rectify it. System setup as follows... Ryzen 5 2600 OC 4.1 ghz, 1080ti, 16 gb ram, SSDs, running at 1440. If relevant, I can post my system setting. Thanks ahead of time.

Are the pedals still available?

Disregard. Seems to be working now. I went through and rebound that key first and it seemed to work, for whatever reason.

Good evening, Did a quick search and couldn't find anything so I figured I'd ask. Recently, I had issues with setting up my keybinds for the Harrier in the beta. I was getting the red line through the a couple of the sensor control binds. Went into the DCS.openbeta>config>input>av8bna folders and deleted applicable files. This fixed the red line issue. However, going through and rebinding my keys I am having an issue setting my throttle slider (incr-decr) as the nozzle angle. The software will detect it but once it binds all of my controls freeze up. This is a non-issue on the stable software version. FYI, I am binding directly with the controls through the in-game menu, not using the TM software. I also went an check my F/A 18 control that I have bound to the slider and it seems to be working find. Though, i didnt try and rebind it as I didnt want to open a can of worms. Any ideas?