Jump to content

[Pb]Shakalakah

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About [Pb]Shakalakah

  • Rank
    Member

Recent Profile Visitors

217 profile views
  1. Brief description: Key commands from T.A.R.G.E.T are not always registering within IL-2 BoX. Detailed description, conditions: I fly with a Thrustmaster Warthog and use the TARGET GUI mainly to give myself modifier keys on the CHF/CHB and joystick paddle. I have to repeatedly hit my desired button (Example: Joystick pinky button is KP 5 to recenter VR, have to hit 5-6 times before IL-2 registers it). The Target GUI has an event tester you can open while a profile is running, and every key press is registered with 0 delay, even commands that might be "Shift + C" (There was an issue with trying to do Shift/Alt/CTRL + "key" during BoS, but I'm experiencing something different). This didn't start happening until update 3.010. I'm playing in VR, but I feel like that shouldn't matter. I'll do a test with TIR to see if it persists. Additional assets (videos, screenshots, logs): I'll come back to this. Your PC config data (OS, drivers, specific software): Windows 10 Thrustmaster T.A.R.G.E.T. GUI IL-2 Battle of Kuban
  2. After the update 3.010 I noticed that when I run a T.A.R.G.E.T. profile that there is delayed or even unregistered key presses within IL-2. I have to repeatedly hit every button to get it to register. You can imagine the frustration during a dive bombing run. I'm curious if anyone else has noticed this, or even use the Thrustmaster GUI. I know there was an issue during version 1.0 where if you programmed a command within target that used a modifier key, the only key press registered was what came after the modifier key. This is not that issue, it's even happening for my recenter VR button which is KP5 (located on pinky). (I remember having that issue, fixed it by changing their type from pulse to hold, even though it's a momentary press.) [However, before this last update, pulsed commands that were for example "Shift + 5" seemed to be working fine in IL-2. Not sure what verdict is there] Should mention I'm using a Thrustmaster Warthog. When I open the even tester while the profile is running, every key press gets registered, with 0 delay. Even my key binds that utilize modifier keys register flawlessly. Yea yea, don't use TARGET. But how else can you get modifier keys within IL-2 BoX? I'd love to see the Devs implement something like that, similar to DCS, but I can't imagine that's something on their priority list.
  3. Ah, I made this late last night, I’ll repost in proper forum. Thanks
  4. After the update 3.010 I noticed that when I run a T.A.R.G.E.T. profile that there is delayed or even unregistered key press within IL-2. I have to repeatedly hit every button to get it to register. You can imagine the frustration during a dive bombing run. I'm curious if anyone else has noticed this, or even use the Thrustmaster GUI. I know there was an issue during version 1.0 where if you programmed a command within target that used a modifier key, the only key press registered was what came after the modifier key. This is not that issue, it's even happening for my recenter VR button which is KP5 (located on pinky). (I remember having that issue, fixed it by changing their type from pulse to hold, even though it's a momentary press.) [However, before this last update, pulsed commands that were for example "Shift + 5" seemed to be working fine in IL-2. Not sure what verdict is there] Should mention I'm using a Thrustmaster Warthog. When I open the even tester while the profile is running, every key press gets registered, with 0 delay. Even my key binds that utilize modifier keys register flawlessly. Yea yea, don't use TARGET. But how else can you get modifier keys within IL-2 BoX? I'd love to see the Devs implement something like that, similar to DCS, but I can't imagine that's something on their priority list.
  5. This was absolutely right. I never thought to put ASW back on, as before my system wouldn't have been able to handle it. Since my upgrade I guess I was sold on still keeping ASW off. The gunsight/prop blade jiggle comes back with ASW on, but I'm hoping Lefuneste's mod will solve that. Still troubleshooting that. Thanks everyone.
  6. I'm unfamiliar with this mod, I'll look into it. Yes I turned ASW off because of the crosshair issue. Thanks for everyones input. I'm gonna come back to this after more tests.
  7. Hello, I've tried numerous suggestions from this forum, yet I'm still having a problem achieving an ideal VR experience. To elaborate on my issue; other planes, the edges of the cockpits, trees... all develop some sort of ghosted image right behind/next to it. Makes identifying friend or foe that much harder since I'm seeing double. Its only extremely noticeable when I'm rolling my aircraft, or if I start moving my head around (so basically all the time). I'm otherwise able to hold 45+ frames consistently, even whilst the problem occurs. (I've tested this by watching my frame rate than rolling my aircraft, frames don't decrease but the ghosting still occurs.) Been only playing Multiplayer lately so I'll have to do a test in regards to campaign mode. I've been playing VR for two years, I understand how focusing is different, it's not that. It's definitely happening inside the headset/game and not just my brain. I have no issues using the gun sight (until of course i have to roll or adjust my head postion). I'm hoping there's something I've overlooked with my settings. Here are my PC specs: ASUS ROG Maximus X Code Intel i7 8700k EVGA GE FORCE GTX 1080ti (Driver version 397.64, most recent) 16GB DDR4 Rift CV1 I'm only using 1 Oculus sensor, with my touch controllers in close proximity. I have to do more testing with having a second sensor up, but I've seen this before with my 3 sensor set up as well. I have IL-2 loaded onto a 1 TB SSD that I have all/most of my games on, it's almost full, but I wouldn't suspect that to be the issue...? I used to use the Oculus tray tool with a profile for turning off ASW and adjusting the pixel density (nothing over 1.5). Even when I would set P.D. at 1 I would still have this issue. I've since reverted to turning off ASW in Steam VR (Left CTRL + NUMpad 1) and adjusting the P.D. in there, trying to in theory limit the load on my cpu. My graphics settings: Ultra Screen Res: 1024x768 (when in vr) UI scale: 100% Shadows Quality: Off Mirrors: Complex Distant Landscape Detail: Normal Horizon Draw distance: 130 km Landscape filter: Off Grass Quality: Normal Clouds Quality: High Dynamic Resolution Factor: Full Anti aliasing: 4 Gamma Correction: .9 SSAO: On HDR: Off Sharpen: On Use 4k textures: On I've done tests at lowest graphic settings while still being able to recreate the problem. I've since turned things back up since I at least want to play in a rich environment. I have more testing of my own I'm going to eventually do, but I'd love to hear if anyone else is experience something like this and was able to find a fix. Thanks
×