Jump to content

Eclipse4349

Members
  • Content Count

    171
  • Joined

  • Last visited

Everything posted by Eclipse4349

  1. Holy **** where did you find that?? It worked... I didn't even have to log out. Thanks!
  2. I wouldn't want to see a meter or other HUD indication, but subtle cues like gasping and straining, along with the visual cues, could probably be tweaked a little without getting gamey. IMO the cues are fine as they are, but that's just my opinion. I've been able to avoid blacking out many times by easing off the stick thanks to those cues. Other times I haven't, and that's because I was too abrupt and that was the result.
  3. Focus not so much on memorizing gauge locations, but on the look of the gauge. All oil temp gauges, for example, will be split into 3 parts - the upper arc is the oil temp, the smaller vertical side needles are for oil pressure and fuel pressure. Loss of pressure is an indication you have a serious leak. No matter whether it is Russian, German, or American, the gauge will look this way. If it's a temperature gauge and it doesn't look this way, it's either water temperature or cylinder head temperature (and I don't believe you'll ever see both in the same aircraft, unless some later-war aircraft include both. I don't own them all yet). The altimeter will always have 3 needles of different lengths, for 100, 1000, and 10000 meters or feet. The manifold pressure gauge will always respond linearly with throttle position changes. The RPM gauge will respond directly to rpm changes, and lag a bit as it takes time for the propeller pitch to adjust. In time you'll be able to easily pick them out by sight, just by seeing how they are scaled and marked. Feel free to ask about any specific ones you aren't sure about.
  4. Haha, the gauges will all make sense to you soon. Most gauges for a certain thing are similar, whether they are Russian, German, or American. And you can also make changes to controls and observe how the instruments react to determine what some of them are. Once you learn them well in 1 aircraft, all others will be simple to learn.
  5. I too always had this problem with TrackIR and just got in the habit of reentering it very frequently. Looking away from center by a good bit, for example when tracking a target through a maneuver, and then lining back up and looking fairly straight on, the view would be sitting well below where it used to sit. I never thought to delete all view and camera related keybinds and inputs that were now handled by TrackIR. I mostly use the Rift S now, but I'll probably delete all camera related controls anyway. Maybe it will end up being the fix for the occasional VR "view shift and reset" that happens every once in a while. It's brief and it doesn't require me to do anything to bring it back to where it should be, it just spazzes once in a while and then over 1 or 2 seconds drifts back to where it should be. This TrackIR fix has me thinking maybe it will fix that also. Thanks to all who took the time to work this out and verify it!
  6. Agreed! This is something I've advocated for off and on for quite a while. Thankfully, the community is full of good people with the time and ability to do great things. I haven't used the 3rd party tools others have suggested myself yet, but I've flown in missions and coop campaigns that prove just how great these tools are. It would be great if one day we have a multiplayer lobby and party system, with a QMB-style set of parameters we can set to generate simple mission scenarios. For now, we have various Discords, the editor, and some really great 3rd party tools.
  7. Welcome! Here is a link for the IL-2 Box discord: https://discord.gg/Hd3EzA The community around this game is nothing short of amazing. It's such a nice break for the typical internet toxicity.
  8. I have done this in all aircraft, pretty much always. Some of the older Russian aircraft (the Yak-1 I believe, for one) have "ambient" lighting rather than backlit instruments, so for some it's situational. But for most it's a necessity! It's funny how the little things can make a big difference!
  9. You're welcome. Making smooth and controlled movements is key, more so now that G effects and tolerance are better simulated. Maintaining enough airspeed and managing your rudder to not stall or slip yourself into a spin is also important. You can also stall at higher airspeed by deflecting your control surfaces so severely that you lose lift from the airflow over the wings being too disrupted (an aerodynamic stall, caused by pulling too hard and putting your wings at too high an angle of attack). If you don't have rudder pedals or a twist rudder on your stick, make sure you have rudder assist toggled on. Maybe you already know all this, but if not I hope it helps.
  10. The new physiology system takes into account not only how many G's, but also how fast you reach high G level, and how much positive and negative G you've had to fight through up to that point. If it's bad enough, you don't just black out, you'll be unconscious. Spins are the same as far as I'm aware, you just have to maintain control. I'm not aware of any changes that would impact going into a spin. Maybe somethimg changed with your control curve or calibration? It sounds to me like you're just having trouble managing G load and keeping control, for whatever reason. The new system is great from all I've experienced, and the old system is still there if you turn off the advanced physiology. If none of that is working for you, it sounds like a problem on your end. Good luck getting it sorted out!
  11. I had the icons Grey out again tonight. As the first poster I quoted said, logging off and logging back on worked! The controllers were back, nothing was greyed out, and it was in the mode I attempted to put it in when it greyed out.
  12. This issue is back with a vengeance. I restarted more last night than I have in a long time. I came across this solution on Reddit a few minutes ago, so I'm spreading the word: Post 1: When the buttons grey out, sign out of windows and then sign back in. The devices will reinitialize and Control Manager will be in the mode you had tried to switch to. I have used this solution, and can confirm it works for me and for a friend. Post 2: Turn off and Disable the Windows Service called SysMain. That fixes all the issues. It gets reenabled by updates though. *Edited for better wording.* The service has something to do with precaching for the windows metro apps. If the buttons grey out again, just open the Windows Store app. Disabling SysMain completely fixes it. Post 3: Killing the Microsoft Store process in the task manager literally fixed every single problem I've had with Control Manager in Windows 10.
  13. Restoring an old version of Windows sounds like a bad idea. You won't get security fixes and whatnot. I came across this potential solution a few minutes ago on Reddit, so I'm spreading the word: Post 1: When the buttons grey out, sign out of windows and then sign back in. The devices will reinitialize and Control Manager will be in the mode you had tried to switch to. Post 2: Turn off and Disable the Windows Service called SysMain. That fixes all the issues. It gets reenabled by updates though. *Edited for better wording.* The service has something to do with precaching for the windows metro apps. If the buttons grey out again, just open the Windows Store app. Disabling SysMain completely fixes it. Post 3: Killing the Microsoft Store process in the task manager literally fixed every single problem I've had with Control Manager in Windows 10.
  14. I just came across some possible fixes for the WI does 10 issues a few minutes ago on Reddit. I will be trying this when I hop on this evening: Post 1: When the buttons grey out, sign out of windows and then sign back in. The devices will reinitialize and Control Manager will be in the mode you had tried to switch to. Post 2: Turn off and Disable the Windows Service called SysMain. That fixes all the issues. It gets reenabled by updates though. *Edited for better wording.* The service has something to do with precaching for the windows metro apps. If the buttons grey out again, just open the Windows Store app. Disabling SysMain completely fixes it. Post 3: Killing the Microsoft Store process in the task manager literally fixed every single problem I've had with Control Manager in Windows 10.
  15. Make sure the host has the ports forwarded. Hope you've already solved this issue! The latest patch broke COOP missions - once you pick a plane it just hangs. But you should at least be able to connect to each other if you have the ports forwarded. They are indicated in the Multiplayer section of the settings menu, I believe. Hopefully the devs patch the COOP situation soon.
  16. This. Hopefully it gets fixed soon! I just set up a 2-player COOP bomber intercept practice mission with a random chance of fighter escort and all Russian planes available to choose from and I can't test it. At least I've re-learned the mission editor a good bit. I'm sure they'll have it sorted soon. Until then, I'll just keep making more practice missions.
  17. Awesome, thanks for replying! I think this is where I ended up after testing of my own. As usual, the community doesn't disappoint. I'll be very interested to see your results. I assume AA is still a no if using SS? Does it matter anymore if the SS is applied through SteamVR or Oculus? Is Open Composite still significantly better than SteamVR in terms of performance headroom?
  18. You do have to target specific parts of your target, more so than with a larger cannon round or an explosive round. As others said, you could riddle the target with holes, but not hit anything vital. If you target something specific, like the engine, cockpit, wing roots, etc, the 50s will do major damage. A quick burst to the engine and its on fire. A half second or so of fire concentrated to its wing root and it will likely snap the wing when it tries to maneuver, if you don't just chew threw it and take it right off. If you're just spraying all over the place and you're not in convergence range, you might not do a whole lot.
  19. This could explain the other night. Attempting to host a coop for a friend and I to start getting him acquainted, and I got the infinite loading screen, and he never saw the lobby. We quit and he tried hosting, and it also wouldn't fully load, even though I saw his lobby and attempted to join. So we joined an empty PvPvE server instead. Hopefully this gets sorted out. I'd like to be able to host short, repeatable training missions for various things.
  20. Can confirm, the 9700k with DDR4 3200mhz and a 2070S with a Rift S performs very well. I just upgraded from a 2700k and DDR2 and a gtx 970 a couple weeks ago and got the Rift S. It's NICE. Like amazing nice. And I still haven't overclocked yet (coming soon, after I get all this SS and AA and SSAO and Sharpen stuff figured out). I can't imagine a 9600k would be that much different. I picked up the 9700k for $300, FWIW. * edit: purchased from Microcenter: https://www.microcenter.com/product/512484/intel-core-i7-9700k-coffee-lake-36-ghz-lga-1151-boxed-processor * Good luck and enjoy the new build!
  21. Hi all, There is so much conflicting information out there that I could really use some clarification. If I understand the situation as it stands now, SS causes the game to not render distant targets well or at all, and the best settings for spotting and target ID are: SteamVR SS: 100% (no SS) No Advanced Supersample Filtering Oculus No ASW 1.0 (no SS) In game AA: 0 Landscape filter: blurry 4K textures Sharpen: ?? SSAO: ?? Please correct me if I'm wrong, and I would appreciate info on SSAO and the Sharpen checkbox. Also, is it only SteamVR SS that causes contact rendering issues? Should I use SteamVR SS at 1.0 and then increase Oculus SS as far as my system can handle? I think turning off ASW in the Oculus Debugging Tool took care of the blurry, doubled contacts. But I am struggling to solve the flickering/half there, half not there appearance of contacts that are more than 0.5km or 1km or so away. Unless the contact is pretty much in guns range, it's seems... Off. I know it will take practice and that's fine, but I can barely see and track it if I'm, say, 1000m above. It isn't so much that the rendering is tiny, it's that it just doesn't appear to be "right". For reference, I am running a Rift S with an i7-9700k, DDR4 3200mhz and RTX 2070 Super. I finally moved on from my 2700k and DDR2. 😁 Hopefully someone can clear up the settings confusion once and for all, and then I can just know that it's as good as it can be and practice from there.
  22. This was my experience, also. I've been away from flying a while, just getting back to it, but I haven't had any problems. I also have a brand new installation of WIN10, FWIW. I hope this issue is resolved for everyone else, also!
  23. Turns out, after doing a lot of research while building a new PC for my mother-in-law, I decided to finally upgrade from my i7-2700k and gtx 970, and I ended up picking up a Rift S also. I have to agree, the immersion is AMAZING. You really do feel like you're on the cockpit. I still have some adjusting to do, you really do feel the physiological effects of maneuvering to an extent. I haven't flown in VR enough yet to know how I would compare it to the 3 monitors at 5460x1080, but I can't see not wanting to fly in VR now that I have it. Having said that, I don't know if I'll be able to fly for long periods with it, so I may still end up using the 3 screens and TrackIR some of the time. So, I'm still hoping to see this fixed some day!
  24. All I want (being a triple 27" user with TrackIR) is for menus, the bombsight, and the map to appear as they do when on a single screen. The bombsight is completely unusable with 3 screens, which should be a higher priority to fix than the rest.
×
×
  • Create New...