JoeyJoJoJunior

Thrustmaster has spare parts for sale. I got some replacement hats for the Cougar stick recently. Cost a pretty penny, though: 6 euro for each part, and 23 euro shipping.

I have most of the non-trainer jet modules now, and your manual is the best of the bunch. Thanks for your excellent work. :thumbup:

See here: https://forums.oculusvr.com/community/discussion/78729/update-on-rift-s-static-white-flashing-new-ptc-build-7-25

It depends on what the issue is. Is it not sharp enough? Higher resolution. Is it too small? Bigger monitor (while holding resolution constant of course...if you move up to 27" 1440p, you'll gain no improvement in the too small department, maybe even worse).

I wouldn't say it's overrated. I get at least a couple every play session since launch. I know I'm not the only one. It's a minor annoyance, but still kind of unacceptable so long after launch from a company with deep pockets like FB.

It's a sim, dude. The idea is to be as faithful to the real thing as possible. Unless your suggestions are in the real plane, they won't happen by design.

Odyssey uses an OLED panel with a pentile layout, which has two green subpixels for every blue/red subpixel. This means a pentile screen has 1/3rd as many subpixels. Whereas the LCD panel in the S uses an RGB stripe layout, with an equal number of red/green/blue subpixels, all the same size. This means an RGB stripe panel can look much sharper than an equivalent resolution, or even higher resolution, OLED pentile panel, especially when looking at it up close like we do in VR. This is one reason most headsets are moving to LCD. Another is RGB stripe panels tend to be denser in their subpixel arrangement, resulting in less screen door effect. Some pics to demonstrate: Left RGB Stripe / Right Pentile

Ok, I got it out. WD-40 helped a bit. So did flipping it over and pressing on the base to apply a bit more pressure to the cam posts. I saw this technique used in the video for the Mk. III and seemed to work here as well. After putting wd-40 on the cam bolt and on the outside of the bearing, I put it back together. Worked fine. Then I decided to take it apart once more to try another spring force setting, and while it was easier, it was still quite difficult (remember it is lubed now). The bearing was so difficult to take off the cam bolt. Had to use a screwdriver as a lever to slowly get it off, whereas in the video it just slides off smoothly. Same with putting the bearing back in the casing. It took so much force to get it back in. Is this normal? Maybe the video is just deceiving about how gentle (or not) the process is? :D

I had the T-Link issue as well. Looks like to make it work you have to load the right profile. I found this one on the VKB forums that works for me: http://ftp.vkb-sim.pro/Firmware/BlackBox/BB_v1_81_6.zip I don't think the firmware matters since I'm on a newer one. Just go to the Profiles/T-Link directory, and load the BB_T-Link_v1_81_6.cfg file in the T-Link software (press the Aux button to reveal the aux panel with the load button). Once I loaded the profile, the virtual brakes started working.

Can someone help me figure out how to get the damn cam assembly out of the t-rudders? I'm following the VKB video. After unscrewing all the various bolts, the cam assembly feels loose, but won't budge. Can't see what else could be holding it in.

I had the same when I first did mine, but it's much smoother now. Probably just takes some time to work it in.

I just install it with OvGME. Manually, you can put it in DCS Install Dir\Mods\aircraft\M-2000C\Liveries\M-2000C-CPT or C:\Users\YourUserName\Saved Games\DCS\Liveries\M-2000C-CPT If it shows up as an option in the dropdown, then you installed it correctly. And yes, once you select it in the Special tab, it will always be active.

You have to select the custom livery to use it. Go to Options -> Special Tab. Choose the M2000 on the left, and you should see a dropdown for custom liveries:

Have you tried this mod? Not sure if it would improve things at night, but you never know. https://www.digitalcombatsimulator.com/en/files/3303537/

Thanks, guys. :thumbup:

I'm interesting in purchasing a some T-Rudders. My only concern is that the only shipping option is DHL Express. Will I have to pay brokerage fees for customs clearance? I know this is often the case with couriers, but I've bought from companies where they must have had a prior arrangement with DHL to have no fees (my cell phone for example). edit: Note, I am not talking about customs fees, which I know I will probably have to pay, but the extra brokerage fees DHL often charges for actually clearing the item through customs.

In addition to the previous binds, I suggest you bind Kneeboard On/Kneeboard Next and Prev Page/Kneeboard Mark Position as well, since you rely on a map and dead reckoning for most navigation in the Huey. I find time accelerate is nice to have on the HOTAS too when you're replaying a mission for the 8th time and don't want to spend 30 mins travelling to point B.

Oops. Here's a one-liner powershell that does it. I don't have the hornet, but I tested it with the F-5 which uses the same format I think (}) return res at the bottom). It will add the lines from a text file (in this example MOD.txt) right before the }) return res portion: (gc -raw default.lua) -replace "}\)\r\n\r\nreturn res", ("`r`n" + (gc -raw MOD.txt) + "`r`n})`r`n`r`nreturn res") | Out-File default.lua You'll have to modify the above to include the full path for default.lua and MOD.txt. You might also have to change your PowerShell execution policy to allow local scripts to run: https://superuser.com/questions/106360/how-to-enable-execution-of-powershell-scripts edit: It's actually good you brought this up, because I had been using the ovgme solution without considering the case where the binds file gets updated! I'll be re-using this for myself as well.

You could write a simple batch script. This echo { down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle - 2Pswitch'),category = {_('Special For Joystick'), _('Left Vertical Panel')}}, >> "E:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua" should work. Simply appends each line to the file. Just have to duplicate that general idea for each line. Put that in a .bat file and run it. Might wanna make a backup and test it just in case.

Didn't work for me. I was able to get it going by adding the following lines at the top of two files: .../Bazar/shaders/model/functions/glass.hlsl #include "functions/aorms.hlsl" .../Bazar/shaders/model/functions/ambient_occlusion.hlsl #include "functions/structs.hlsl" edit: Spoke to soon. Worked for the Huey, but didn't work for some other modules like the MiG-15.

The most taxing settings are shadows, msaa, draw distance, and pixel density, so I would adjust those down first. Especially MSAA...if you can live with the aliasing, it's better to turn off because it's such a performance killer. Also, I personally see little to no difference with cockpit global illumination on/off and it can also gain you a few FPS. I also have a 1070, and I have shadows/terrain shadows on Flat, Visible Range on medium, no MSAA, and 1.4 PD. This gets me 40 fps the vast majority of the time (single player) even in heavier modules/maps. If you wanna adjust any of those, it'll probably have to be a trade-off. I prefer the extra sharpness of boosting PD personally and leaving the other things lower.

I got one of these: https://www.aliexpress.com/item/21-23-24-Key-RGB-YMDK-Programmable-Marco-Function-MX-Cherry-Gateron-Switches-Mechanical-Keyboard-Numpad/32916152785.html Lights are nice, more keys than a normal numpad, and it's fully programmable. Can change each individual key, setup macros, create function layers, etc. I love it so much I'm gonna buy a second one.

I have two monitors (DP, DVI) a TV (HDMI) and the Rift S hooked up with no issues, so I don't think having multiple monitors alone would cause the issue. The S does seem to be picky about hardware, just like the CV1. I've had no issues luckily (and didn't with the CV1 either), but man some people are having a hard time. You think Oculus would have learned something and tested this thing on a wider variety of hardware.

Well, I think this is a bug with sling loading. I was able to complete the mission by editing the file and increasing the weight of the cargo to 760lbs.

I noticed today I was wearing the back of the halo a bit too low, like I would the CV1. Having it just a bit higher brought the bottom of the headset closer to my face, significantly increasing vertical FOV, mostly in the lower half of the screen. And I know it's not placebo because I had to increase the masksize in Kegetys' VR mod. I experimented with taking the facial interface off, but I found seeing the view in my peripheral too distracting. I also couldn't get the lenses that much closer to my eyes. I actually think the cushion in the halo itself is the limiting factor for that. It's much less compressible than the foam and sticks out more.