trigen

Hello chaps Ive noticed that whenever you go passed 70% GPU usage in DCS you will get frames lagging and rubberbanding when you look off to the sides or rotating the plane. Its not really stutter but i suppose you can call it that too. I really wonder why this is and how it can be fixed since it leaves a large amount of perfomance out. This was also the case on different computers. I have this is my Pimax but i believe i saw it on my reverb G2 when i had this too. I suppose its a limitation of the DCS engine but are the developers aware of it and working on a fix?

CTS 2.550 TARGET_v3.0.20.427 and TARGET_v3.0.20.826 no trackir Pimax 8kX Tm WH stick Tm cougar throttle. After doing a rebuild i will get Compile Error: Symbol not found: TrackIR in DCS_World.tmc at line 167 no matter what settings i use. If i comment out that in the .tmc file it will just give another symbol fault. No hardware changes Ive reinstalled target and cts (and full cleanrup) a number of times. Any ideas?

Well here we are in 21 and still not fixed.

Beta 2.5.6.5965 When gear is up it will function as the button press ALT ATT and not go middle when no press is detected When gear is down it functions as (switch up) ALT HOLD (switch middle no press detected) middle (switch down) ATT HOLD HDG SEL/ATT HOLD works as intended. Im assuming you intend for the AP to work the same since while not explicitly written as ALT HOLD/OFF it works that way when wheels are down. Laser ARM/off only work as normal up/down so you need to cycle the switch Hope this can be fixed asap

nvm

Hello Im doing some research to get the panel shake/buffeting telemetry output for motion. Ideally it would be in the standard XYZ but from what i can see its done as panel shake inside the aircraft. Now the UH-1 and some others have a Panelshake in mainpanel_init that i see simshaker.lue is using and for example the F16 f-14 and others has no info on it that i can see in the main panel. Any tips on how to do this relatively easy for all modules or does the developer/ED have to enable it in the XYZ telemetry ? This happens to be a major part of the motion in my opinion and is sorely needed for realism. I suppose a 1-100% range would also be good for a noise value [code] Panel_Shake_Z = CreateGauge() Panel_Shake_Z.arg_number = 264 Panel_Shake_Z.input = {-1,1} Panel_Shake_Z.output = {-0.8,0.8} Panel_Shake_Z.controller = controllers.Panel_Shake_Z Panel_Shake_Y = CreateGauge() Panel_Shake_Y.arg_number = 265 Panel_Shake_Y.input = {-1,1} Panel_Shake_Y.output = {-0.8,0.8} Panel_Shake_Y.controller = controllers.Panel_Shake_Y Panel_Rot_X = CreateGauge() Panel_Rot_X.arg_number = 282 Panel_Rot_X.input = {-1,1} Panel_Rot_X.output = {-0.5,0.5} Panel_Rot_X.controller = controllers.Panel_Rot_X [/code] If i look at simshakers.lua it goes something like this [code] local PanelShake = string.format( "%.2f~%.2f~%.2f", MainPanel:get_argument_value(264), MainPanel:get_argument_value(265), MainPanel:get_argument_value(282) dataTable.panelShake = PanelShake

p8kX 75/37.5 3090 Ive noticed as soon as you go over 70% GPU use motion smooth (or a DCS issue?) can no longer keep up and start frame lagging and stops being smooth. its very visible looking out to the sides and leaves a pretty big loss in available performance. You guys getting that?

Makes no difference, its random.

Here you go dcs.log dcs.log.old

Hello Windows 10 2004 Nvidia 3090 457.51 I get this bug where the game window will start in the correct spot and then drop down half a screen. Its been there for at least 3 patches and i get it on my 1080TI and 3090 with different drivers. Its is completely random and the picture looks like its zoomed out and much higher res before it happens.

Hi there! Hopefully you can give me some pointers here. Sadly i'm at a place where i just cant trust that it works. It can work fine all day and then just break from startup ( see comm buttons) or just stop working during a mission. F16C Viper Tm cougar throttle Tm WH stick 2 TM MFD SRS option enabled. Issue 1: Cougar comm switch will work fine and radio 1 is set to Tm game controller root and the respective buttons in SRS 20 21 23. Then for some reason the script wont work and it gives me keyboard 44 for all of the comm switches and it will just give a click on off as its not holding the button. Sometimes restarting the script works but most of the time it does not. Issue 2: Sometimes the TM WH and Cougar throttle buttons will just stop working completely but the MFD will still run fine. Script restart will solve it. issue 3: Sometimes it gets stuck in Commstate and pressing buttons will be F1-F12 etc. I have disabled commstate now

Is there a way to fix the glare on the MFD? I cant see anything if im in the Viper and the sun is on em

Some quick info on the 8k X I run mine on a 1080TI + i7700k perfectly fine 75hz in most racing sims and i run 37 motion smooth for DCS. I can run large or small fov but i prefer small with a bit more SS 2500 vs 3000 res. My 1080TI is slightly lacking there but a 3080 normal or TI version will be more than good enough for me. DCS is cpu limited anyways To get a reasonably clear hud and instruments you want to have a IPD of minimum 65. preferably 66 as with the small sweet spot and canted lenses (Technically you are a bit outside the sweet spot with canted lenses but it does not work with such a small sweet spot but works great for the Index) reporting minimum IPD at 60ish but the center sweet spot actually being 65-66 it is physically impossible to be in the proper sweet spot if you are 64 or 63.5 like me. If you look to the sides more like in a racing or normal game where you dont really need to read things up close it is for the most part fine but if you wish to read instruments and hud you wont get a properly sharp view as you need to look like this \ / since the sweet spot is a fair bit away from your actual IPD. So you either need to extreme mod IPD (made it nice and sharp) it like me or live with a fuzzy center view and more clear when looking a bit to the sides but only with one eye sharp. Image quality is of course much better than the 5k+ at lower SS but you get the jaggies. Sadly the small sweet spot also force you to go higher SS to clear up some of the fuzzy view. Upscaling seems a a bit pointless for performance the moment and feels like its more there to give you the option for higher refresh rates which i think is great. In short its a great HMD that i think is quite future proof but sadly with a very big shortcoming and that's the lenses and sweet spot that really ruins the experience for a lot of people when they cant get a sharp view in both eyes due to the canted lens and somewhat misleading (they never mention anything about being due to canting or any other documentation) numbers. If they make replacement lenses with a better sweet spot and or increase the adjustment range this will be a killer HMD.

Getting this when trying to update to the latest

If you guys dont mind comparing. I find this to be quite odd. Everything works and i dont need to invert in DCS but i find it very odd that negative numbers is full throttle and positive is minimum. I honestly dont remember what it was like before but i just cant get the shut down etc to work. The top of the curve is idle on DCS. Shouldnt that be full throttle? Same way for you guys?

Everything is set as described and tested with several different values. Hc diff is on, using 2 mfd cougar and warthog. Nothing happens in event view either when testing or in game. Any easy way for me to reverse the Z axis so i can check if thats what causing the shutdown to fail?

Thanks for checking it out. No dice either way though. I dont remember what version it was but it was not inverted a couple of months ago if i recall correctly If i hold S3 nothing will happen and im assuming that is cause the axis is inverted and the script wont get the correct axis values. Outside of the script my throttle Z axis is operating normally My Cougar throttle shutdown delay is 0 so it should be instant and but there is no change no matter how long Cougar engine Start and shutdown enabled. 1

Sorry forgot to mention it. Tm Cougar throttle with WH base and 2x MFD

CTS 2.510 In the F-16 profile the Z throttle axis is inverted and i cant get any throttle shutdown/startup to work. I have not tested any other profiles.

Just bought this mint FSSB R3 with the WH board installed but the universe decided my car was going to break so its with a sad heart i sell it as i have just upgraded my computer and VR and soon the PointCTRL so im broke for quite some time. Norway only as stated due to taxes etc. Selling for the price i gave. 4880kr +shipping. New price would be 6500+ with shipping and taxes

Bug 2.49 F16C WH and HC profile, maybe more. BTN 5 reported as 29 NWS is assigned btn 30 + 5 which should be canopy close\open Canopy open close is not assigned, should be with BTN 5 mod 30 held Pressing the F16 Viper cougar picture in references will open a larger picture but with Warthog and not Cougar throttle.

Ah thanks, Missed that one! Then there is hope!

Apologies if this is already mentioned. Couldn't really find anything. While i realize this is not a top priority i would very much like to get a pilot in the seat for VR. This for me is a huge part of the immersion and also a really good tool for getting to the correct seating position and 1:1 with the aircraft. Hope to see this really soon.

Waiting for AMD and TI seems to be the smart way to go here. Hard to wait but one will almost guaranteed to be better off keeping things on ice for now. Exciting times though! Cant wait to crank up the SS and run 120/144hz with motion smooth on my P5k+ Or perhaps even 90 and Large fov if possible.

I'd like to buy the FSSB R3 Pm me if you got one to sell Managed to get a R3 Warthog.