Davee

I use Target Script. But . . . . if you use straight Target you can find the script file here: Just click on "View Script" and edit that document when it pops up. Hope it works for you.

This!

Hi Alamo, Similar problems and went through my systems and I may have found a solution. A least it has worked now several times in a row. First I did the usual things about ensuring recognition and ensuring no "sleep" mode for the USB invoked. Made sure it was connected to USB 2.0, and ensured "Legacy" mode was on in the Bios. The fix was - to remark out some of the TM headings in the script file as follows: include "target.tmh" int main() { //Configure(&Joystick, MODE_EXCLUDED); //Configure(&HCougar, MODE_EXCLUDED); //Configure(&T16000, MODE_EXCLUDED); //Configure(&LMFD, MODE_EXCLUDED); //Configure(&RMFD, MODE_EXCLUDED); if(Init(&EventHandle)) return 1; SetKBRate(50, 50); SetKBLayout(KB_ENG); SetShiftButton(&Joystick, S1, &Throttle, BSF, BSB, 0); This change also stopped the delay in loading and also worked from rebooting the PC. Keeping my fingers crossed. Cheers

Thanks IvanK, But just for a little fun, it sounds like a ballet maneuvre. :) Cheers, Cats . . .

Easy guys - WAGS has been recovering from what sounds like a pretty bad cold/flu - bug!

Interesting about the cockpit scale being correct if you set the in-game ipd to one's actual ipd. I'm lucky in that I wear eye-glasses and my prescription shows it as exactly 65mm. I'll start there and make small adjustments along with the others of which I am very grateful.

SE, Thanks for the details on PD/MSAA. I wondered if MSAA could be run with an HMD.

I checked out 1 - 3 and they are as you show. I need to plug the HMD in and see 4 - 6 settings. Thanks again.

Thanks backspace340, Working on this today. My prescription is 65mm and that is set. So now to check out the in game IPD setting to see what it does to the in game scale. Right now it looks too far away and fuzzy. I did notice that when I physically moved forward things became clearer so I'm wondering if a closer scale will begin to resolve the clarity. Gonna' be a fun day guys. I really don't want to return this. Also, I have a small bucket on my lap. ;) :)

Hi Svsmokey, I Think that the PD might be the issue. I'm going to try 1.5 and see what happens. Most seem to recommend 1.0. Also, I read Skatezilla's post on what the difference means between the physical wheel that moves the lenses and the ingame Force IPD distance that will change the FOV. I need to look into that - it's currently set to 100. I now have the following: pd ingame 1.0 going to try 1.5 steam ss 200% rendertarget 2.0 no ingame aa steam wmr beta ASUS gtx1080 odyssey 1 hmd wmr very-high (beta) in windows control panel Thanks for your help. Cats . . . ps: I have to say though, that even not fully clear is blows you away looking at 3D. I almost puked rolling and looking out the side of the cockpit. (Inner ear balance thingy.)

Hi Walleye62, Thanks for the feedback. I'm using the beta version and following your info checked that "renderTargetScale": is set to 2.0 (looks like that is a fix already set) I have the resolution set to 200. So the one thing that I did not have set correctly is the PD. That is the software PD not the physical dial in the HMD. Thanks for the tips. I'll try it out tomorrow. Cheers

Hi Guys, I just received my Odyssey + and followed the instructions I could find in these threads. I tried everything I could but the image is fuzzy all over. The cockpit panels are fuzzy and all switches. I thought only the text would be an issue but so far no fix. My system I7 ASUS Rogue HeroIX overclocked, vid card 1080 oclocked. Shimmering I can understand and the text not fully clear but I'm troubled by the fuzzy panels. I'm on the verge of returning but I need to make sure I checked all the issues. Cheers

Link?

Thanks for your perspective! As an older guy and simming since 1985 and upgrading every few years to maintain systems currency - I just sprung for the SO+ and hope it gives me a similar impression as yours. It is to arrive March 12 or so. I will be reading through these threads to determine just exactly what I will need to install to make it work the best it can. So much good info here but I will have to search through it bit by bit. One of my issues is visual and I require eye-glasses. I know there are optical solutions available but I'm a bit anxious to determine if there will be issues. Cheers

Troll?

+1

+1 Always wondered if this is final or WIP.

OK, thanks. Yes, I'v experienced the sync thingy so I only use the back A/G switch and my VKB joystick to switch back to NAV when finished with AA which I select on the VKB Joystick. Mixed sytems. :) Thanks again.

Hi Guys, I'm taking a stab at using ED's .lua coding for my TM Throttle instead of using Target. The one control I am not having sucess is the boatswitch right side of the throttle. I would like to make it work like I do in Target if possible. Forward Press is A/A mode then move back to middle (release) returns to NAV mode. I do this by having the switch press #1 going forward and on Release to the middle Pressing #1 again. I also have the Back Press set for A/G and Release to middle again is NAV mode. I do this in Target by having the Back Press as #2 and Release is #2 again. Just two different Press and Release commands which are easy to do in Target. This may not be possible in .lua files so any help much appreciated. Thanks.

Reduce world sounds in the slider.

Same issue here. Today I just downloaded the latest drivers and reloaded Target. Also, ran a systems program to clear out any left over bits in the registry. It seemed to work great at first until I loaded the throttle without the combined setup. It showed up just fine in DCS but, when I went to load the conbined setup after shutting down DCS, it showed both setups in DCS again. You can tell when it's struggling on loading the stick when there is a long delay. However, on subsequent DCS boots with combined setup DCS did show only the combined setup. So, more testing. Oh, yes, I deleted all the configs in the Save Games folder and then loaded my backup files through DCS. I only had to play with the axes controls a bit.

That doesn't work for me and others. Seems 50/50 between reports. I wonder what makes one work and the other not between systems.

I stand corrected! :)

You've quoted the same forum. :)

Similar . . . I've been using Target Script - assigning my slew with a press/release of the TDC included in the script assigning the slew to the china hat.