zero2005

So, me and my buddy are trying to get multicrew working for this thing, got everything *mostly* working, although it's kind of annoying that I cant flare from the left seat, and several of the switches are unable to be operated from the left as well, but the most important thing is that the TV is completely unusable -- we're both in VR and the camera is so unstable and shaking like Michael J Fox is at the controls. My buddy is trying to hold it as steady as possible but it's just a straight no-go at this point. Is there any fix for this, or should I just chalk it up to being broken at this point?

Also running 200% SteamVR SS, was using PD of 1.5 and noticed that the SteamVR is slightly more stable, and I was able to add 2x MSAA because of it. Noticed no difference going to Low on the windows setting, Make sure that the WMR window isn't repeating! make sure you hit that Pause button otherwise its an additional layer of rendering. I had this happen a few times and it caused some weird issues.

Just a tip, after you delete the shadows.hsl file, you can launch the game, then go to the multiplayer tab, and hover over the red shield, which will give you the list of incompatible files; delete those, then you'll have a mostly working multiplayer acceptable shader mod, it won't be 100%, but it has helped my frames a ton and made it so I can actually play with reprojection on with my current setup and a solid 45 frames with a frame time between 10-15ms; 200% SteamSS res.

I was just having this issue, and mine was an issue with the newest Nvidia driver, 441.61; for some reason it just was not initializing itself. I rolled back to 441.41. EVGA 1080ti SC2. Might be something to look into -- if you don't have the Nvidia control panel icon in the bottom right corner, and/or you go to device manager and look under display adapters and your GPU is showing a caution sign, it's because your driver didn't initialize -- no driver == no go. I could get .61 to run right after I installed it, but as soon as a reboot happens, it fails to initialize, and I'd either have to install .61 again, or just roll back to .41 and be happy.

Is there a fix for this error? shader "bazar/shaders/deferred/compoxe.fx" failed to compile

I just noticed it keeps bringing up the comm menu when I press the pinky nose wheel steering button. This is kind of annoying as it brings up the cursor and the menu when I don't want it to. Any way to turn this off? I understand that this button is a PTT in the real jet, but having it bring up a menu is an odd choice...

1080Ti (Evga SC2) and an old ass i5-4690k here, new Reverb user. I wouldn't say it works flawlessly for me, I think i'm at the limit of being CPU bottlenecked. I have a 3800X sitting on my desk but got cucked by amazon on the motherboard. Said it'd be here 4 days ago "guaranteed shipping"... won't be here till saturday. Anyways, If I turn everything down (ie clutter and the other things that don't matter) and set SteamVR SS to 100%, and PD to 1.0 I can get a respectable 50-60 frames solid, sometimes peaks out to 70. I couldn't really tell that much of a difference for about an hour or two worth of testing. I'm just now playing around with reprojection to see how it goes, if I can get a solid 45 frames and increase the res/eye candy slightly I'll be happy I think. Oddly, I've found that sometimes going back to desktop, opening up MSI Afterburner or EVGA Precision X1, and hitting "default" to reset it (even if nothing was changed) nets a decent performance boost for some stupid reason. Boosting Voltage/Power limit seems to create more problems than it solves, but the problem only seems to appear in DCS.

What settings are you running on the Reverb? Mine should be here tomorrow hopefully. Currently on a 1080ti with a i5-4690k, waiting on motherboard (be here friday) to upgrade to 3800x so I'm curious how well it'll run with my older i5. Just returned two Pimax 5k+, was running fairly decently for the 10 minutes or so the one was working before it started screen tearing, with around a PD of 1.5 and a SteamVR render at approx 2560x2560.

I'm gunna add in another HARD NO to Pimax 5k+ as well. I just returned two of them. one had a screen DOA, other had right eye screen tearing and shimmering on lower half. Just ordered Reverb. Thank god for Amazon returns as well. IF anyone decides to Pimax -- get it through amazon, that way if any issue arise, you can just send it back.

Interested in purchasing a VR headset, Been following the Pimax stuff (specifically the 5k 120hz). I haven't used VR in a couple years (around time the CV1/Vive was released). Just wondering if anyone recommends getting the Pimax 5k now, or waiting? Just ordered new Mobo/CPU/Ram, upgrading from 4690k and 16gb ram to AMD 3700X and 32gb 3600mhz soon as it arrives. Already sitting on a 1080ti, no plans on upgrading that right now. How well will the 5k run on this? I'm the type of guy who prefers to run lower graphics to obtain higher frames, so if I have to run a lower setting to obtain acceptable results, but maintain a higher res/FOV I'll gladly accept that. For me, the SDE when I used the CV1 was too much, was not a fan. Also the FOV was very restrictive. When I played around before, both the Vive and CV1 were cool but not enough for me to really consider dropping money on. I'll literally be using this 99% for DCS, everything else is secondary. I wear glasses (nearsighted, 20/400 or -4.0, both eyes) and my IPD is ~62mm, though I occasionally wear contacts. My other question regards the base station, I was considering just getting a used one off ebay, for DCS and 6DOF do I only need one (again, just for DCS)? I don't need nor want the controllers (yet, maybe down the road). I've read some people complaining about have to "wake up" or reconnect the 5k? Can anyone expand on that? If it's a simple fix I'm willing to live with it if the display gives me what I'm looking for. Also, I use decent headphones (Fostex T50RP mk3) through a desktop DAC/AMP. how well does the Pimax fit with aftermarket over ear headphones?

Is there an easy way to delete a controller, all it's button and assignments, from all aircraft? I'm having an issue where DCS in its infinite wisdom decided to map my EDTracker Pro to pitch/roll/yaw... I'd rather just turn off automatic profiling if at all possible. On top of that, is there a way to share axis assignments to all aircraft? I generally always set the same axis and curves for all aircraft, with the exception of helo's.

Anyone have any mods to fix this, specifically on NTTR? really annoying to be flying over vegas in some missions that place units IN THE CITY which you can't even engage as they blend into the buildings which are "hotter" than than the units (never mind the fact they have a tendency to spawn inside buildings)... or BUSHES that glow as if they're actively burning missiles. i've basically reverted to never using BHOT or WHOT, only CCD... even better when Mr. AGM-65D also locks on to said bush because its a glowing hot target...

How are you liking a single large 55" curved screen? what screen is it? any recommendations? I'm currently on a 27" 1440p, with a secondary smaller 1680x1050 21" (mainly for multitasking outside of DCS) and thinking of going to a single large screen. my biggest problem would be the potential for input lag. I also want to stick to a single screen, only using multiple screens for multitasking purposes. i'm holding off on VR until something like the Pimax 8k becomes "the standard" (ie at least 4k native display per eye, even if input is upscaled) with native support. also, as for feeding oxygen to a mask; there were small compressors available for painters (fresh air respirator), or you could even use the 3 element filters from a small air compressor in a garage; though i'm not sure i'd trust that depending on your compressor. (also adds to cost if you don't already have a shop compressor) you could also look into something we use for our "chemical defense" called AERPS -- the blower i believe is called CQU-7/P. if you get a legit one, and a legit mask, the connections should all hook up directly. the unit iself runs off batteries, and has a power adapter, but you'd likely need to build a power supply. the batteries themselves are odd, though i'm sure you could make them from rechargeable lithium cells.

all my exports for A-10C and KA-50 have stopped working, i was using Gadrocs & Capt Zeens luas, with individual monitorsetup lua's (not using reconfigure for unit). i've tried downloading a few others to no avail. is there a workaround?

I wasn't "comparing" them -- i was just looking for a reasonably priced rudder pedals. my only complaint is no toe brake, but its fine, don't really use that very much anyways, and now i can just assign my unused X52 twist axis to differential wheel braking. these things are built like a tank and put a shame to anythign else on the market. i got them at a steal IMO for only 250$. it just saddens me that there's no halfway decent options under 150$ (or now 250$ for that matter) when its such a simple ****ing thing to do. TM really screwed up with their new one -- funny thing is they had a damn amazingly designed set back in the day that was serial port (i had a pair, no idea where they went otherwise i'd be using them!) -- they could literally have reinitiated them, updated them to USB and they'd probably outsell the saitek bullcrap if it were reasonably priced. the axis is NOT already assigned, it tries to assign "joy_RZ" axis IIRC, but default the VKB uses joy_RX axis. so not only do i have to go unbind the joy_RZ axis from my x52, i also need to rebind the VKB axis from the RZ to the RX

yea, if i'm going to spend the time setting the axis to each aircraft (again) then i'm going to add the curve in DCS. tbh the VKB software is very bleh, granted it doesn't bother me -- i don't need the software for anything when all i bought this for was the rudder axis. just having issues with DCS not letting my save my controls because every time i exit the setting screen (1.5.4) by hitting OK it freaks out and goes to black screen, and won't return to main menu.

ordered the VKB rudders due to the inability to find saiteks for a reasonable price (rumor mill says they may be going out of business/having budget problems?) and TM's new budget pedals being absolute garbage. my question is, is there a way to bind the axis for the VKB to every rudder axis in the game with a specific curve of 20, without having to go through each menu? i just went through and TRIED to do that, but due to 1.5.4 being buggy with the settings menu still -- it didn't keep my settings after i hit OK and it went to black screen and eventually CTD... i just want to set my VKB joy_RX axis to every rudder axis in the game by default and add a curvature of about 15-20.

does that mac have an HDMI in, or are you getting the navmap & TGP streamed via network? I have an Asus T300 i'd like to use as a tertiary control w/ helios, but getting it to display the TGP or nav map would help. only way i believe i can do this is via network. I think i can do helios via network, but unsure about how to go about streaming the display unless i actually use something like remote desktop?

Just a quick update, i managed to get the shkval and abris exported and somehwat sized properly, and helios is installed, profile is running good, but the actual helios overlay isn't responding to DCS? i went in, opened the profile in the editor, updated for my specific monitors and changed my DCS path to match. the profile included folders to drop into the DCS path and i did that. by not responding, its not letting me click on any of the buttons and the actual gauges arent showing data from DCS. any help appreciated. EDIT UPDATE: all problems lie with export.lua, i have since fixed it and it is working great. swapped my 19" monitor for one of my old 1680x1050 monitors, and super-res'd it to 1800x1440. not ideal pixel quality, but it makes sizing sooo much easier than having to do a bunch of math. I'm on to doing A-10c exports now, but i can't get those to work. for exporting over to different computer i may use helios, and/or i might make a virtual monitor and use Spacedesk to display that virtual monitor on the laptop or another remote desktop application for the exports

just started my journey into multiple displays. current setup is a single 1440p x-star monitor (overclocked) and i just plugged in a 2nd cheap 19" 1280x1024 display from like 10 years ago. but I also have a spare asus T300 chi (basically a surface tablet that has a detachable keyboard). I have little to no experience with helios but i can't seem to find much information on it that isn't 5-6 years old. my main question is, is there a way to use my tablet over network, with its touch screen capability, to display and control cockpit items? right now i'm mainly interested in the KA-50, though eventually i will branch into different things like the M2000 and A10C. 2nd question is, would "shedding the graphical load" make sense? ie passing the info to a 2nd/3rd computer via network -- versus running a single computer to handle a larger than normal desktop.

Thanks, appreciate it. installing separate versions and rolling back current to stabil for the time being. hopefully it doesnt try to auto update again.

dang, just got updated automatically without thinking about it. first time running DCS using the actual DCS install vs Steam, and it auto updated me to 1.5.4 any way to revert back so i can get on the 104th?

If you load more ordnance on one side (or use ordnance from one side) it will also throw your trim out depending on the weight. also, what stick are you using? some of them are pretty innacurate in middle -- my X52 requires a deadzone of around 7-9. and thats centered, if i even breathe wrong sometimes it wiill require more, but i've found if i bump it up i start really loosing a feel for the center... (and is why i'm ordering a TM Warthog as soon as i return home) one thing to check is hit right control + Enter. this will show your control indicator, which will allow you to see where your controls are in relation to dead center... if you notice that your stick is off center to the left, then its probably either a deadzone/calibration issue OR a trim issue..

yea, i've noticed it doing that too. or sometimes the AI will just lock in position, so when i go to move to the contact position, he just keeps it where it is, which ends up looking like hes trying to plug my engines lol luckily there's no strike until the boom ruddervators contact the aircraft. i just wish the contact position was fixed. in its current location its too easy to pop in/up just a bit too far and strike the boom, causing all kinds of problems. the boom also never calls a breakaway and fails to move it if you come too far in/up. i've only gotten him to call a breakaway one time, and it was because DCS reset my Axis curves which really threw me off lol. the breakaway isn't animated properly at all either. the PDI lights should flash on/off (all of them) and the boom should raise to avoid a collision. the aircraft will accelerate at MCT power, and start a gentle climb to the "top of the block". tankers work block airspace - ie FL240BFL260 which is 24,000 to 26,000, and they will usually sit at 25,000. in the event of a breakaway, the receiver will drop to the bottom, tanker will go to the top (if necessary). after a disconnect is initiated the boom would also raise up to about the 0 elevation area. i can live without these, but the contact position is the biggest problem. give the AI some kind of control over the extension, basically, when receiver is in the contact position for "X" amount of seconds, start extension at "Y" rate until contact is made. the AI already starts to move the boom to align with the UARRSI when you get within a certain distance, so i would think it shouldn't be too hard to add an extra few lines to do the same thing for the extension. after contact, the extension will be controlled by the receiver aircraft position. if i knew anything about modding, i'd implement this myself IF it was possible to adjust such things.

Just wondering, is this a known error, or is it just modeled incorrectly? Basically, flying the F-15, I get into the AR position, and the AI boom operator will not make contact -- even though I am in the envelope to do so. I have found in order to make a contact I need to come close to the forward and upper limits for the AI to plug me. this is not how it should be, the boom can make a contact anywhere within the limits. what i am seeing is that the AI basically has no control over the extension of the boom? i've found the PDI lights to be accurate at least. is there a way to fix this, or mod this? i've also found that the AI boom bugs off sometimes (aims toward one side or another of the UARRSI), requiring me to back out, cancel the AR, and re-initiate. I would suggest another radio option in the menu to "reset" the AI such as "returning to pre-contact" - then once in the pre-contact position, i can state "pre-contact" as usual and move in. many less keystrokes that way. If there are any other questions regarding AR, i'd be glad to help - i'm a KC-10 flight engineer. also, why is there no KC-10 stock? I read somewhere that one could be modded in, i'd like to give that a go and see how the envelope is on that as well.