Jump to content

Granny

Members
  • Posts

    35
  • Joined

  • Last visited

1 Follower

About Granny

  • Birthday July 11

Personal Information

  • Flight Simulators
    DCS F-16C, F-14B, JAS37, A-4E, OV-10, JF-22, AS-39, UH-60L
  • Location
    Arkansas
  • Occupation
    Retired C-130 Pilot

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I attempted to fly a couple of the stock missions that come with the FC 2024 F-86. I was unable to get weapons to fire or change weapons modes. Went onto a multiplayer server and weapons worked as expected. Bug?
  2. I'm having this same problem now. Not sure if its the DCS patch that causing it or the fact I installed Steam VR yesterday as well. I run steamVR before and did not get this issue. Also, not using VD, using Steamlink instead. Only solution I have found so far is to completely uninstall SteamVR, Anyone find a better one?
  3. Disregard, figured out the issue. Offending Freqs are in Voice Chat. Servers that use SRS instead of VC are the ones that don't give me the static problem. Pulling up Voice chat overlay in those servers that use Voice Chat allows one to interface with the radios in FC modules. Change the freq or channel there in the VC overly makes the static go away.
  4. I am encountering static on the radios in Flaming Cliffs modules (A10A, F15C) that will not go away. Its only in multiplayer, and seems to be only certain servers, and maybe not even every airfield. I use SRS but that doesn't seem to be the issue as the static is present even if I do not connect to SRS. I can usually figure out which radio it is by keying my PTT. That's the only thing that will make the radio go silent. I have tried using the VOIP controls and set up key binds to power down the radio, change channel, turn squelch on and off, but there is no response. Only the HOTAS Switches I have assigned to PTT seem to do anything (maybe because I have the same set up in SRS). I have tried to use the easy comms menu thinking contacting ATC or something would change the freq and clear the static but that didn't work either. The freq doesn't change. Is there some why to operate the Radios in the FC modules that I am missing? Is this just an effect on the particular server to add "realism" Am I setting up my radios controls wrong? Its driving me nuts, and driving me away from certain servers and certain modules that I really like. Example: Pretense, Syria Map, Death Island , Akritori Airfield - A10A has static on UHF freq 251. Not sure why 251 even shows up in the radio since the Freq for Akritoti is 252 but that's where the noise is and I can't figure out how to make it go away.
  5. Anyone know a good way to tune radios in the Flaming Cliffs aircraft? I fly on a VR headset so tuning radios via keyboard is problematic, and in FC the cockpit is not mouse clickable. I have SRS but I don't if I can tune radios with it. When I toggle on the SRS radio controls, they appear on my desk top, not in the VR goggles, so that's not much better.
  6. Same issue here as well. The 3 new planes did show up in the files and installed successfully. Are the old FC3 planes actually updated? Launcher shows I have 6 updates available but none are listed. The 6 updates would be the original FC3 planes needing update to FC2024. What changes can I look for to see if the update was successful on the original FC3 planes?
  7. I've been trying out multiplayer lately (mostly on TTI), I'm pretty new at it and not very good. I'm trying to figure out radio comms. I'm using SRS on TTI's servers, seems to work but rarely anyone else on SRS. I'd love to try new Voice Chat in v2.9, so far haven't found a server using it yet, maybe I need to look harder. I see the chat box on the left, among the log of events scrolling through it they're also players communicating there. Its text to me but the verbiage suggests it might be Voice chat. Some have even reached out to me, but I don't know how to respond. I see the text, I don't hear any voice. Is that through Discord voice chat or something else? I've heard other players mention just use Discord instead of SRS or the in-game voice chat, I have no clue how to use Discord in the game.
  8. I'm not using steam and tried a couple of the other suggestions but didn't have any luck. (I'm probably doing something wrong). I'm thinking of giving VD a try but I notice the requirements say you need an ethernet connection. Where my system is located I can't run an ethernet cable to my router without some painful construction projects. I do have pretty good wifi signal and good speed though. Is it even possible to use VD over wifi, and if it is would DCS play well that way?
  9. Just discover I have this problem now, had updates on Automatic and now have V63 on both PC and Headset. How did you revert to V62?
  10. Thanks again everyone for your help, I think I have found my happy place. Its not perfect but I'm in a much better, more playable state than I was a couple weeks ago. For anyone interested, the final changes I made was to go with 80Hz refresh rate on the Q2, then on Oculus Debug Tool reduced my field of view to 0.8. This was an effort to preserved some FPS for the next steps. I increased distortion curvature to High, to focus resolution towards the center. Then I started inching PD back up, but in the ODT this time, rather than in game. I don't now why but doing this in ODT seemed to be less of an FPS hit than using the in game slider. 1.3PD is my wall. With those setting I am getting perfectly smooth 80fps, and readable instruments. Not crystal clear, but readable. Still some ghosting and a bit of aliasing but nothing I can't live with. Considering the limitations of my system I am pretty happy. Thanks again. Granny out!
  11. Thanks all for your suggestions and putting up with my lack of knowledge on this stuff. I was caught in this weird loop where I believe more FPS was the answer, and since FPS seem to always be half my refresh rate, I need to increase refresh rate, which drove me to try and run at 120hz just to get 60FPS. I didn't take account the demand my high PD setting had. As soon as I dropped my PD to 1.2, I got all my FPS back, and dropping the refresh rate to 90hz made it smooth, turbo mode made it all pretty stable as well. I'm getting 80 to 90 very playable FPS now, so that seems to be the sweet spot form my set up. So here's my next question. I got to 1.5PD by trying to find a setting the would make my cockpit instruments and such clear and readable. I have cockpit res at 1040, textures high, and sharpness at 0.9. But at 1.2PD all the text is pretty blurry, anything in my MFDs is unreadable without zooming. I suspect the problem is TAA but without TAA the aliasing is unbearable (I really hate aliasing). I had hoped Quadview would help, but I tried that and it gave me a few more FPS but didn't clear up the cockpit display. Is there anything else I can do to sharpen this up or is it something I'm going to have to live with until I can upgrade?
  12. Bear with me, I am an amateur with a no budget for an upgrade. I have to live with what I have so I'm trying o max perform my system and I know (becasue I've seen) it can do better than it is right now. I thought I was onto something new when I discovered the overhead capacity stats yesterday, hence the new thread. Here are my current points of confusion: 1) You're saying what I'm seeing is Motion Reprojection caused by ASW. That makes sense except I've been using OpenXR Took Kit's Turbo Mode for a long time, which gives me a big red warning that it disables ASW. So, is Turbo also a form of motion reprojection or is something else going on? 2) Oculus display tools shows I have in the neighborhood of 97% overhead capacity even before my FPS is cut in half, and it stays there after the cut. In other games I see a cut in capacity but maintain FPS. If I have so much overhead, why is the FPS getting cut? It looks to me like my system has more resources and performance available but either Oculus or DCS just won't take advantage of it. Or do I just completely misunderstand what "overhead capacity" means?
  13. 120Hz is experimental but I do get 60FPS and the best overall results when its stable but becomes unstable sometimes in busy scenarios. 90hz is my sweet spot most of the time for multiplayer. 80hzworks but isn't as smooth. 72 is just annoying. I think its weird that I'm seeing the drop in while I'm just looking at loading screens and menus too.
  14. I don't know how I never noticed this before but I found myself in cold FC3 jet yesterday, and feeling lazy I hit Lwin-Home to get the autostart sequence rolling. This works on my F-16 like a champ, but nothing happened on the FC3 A10-A Then I opened the Controls menu and did a search but could not find autostart. Same for the Mig-29, I assume same for all FC3 aircraft. Am I missing it or is there not an autostart feature in FC3?
  15. I've been troubleshooting some issue in DCS on my Quest 2 and I think I may be on to something, but I don't know what to do about it. I have notice that the DCS FPS counter shows I am getting FPS equal to half of the refresh rate of the Quest 2 headset. I.e if set my Q2 at 120hz refresh rate I get a solid 60FPS on the counter. I have heard that's the result of the headset effectively being 2 displays, one for each eye, thus 120/2 = 60. I think that information is incorrect. I recently discovered the Oculus Debug Tool and its performance Hud did a little investigating. This is what I see, before I load DCS, FPS is green and maxed out, overhead is green and near 100%, very few dropped frames. As soon as the DCS load screen pops up (not even at the menu yet) FPS instantly drops by half, and the dropped frame counter begins to sky rocker, yet my overhead remains green and near 100%. It stays the way until I close DCS. I tried this same experiment on Star Wars Squadrons in VR and this did not happen. I maintained a smooth and steady 120FPS in game play, but overhead dropped to the low 60%s. Dropped frames were very minimal. This is what I would expect to see. So my problem seems to be a DCS issue specific issue. I saw a youtuber that had exactly this same problem on another game. On his system it seemed to be a bug connected with his audio Simply changing his audio output from the Q2 headset, to his monitor speakers fixed the issue instantly. I tried the same but it had no effect. If I have nearly 100% overhead available, i would think I should be able to max out the FPS. I'm pretty sure if I can fix this issue it will fix the other VR anomalies I'm having. Anyone have a clue what's happening??
×
×
  • Create New...