Mrgone

That's Okay, it fixed itself with this last update . . .

I waited a year for my pre-order G2 to arrive. Actually, I and a friend in 1982 were creating video-linked hardware and goggles however, the technology just was not there. I waited and waited for the technology to catch up. Most headsets were disappointing that I watched over the years. I took a chance before I died to finally invest in the G2. I have not been disappointed. There may be better unit but, not in my price range. Our original concept was for someone to wear the goggles, while another flew the airplane as hard and fast as possible, dodging any and every obstacle, while attempting to scare the crap out of they who were currently wearing the goggles. The first to remove them or scream were the loser!

To Eagle Dynamics, All Members, Contributors, Developers, Programmers, etc, I have been fighting a bone cancer now for four years and am finally in remission. DCS World and X-plane have been my only distraction. I am in debt to all of you. I own every module, and pretty much every Mod. In the beginning, and for almost 9 months following, the most torturous aspect to being sick was, having DCS installed and not even being able to play due to paralysis... A broken spine. I am sorry to state that I have made little effort since to remark or express a liking or, dislike to any and all of your works. Like YouTube, lets just remove the dislike button altogether (by the way, what the "F")? Your collective minds and contributions are all remarkable. I like all that apply to my installation. I have no criticisms or critiques. Well, maybe bigger booms! All patrons, at every level of experience are awesome. (Sappy Part), You have been my comrades, compadres, collaborators, colleagues and every other synonym one might use. All have been my unacknowledged friends and mentors. Differences aside, we come from all over the world with no other objectives in mind but share ideas and to enjoy this program which Eagle Dynamics has created for us. To all of you . . . Thank you for being there, for me, and for all other members you assist. Most of all, Thank you Eagle Dynamics. HAPPY NEW YEAR!

Anyone else crashing in the new missions at mission start? Everything else is fine . . . just curious?

C:\Users\%username\Saved Games\DCS\Config C:\Users\%username\Saved Games\DCS.openbeta\Config

My Mother once, while investigating a corporate merger at the USDOJ, looked up Hard Drive(images)on an unrestricted network . . . she walked away before the results completed. Her co-workers were rather amused upon her return. I told her older adults have no business on the Internet . . . She also called me on the WATS one day as, she was now transferring to another division . . . Her question: "How do I delete my X-Files?" The next question posed to her was "Eh-um . . . Where are these "X-Files" of which you speak? God Bless Mothers . . . Oh sorry . . . The X-files were pictures of Scully, Mulder and Aliens . . . She didn't want to be embarrassed should anyone discover her secret!

DCS 2.7 failed to start for me with all the vagueness as with other updates in the past and most of those start-failures described here. Since DCS relies on Steam, SteamVR, Windows Mixed Reality and Lord know what else Steam/Windows related and it fails during the initialization of one of these application layers when started manually or through any third-party like "Updater Utility" I did this. . . I added my Non-Steam version of DCS to Steam and let Steam handle startup . . . DCS starts every time.

Thanks Lange_666, I wasn't exactly posting an issue here, well, it is but, it isn't at the same time. Others are experiencing the same tearing I was. I know so for, they have posted this fact and some with no resolve. I was merely attempting to note to others that, installing the texture removed all tearing for me. This seemed a bit odd . . . for it is neither Steam, WMR, drivers, system configuration, USB, underrated video card, windows 10 or, the linear transition of IO across Jupiter. I flew for six additional hours after testing last night without a single glitch, tear, jitter or SteamVR crash. As for everything else, it looks great . . .

I've tweaking my G2 for three weeks now. I might add that this is my first VR experience. I ordered them when they first began taking orders for my up up-and-coming 60th birthday... Now, I'm 60 and I'm totally shrooming! Curious note, I've been plagued with two major annoyances and have been following the same path as everybody . . . trying everything? One, screen jitters, those white bands that look like lightning bolts or screen sync issues. Every time I move the mouse or, really just whatever pointing devise I've chosen, at the same time as one of these glitches, SteamVR crashes. Hard to tell for, Steam crashes because, that is what Steam does and diagnosis can be frustrating. I found that slow head movements kept the jitters to a minimum and I also slowed my mouse movements as well . . . this helps. Second is just all the juggling and configuring that comes with VR headsets with the hardware and software but mostly SteamVR. Tonight, while playing around with textures and after installing Ga-Bika Texture Pack, those jitters and SteamVR crashes stopped. Not convinced, I reverted back to Caucasus default and the jitters returned. I reinstalled the texture pack and they went away again. What ever the reason, I can duplicate at will and there is something unique about these if only for me? I have just flown for over two hours without a single crash. Perhaps someone who is experiencing the same issue might try installing Ga_Bika and see if this helps. If it does, we might be on to something. I'm looking at the differences between these files like, their sizes or bit-depth or, what ever can explain what I am experiencing. I've not gone into it yet in any depth. I just wanted to get this out there and see if it helps someone and perhaps get some feedback. I may find an answer if only for my own edification. I am running 2.5.6.58125 Open Beta. The textures are here: https://www.digitalcombatsimulator.com/en/files/3309252/ I used OvGME to install the textures which I downloaded here: http://www.476vfightergroup.com/downloads.php?do=file&id=505 Let me know?

Can't keep up with flight. Flaps are up Wheels are up Plane is trimmed Temps are good Canopy is closed However, adjacent AI P-47-30's pull ahead in level flight at about 10-15 knots greater speed. I can shallow dive to catch up but once leveled, they slowly pull away again?

File Version: 2.56.52437 Stable For some reason the Initial Briefing Screens fail to display at the start of a mission. They work however if I launch the same mission from the ME, but not from Instant Action menu. I performed a repair and let the updater do what it needed to do but, the problem persists. Not a biggie for, I can just unpause to start the mission. Just wondered if there is a configuration script with a switch to turn this back on? It is common to all modules, not specific to any aircraft or terrain. Resolved it rebuilding the \Saved Games\DCS\Config\Input folder. When done, the folder and file structures were identical? Through process of elimination, I found the issue, and what I do not understand, this folder only contains Joystick and Keyboard information. Just how can these files affect whether or not a dialog screen appears?

DCS 2.5.6.50793 Open Beta installed and is now asking to Authenticate the USS_Cole. [The following DLCs are not authorized and will be disabled: USS_Cole] Was this not the Mod "DDG-67 USS Cole release 2" https://www.digitalcombatsimulator.com/en/files/?CREATED_BY=markindel&set_filter=Y Why is DCS asking to Authenticate. The installed file is the same one according to its own installed Readme.txt

One other thing . . . deselect Syncronize Hotas controls with cockpit controls in the options panel. With it on, for me, the plane behaved crazy . . .

I have TARGET installed however, I only use it to turn On/Off the LEDs. Install it and then ignore it. It really does not seem to matter or, that is to say, it's played no role other than to provide the system drivers. Try opening "Game Controller" in the device properties in the Control Panel. Select "Settings" and select "Calibrate" for each of the devices. This is all I have ever done. . .

User Koekemoeroetoe asked is it recognized by the system? Is it?

The warthog works quite well with DCS for me. TARGET does not need to be employed though, it can if you'd like. The TARGET software is a little odd and at times a difficult to setup. As I said, DCS recognizes the warthog without doing anything. The biggest issue I encountered was this, when I open the Options page in DCS setup I often find Button from all three devices redundantly mapped to any or all three devices. Throttle buttons mapped to rudder pedals or, Joystick mapped to both Throttle and Rudders at the same time. Without realizing this at first, my HOTAS appears to be out of control. Here's what I did. 1) Plug it in and start DCS 2) Open the DCS program and go to the Options/Control and select the appropriate module and select the "SIM" version. 3) Make sure their are no duplicates in adjacent columns. 4) When satisfied, make sure to save the profile in the appropriate module folder. KA-50 - "\Users\user\Saved Games\DCS\Config\Input\Ka-50\joystick" or FA-18 - "\Users\user\Saved Games\DCS\Config\Input\FA-18C_hornet\joystick" Other than this, there really is nothing to do . . . Just watch for buttons mapped to other device. It will make the HOTAS go nuts

Neither the Stable or Beta releases seem to use the autoexec.cfg to set the Affinity Mask Or, there is another issue overwriting autoexec.cfg? Perhaps there's a new way to configure affinity without using Process Lasso or ALT-Tabing to task manager? Does DCS even use "affinity_mask =" anymore?

Well, I certainly see that this is a necessary step to perform from now on . . .

Thank you TOYKILLA. Found it. Mapped to button-24 of my Warthog. Since I hadn't mapped the switch, I didn't think to look at the configuration. As a matter of fact, I have found several instances of unrelated items being mapped to the axis controllers . . . Like thrust to my rudder. How this could happen is a bit of a mystery to me?

Beginning with the two updates, the FA-18's Refueling Probe is extended when I start . . . I have to keep moving the Pilot out of the way to reset the Probe switch. Is there a initial-settings where I can set it to "0, Off or False" whatever the requirement"?