Jump to content

Mordant

Members
  • Posts

    77
  • Joined

  • Last visited

About Mordant

  • Birthday May 18

Personal Information

  • Flight Simulators
    DCS World, Flight Gear Flight Simulator
  • Location
    United States
  • Interests
    Aircraft, Drones, Technology
  • Occupation
    Student

Recent Profile Visitors

1198 profile views
  1. Apologies, completely forgot. Here are the logs: dcs.log-20230416-043515.zipdcs.log And the dxdiag: DxDiag.txt I will update the OG post with these as well
  2. This issue has made my game unplayable. I will start off with what’s happening, my specs, and finally what I’ve tried to do to fix it. Heres the simple rundown: At completely random times while playing DCS, all 4 of my monitors will go black and flicker for 5-7 seconds. When they return, all of my applications except DCS are effed(technically alive in the sense that they work, but have no visuals) and often DCS is frozen but not dead. Around 75% of the time, after having its fit, DCS will have a permanent black bar at the top. The whole thing is so unbelievably frustrating as I have no idea what’s causing it, but I will get to what I tried later. Edit: Important to note that DCS does not last long after this fit occurs. Often crashes within a minute or two. I have gotten various errors from SRS and other programs as well as this happens but I have not been able to remember or understand their contents My specs are a water cooled Ryzen 7 5800X, 32gb (4x8gb) 3200mhz ram, RTX 3060Ti, a 16gb(?) page file, and like 5 different drives with anything from it being a 7 year old hard drive to a 1tb NVMe ssd. DCS is on the NVMe. I have DDU’ed my graphics card to ensure that isn’t the issue, I have done microsoft’s memory tests as well as their drive checker(on all my drives) which all have come back with no corruption or issues. Running FurMark with all other variables equal is uneventful(I tested it at 1440p 8x MSAA for 4+ hours and never had a flicker. Sat in my chair for 4 hours doing nothing but monitoring it and scrolling on my phone). The GPU, CPU, RAM, and drives are working optimally at face value. I even cleaned out all the dust. I reseated RAM. Reseated my GPU. Only thing I haven’t looked too hard into is the CPU, but I haven’t had any issues with it. This issue has been going on for ~6 months now and I’ve tried to keep it off the forums because my ego wouldn’t let me. Plus I wanted to see if MT would make things better, and unfortunately it did not improve this issue. Literally any help or advice is a blessing, any new lead or possibility is helpful. I’m at a complete loss. This video is the most recent one, I was on Rotorheads in an A-10(shh) in Syria. MT made my performance awesome until I was in cruise and this fit struck. I whipped out my phone and recorded it. For reference, left screen had SRS and discord. Right had spotify. Important to note that spotify was still pumping music, even while the app looked like it was euthanized. Center low had task manager, and center high(or main) had dcs. It’s a pretty shoddy video, but it should give some context to how weird this is… DCS graphics issue: https://youtu.be/swLWPu8rZTY Edit: LOGS dcs.log-20230416-043515.zipdcs.log and DXDIAG DxDiag.txt
  3. Identical issue, happened over 5 times, with 3 leading to an eventual total electrical system failure. No combat damage was ever taken. Always max of 0.95M (Typical of 0.85M) and max altitude of 32K(averaging 20-ish). ALT2 goes, then at an undetermined time afterwards it sometimes then has the entire electrical system(including ALT1, air data, CAP warning, etc.). After total electrical failure it seems my right tanks start losing pressure/leaking. This is a screenshot 3-5 minutes after the second electrical event(note the fuel gauges and the warning panel): Very soon after this screenshot, the NIV(low feeder tank fuel warning, <250 litres) lit up as the right tanks started drying up. Nothing cleared any warnings and I was forced to land. Because of this fuel leak, my engine often quit, thus making the situation worse. I have a clip on YouTube of after the ALT2 fail through the entire electrical failure and subsequent engine starvation and crash. I'll edit this post with the link as soon as it's done processing. Any thoughts, concerns, big things I'm missing? V/r, Mordant
  4. Hello all, this post was made on request from Alpha Juliet on the Razbam discord, I'll try to encompass everything I can to make this a good bug report. Thanks for the hard work Razbam! TL;DR The main 2 issues are that in the "HUD only view"(HOV, LAlt + F1) some MPCD pages are semi-transparent, with the second issue being the ODU, cipher/encrypted radios, and the main UFC displays including the 2 main radios. This happens in regardless of mission start parameters(Cold, hot, tracks even). This video shows the main problems and is the best visual representation I could make. I will go into more detail into both of these in two separate sections. Transparency Issue The first thing I noticed was that some pages are either fully transparent(EW page), semi-transparent(FLIR, EHSD), or opaque like they should be(TPOD). The fully transparent pages include the EW page, CAS page, STRS page, ENG page, CONF page, and the COMM page, and of course the menu/emer menu. A special page that sort of fits here is the HUD repeater page, which shows nothing when in HOV(probably because theres already the HUD in the view. All of these pages have the green lettering, text, symbols, etc but have completely transparent backgrounds that show the terrain/water in front of the aircraft. The semi-transparent pages include the FLIR page, the EHSD page, and the DMT. These have semi-transparent backgrounds in which the terrain/water makes viewing the video or in the case of the EHSD the moving map nearly impossible to read. Much like the fully transparent pages however, all of the text on these pages are fully readable and opaque. The fully opaque pages include solely the TPOD page. This is where the TPOD video can be seen clearly and fully blocks the background. This is how I think all of the pages should be in this mode, and I have no problems with it. If anything, it's the best page to have working ;D This video was from a track that I recorded and cropped and it highlights the issues with the EHSD primarily. The TPOD footage looks decent(it being opaque and all) but the EHSD moving map is unreadable. Overlay Issue There are 5 main sub-screens that get overlayed on the right MFCD in HOV. First of note being the two cipher/encrypted radio displays, the ODU, UFC, and the two main radio screens. The main cipher radio screen gets put above the right MPCD, so it's ok. But the second cipher screen is in the bottom left of the right MPCD, so it's not very cool. The next one I noticed was the two main radio LCDs were overlayed at the bottom, left radio in the bottom left and the right radio in the bottom right. The little "M"s were overlayed below the cipher text. The ODU gets the cheese for the worst offender(when it's active). It is nearly smack dab in the middle of the right MFCD with the bottom two buttons being overlayed below the cipher as well as intersecting with the two radio "M"s. Finally, the UFC screen is put near the top of the MFCD, an ok amount above the ODU. I haven't seen any other jet overlay their screens like this, even in something like the A-10CII. You would think they would include a third screen for the CDU in between the left and right MFDs but they just don't include it, so maybe just removing the ODU, ICP, Radios, and cipher is the play here. But hey I'm not the devs, you guys do whatcha want Summary While this isn't game breaking or disastrous to the world of Harrier pilots, I do think it's a shame as this is the easiest way to get a quick tape of you shacking some bad guys. The alternative, exporting the screens to another display is slightly more complicated and has it's own issues that have been well reported. Thanks a bunch Razbam and especially Alpha Juliet, love the community you guys are growing! V/r, Mordant
  5. I don't know many correct terms for it but heres what I know and can explain: Recently, I upgraded from a 60hz display to a 165hz display and I adjusted my display settings in Windows accordingly and it has been a wonderful upgrade. However, in DCS I have noticed a distinct color change or lag in adjustment when moving my head(I use TrackIR 5 with ProClip). It is not anything I have noticed before the change to the new monitor and I have not changed any in game settings. The artifacts only go away when I stop moving my head, and they resume when I move my head again. Moving the aircraft in game does not affect this, it is purely a head movement issue. All screenshots I have been able to gather have shown that in game there is no problem, which makes me think the game is not able to run up to 165hz(or at least thats proving to have some issues on my monitor). Average frame rate in DCS is around 110-120, however I did not think this would create artifacts if my monitor is at 165hz. Is there a certain setting I could change, or is this just a quirk of DCS? V/r, Mordant
  6. The user livery also explains the blue-striped AGM-88Cs... Is that tanker boom view an F4 view of the tanker? I've always wondered how to get in that position, and F4 is just really finnicky for me... Am I missing a dedicated camera mode?
  7. It appears to still be off the Steam Store. Unfortunate, was really hoping to grab it for the Gazelle
  8. We've waited a long time, but a couple more months is necessary. The Viper was all about hype, and they released it to keep the hype train instead of releasing and hyping it when it should've been released. This is exactly the opposite of what Polychop is doing, and they're a better company for it. Releasing the Kiowa Warrior in a release state instead of EA allows for literally the best experience out of the box. They aren't releasing any more screenshots because they don't want to hype it before they need to. Once you start to hear more from them, the more we will be able to expect a release. Both are highly wanted helos, have a similar but completely different mission, and both are going to be modeled to a high level of precision. We need to make it earn the title of "full-fidelity" and "Best combat flight simulation". All in due time... Smooth skies, Mordant
  9. Ah, that makes sense as to why everything seemed more normal. One last question: Are the virtual tracers for a training mode with the training pod thingy? Or is it an aim assist thing?
  10. I have warthog stick and rebound the trigger for stages 1 and 2 but I'm lost on whats different iirc I did a flight on the most recent open beta about a week ago, and when I wanted guns I switched like I would typically do before the update. Before the update, my trigger was second detent, first not doing any. I have now bound the first and second detents as the manual states, but I havent found any issues such as trying to fire the gun or fire 530s. I would select 530s and hold 2nd stage until they launched. I would select guns and hold second detent. How is it supposed to work? Whats the function? I've only briefly checked a dubious manual that isn't the official one but I'm not that into manuals and don't know where to find it. Ik this is a tiny bit off topic, but I've been confused as to whats changed and thought you guys may know
  11. well that makes me feel just a little more stupid, i thought they were city markers... ty
  12. You should be able to use it as a 2D model regardless of aircraft, but if you want the 3D model you will have to buy those. I bought the 3D model for the Hip and I haven't regretted it!
  13. I think this blends in similarly to a thread about overspeed damage. I feel a lot of these things need to be modeled better as they are not well modeled. One of the very big issues I think we will encounter is that recovering an aircraft with overspeed/over-g damage let alone certain parameters at the time of damage is very difficult. Plus I don't think the Air Force/Russia/Pakistan/etc would key ED into it anyway. It'd be difficult, although ED could maybe do it. I think it's pointless to argue over "How much further should the aircraft go after the pinned limit" as we don't know. If someone has evidence to the real number, come forward. Otherwise, I don't think its worth arguing or even politely debating. Heres the Overspeed thread: Smooth Skies, Mordant
×
×
  • Create New...