Jump to content

audiman

Members
 View Profile  See their activity

  • Posts

    36

  • Joined

  • Last visited

 Content Type 

Everything posted by audiman

  1. audiman
    Same issue for me, using the thumb min-stick on the stick of an X56 Hotas. Tried using the mini-stick on the throttle and same issue occurs.
  2. audiman
    Also have this issue. Although it's not EVERY time, it normally happens on the ground when I press "Route 1 setup" after adding waypoints. It has crashed at this exact step many times. I also had it crash yesterday after shooting down an Mi-28 on Rotorheads with an APKWS. Got the BDA and DCS crashed to Desktop. I've had random DCS crashes in the Kiowa from either navigation menu stuff or just randomly flying and DCS crashing to desktop. the worst is when I fly 15-20 minutes to an area and shortly after I start to search for targets or engage them, DCS crashes to desktop. essentially wasting half an hour for nothing. Having said that, the Kiowa is by far the most fun module in DCS for me right now, aside from these game crashes lol
  3. audiman
    I'd also HIGHLY recommend the OH-58D Kiowa. It's like a very small and much simpler Apache, except it flies like an absolute DREAM compared to the Apache. I love the Apache, don't get me wrong, but Polychop absolutely knocked the Kiowa out of the park and the overall flight model, and ESPECIALLY specifically the AI Pilot, feel far superior to the Apache. I say that with no real life helicopter experience...so take it for what it is. But the Apache currently requires VERY smooth inputs and you basically need to be in a very stable/trimmed Hover before engaging Attitude hold. And even then, sometimes it will wander and float around(sometimes violently) for a few seconds before it stabilizes. Also if you use Altitude hold, make sure you do not move the collective at all, as it will sometimes disengage the hold mode even with the slightest drift of collective input from pushing buttons. This is my biggest problem, I have a Logitech X56 Hotas and the throttle(collective in this case) does not have enough friction to hold it still while I press buttons to operate various systems.
  4. audiman
    Same issue for me, though I'm on the Steam version. the past month or two it has been SUPER slow to get past the splash screen when first launching. It currently takes 2-4 minutes to launch to the menu which is outrageous. A year or so ago I found a thread mentioning that you could omit DCS from Windows Firewall and it would load faster, which I found to be true. DCS would load in under a minute normally. But now it's back to being SUPER slow to launch and I double checked the Windows Firewall settings too. DCS, for me, is on a 1TB NVME M.2 drive, a Samsung 980 Pro.
  5. audiman
    I have the same thing on my left and right monitors. I believe it is the outline of, what would be, the visor when it is down. Look in controls, search for the visor to find the keybind(RALT+F i think...), activate the visor, and you'll notice that those graphical marks on the left and right monitors roughly coincide with the edge of the visor. I'm sure it's just a small graphical error that will be patched.
  6. audiman
    +1
  7. audiman
    Do you happen to have pictures of how you mounted the MIP to the Track racer frame? And how you modified the seat for center stick? I have the TR120 frame(non-motion) with VRS DFP pedals and a VRS DFP Direct Drive wheelbase for sim racing, but have spent the majority of the last year using the rig for DCS... I think I can add some aluminum extrusion to the Wheelbase mount and clamp the MIP stuff to the extra extrusion. My HOTAS is currently side mounted and would have to cut out the center of the seat a bit. (i have the GT style seat with the surrounding headrests) The arm rest is the best additon ever to be honest
  8. audiman
    +1
  9. audiman
    One thing that was discussed is the potential of the GPU not having the required power. For reference, I have an Asus TUF Gaming OC RTX3080 and the Power Supply is a Corsair RM850. The GPU is given power via two separate 8-pin connectors/cables. I made sure to use two separate cables rather than the single cable with the extra 8-pin "splitter." Rest of the specs are in my signature for reference as well. Nothing super crazy
  10. audiman
    yes, when I set up the sim rig with the triples, I color calibrated all 3 monitors and made sure they all had identical settings with no power saving modes enabled. But that is a good thought.
  11. audiman
    Small update. I submitted a ticket. Troubleshooting still ongoing. It is not "fixed", per-say, but I think I have a workaround for now. To re-cap the ticket troubleshooting: I was asked to change the name of my Saved Games DCS folder to "Backup". Then to verify the integrity of the files (I'm on Steam). This created a new Saved Games DCS folder with completely default settings. As in no mods at all like SRS, all key binds were reset to default (don't freak out, your key binds are still in the original folder now called "Backup" under an input folder), default graphic settings (for me that is going from triple screens to a single screen). Then I was told to launch the game and try to recreate the issue. I simply bound the throttles and the stick Axis' so I could fly around. I flew around for 10-15 minutes at night in the pitch black and could not recreate the issue. I then changed one graphic setting by going back to triple screens and tried flying again. Immediately began having the darkness bug where I couldn't see anything which was a bummer. So, for me at least, if I want to fly at night I need to change back to a single screen as a work around. Granted, I didn't spend a ton of time flying in single screen to see if it still happened after extended periods of time, but changing back to triples makes the issue occur within a minute or two. So it seems like Single screen is more advantageous at night for me. Not the end of the world, just slightly less immersive. Also, several of my buddies who have experienced the same issue I'm describing play on single screens or in VR. So I have asked them to submit tickets with track files and log files for additional data as well. My ticket Rep has also asked if my friends have submitted tickets. Hoping to provide as much data as possible. Thanks again for all the input I've received on this post.
  12. audiman
    here is a track file. towards the end of the flight the screen went very dark and stayed that way for me. pitch black f18 darkness bug.trk
  13. audiman
    well damn...I assumed all tracks were saved automatically. I'll figure this stuff out eventually. thanks for the clarification. I'll try and get another track and post it, possibly this afternoon. Will be out of town this weekend starting tomorrow though.
  14. audiman
    Alright, so here is a short video I chopped together really quick. I took the track file that Flappie gave me and edited it to put me in an F-18C where I spend most of my time, and therefore notice it the most. I flew around for about 9 minutes and shortened the video to the most obvious clips of it occurring. Posted it on YouTube for troubleshooting purposes. For some reason I can't find MY track file for this flight though. Makes me feel dumb. but hopefully this is a better example for everyone. And before anyone says anything about it being G-lock, it is not. I just happened to be yanking and banking on a few of the examples because I was just flying around waiting for it to happen enough times. it happened at the start of the video when I was on Downwind for a practice landing, too close to the airfield but I digress... Thank you all for your comments so far
  15. audiman
    Ah, true, I'll do that.
  16. audiman
    So, I finally tried this last night. I flew around for about 5 minutes and had one brief instance of the whole screen dimming again. but it took a few minutes of flying and trying different things to trigger it, which is frustrating because it seems so random. I can try and upload the track file this afternoon when I get home to see if anyone else sees it, assuming the track file is not too large. Essentially, I flew around for few minutes just fine, then tried different maneuvers to change the perspective of the ground lights from the city compared to the dark sky. last thing I did was a full loop, and towards the end of it as I was pulling up from the ground and could see the city lights, the whole screen went dim for just a second and came back. then I crashed into the ground because I have never flown the SU-25T, don't know how it flies, and I was just having fun with it. Plus, wife was getting home and I was hopping off for the night. What settings did you have to make it so dark? I was unable to recreate this in my own mission, though I did not change the time of year, only the time of day and weather conditions. Thanks so much for providing that track file for my testing though!
  17. audiman
    Sorry for such a late reply, had some personal matters take up my time during the last month. I'll try this out this week hopefully Thanks!
  18. audiman
    So how do you set the weather/lighting in a private mission to be absolutely pitch black with no moon light? I tried to make a dedicated mission to reproduce this issue, but I can't make the weather/sky dark enough regardless of the cloud layer or time of night I select. I must be missing a setting somewhere. It's most noticeable for me when I fly GAW at night, but when there is a VERY thick cloud layer at multiple altitudes, so no Moon light is visible. I can't seem to recreate this in a private mission.
  19. audiman
    Well unfortunately it happened several times again yesterday evening while flying at night on Hoggits GAW. It was exceptionally dark with no moonlight and some heavy cloud cover. So the contrast between the cockpit instrument lights and the exterior of the jet was pretty extreme. After I deleted the contents of the FXO and metashaders2 folders previously, I flew for hours at night on several different days I thought for sure it was fixed. But it wasn't as dark as it was last night on GAW. I flew around for a bit, shot down some planes, and then logged off and exited DCS. I deleted the contents of the FXO and metashaders2 folders again. Launched the game again and hopped back into GAW at night, launched off the carrier and still had the random blindness/dimming of the game. I want to note that I'm running triple monitors on my Sim Racing Rig that now doubles as a flight sim rig. Still using Track IR. But I had the thought yesterday that while the center screen is normally the cockpit/HUD view two peripheral screens on each side are essentially seeing complete darkness. So I wonder if DCS just doesn't know how to handle such severe contrast between the center monitor/cockpit instrument lights and the peripheral monitors seeing complete darkness. The issue seems to be independent of where I'm looking with track IR. I can already be heads down looking at the Radar and the screen goes very dim. I can look outside with NVG's and the screen goes very dim. I unfortunately removed the "mark as solution" from the shaders folders suggestion for now. Here are some pictures from a few months ago of what my setup looks like. Unfortunately don't have any similar pics of night flight, but I'll try to remedy that next time I fly at night. But just picture the side monitors being pitch black and the center monitor full of instrument lights. Just makes me wonder if I tried running it on just the single center screen if I'd still have the issue? Just thinking out loud, it might not even make sense
  20. audiman
    I'm going to call this one FIXED. After deleting the contents of the FXO folder and Metashaders2 folder, I've been able to fly at night for hours without any lighting/contrast issues. Thanks for all of the questions to double check that I didn't miss anything simple and for all of the recommendations!
  21. audiman
    The problem MIGHT be fixed... So, I deleted the Shader files as described in the screenshot, and I flew PGAW at night for about an hour without issue. However I want to test a bunch more before saying this was causing my issue for sure.
  22. audiman
    ah all good. all good, no stupid questions here. no, I clear assigned key binds when I assign new buttons and Axis binds, I do not have any binds for lights. If you see the pictures and video, it's not simply instrument lights specifically going dim (I mean they are...but) it's more of a global illumination issue within the game. because I can have NVG's on and look at the moon and the whole screen still gets very dark. But yes, I have G-forces enabled, but this happens when I'm simply cruising around navigating. not when I'm pulling higher G's
  23. audiman
    interesting. I'm assuming that is meant for the stand alone version of DCS? I have the Steam version, and don't see anything that indicates steam compatibility.
  24. audiman
    Ah, well damn. That's interesting. I was wondering if it would show up for anyone else via the track file or not. Well I really appreciate you taking the time to look into it! Thanks for the effort! I'll research the shaders and try that, it'll be a couple days before I can do it but I'll give it a go. Thanks for your input.
  25. audiman
    Ok here is a track file, i just hopped on PGAW at night and flew around for a few minutes until it happened. didn't happen as frequently but it did happen several times towards the middle and end of the flight. Persian Gulf At War 1.0.0_evening-20230824-192905.trk
×
×
  • Create New...