Jump to content

Majik

Members
  • Posts

    157
  • Joined

  • Last visited

Posts posted by Majik

  1. 23 hours ago, EFGross said:

    I was flying around in the F16 last night for the first time since the patch and all the pilot textures are showing the green, white and black checkerboard textures.  It's fine when I disable the optimized F16 textures (standalone, doesnt appear to be from the ones in the core mods.  Anyone know which files in the zip are for the pilot?null

    image.png

    You need to transfer over the pilot body files into the F-16 zip in Optimised Cockpits (The directory for both mod and original file is at the top of the image)

    null

    image.png

    • Like 1
  2. 12 minutes ago, Qcumber said:

    Much appreciated!

    Just to confirm, yours has 6e? As I understand, WiFi6 and 6e (6GHz) are not the same, but I may be wrong. Nevertheless, if it working fine for you, that's good enough for me, and certainly will be a step up.

  3. 8 hours ago, Qcumber said:

    Glad you are enjoying the QP. I have been having the same issue recently. It's happened about 3 times the last couple of days. Not sure why. It's not been an issue for me before. 

    I am maintaining 1200 Mbps, occasionally dropping lower. I think the minimum you can get away with is 860 Mbps. That might be part of your issue. I have a dedicated router next to my desk. 6e Mercusys from Amazon for £40. In terms of codecs, try using h264+ at about 200 Mbps. It has lower latency than HEVC 10 but and I can't notice any difference in DCS. 

    Which version of oculus software are you using and do you have the Public Test Channel enabled? I am using PTC v65. I might try unchecking the PTC to see if that stops my freezing. 

     

    Interesting, so might be new issue? I didn't setup my QP until after latest DCS patch, so have no data to compare to, either VD or DCS. I can't fully remember, but I think I was also getting crashes in Asseto Corsa and AMS2 as well in limited testing last week, so maybe it's more of a VD issue?

    I'm definitely not hitting 860 very often, mostly hover around 550-700 so I'll definitely need to look into the router and some new cat cables to replace the aging ones I have. Would you happen to have a link or model number for your router, all I could find at that price point was a PCIE WIFI card?

    Headset should be fully updated, so v65 I believe. Definitely don't have PTC enabled.

    2 hours ago, Qcumber said:

    What Nvidia driver version are you using? Just seen in the VD discord that there were issues with the last version. The one released last week solved these issues. I have just updated to the latest so will see if this has solved it. 

    Oh I'm on a very old driver, 536.23. Actually dowloaded 537.58 last night, which from reading seems like the last really, really stable one (I know we're up to 552 currently). Can certainly update to latest and give it a spin though.

    Appreciate all the help!

    Have also joined the VD discord, will have a look there too

    • Like 1
  4. Another new sub £500 sealed QPro user here, loving everything about it now that I have it all dialed in, including QVFR. Much, much higher clarity than my old Reverb G1, with even slightly higher fps on my aging 9700k, 2080super PC!

    I just have one problem; using VD, I fairly often get crashes in the headset, that 9 times out of 10 are unrecoverable with a VD restart in headset. The game in still running on pc, and will move with the headset, but the image is frozen in headset. I've read this can be VRAM issues, but nothing I've tried seems to alleviate this. I already run Taz's optimised texture mods, the background hanger removal mod, in-game textures are normally medium, but have tried low on both and I still get crashes. Godlike in VD gets me the best clarity and decent perf, but have also tried down to high with no luck. I can run fine sometimes for a couple hours with no issues, or get crashes loading into a server immediately. Can't find a rhyme or reason.

    Could it be my connection dropping? I'm usually running anywhere from 860 to 500mbps, on a 5GHz AC connection, 20ft from the router (in a different room, but direct line of sight through open door). PC is hard wired to the router, and has always been (cable is probably nearly 20 years old at this point). My latency is usually showing orange and jumps around but often near 60ms. Using auto codec, which defaults to HEVC 10bit, and 150mbps. I wonder if a dedicated 6e router would help this situation?

    Wired link gives me lower fps at a lower clarity compared to VD, so I'd like to avoid using that if possible.

    Anyone experienced similar, or have any advise?

  5. 21 hours ago, silverdevil said:

    try a mission without the F14 in it. including AI. i think there have been some problems with that plane recently. you can also rename your dcs folder in saved games to something as a backup. copy config folder to new dcs folder when it is recreated. starting dcs with make a fresh copy.

    The missions I've been getting most crashes on do have F-14 slots, but none spawned.  Does that make a difference?  Also, I've flown around in the Tomcat on busy Supercarrier decks with no issue.  My squadron's server does have a few static jets (Warthogs, Hornets, Vipers) placed around Nellis, and loading textures on one of these seem to causes crashes as I click to spawn into a jet.  When I do manage to get in, I get crashes as I apporach one of the ranges and objects/units there try to load in.  As you said, I have enough memory and pagefile, so it's a little baffling unless there is a memory leak or something.

    As for rebuilding saved games, I've done so twice already.  Got a nice performance boost, but no help on the crashes unfortunatly.

  6. 54 minutes ago, silverdevil said:

    even though you show plenty of RAM and pagefile, you are still getting an error about memory

    2022-06-09 20:51:50.067 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.067 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183
    2022-06-09 20:51:50.069 ERROR   DX11BACKEND: failed to create index buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.072 WARNING LOG: 1 duplicate message(s) skipped.
    2022-06-09 20:51:50.072 ERROR   DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.072 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
    2022-06-09 20:51:50.072 ERROR   DX11BACKEND: failed to create index buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.073 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.073 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183
    2022-06-09 20:51:50.073 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.073 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183
    2022-06-09 20:51:50.073 INFO    EDCORE: try to write dump information
    2022-06-09 20:51:50.074 ERROR   SOUND: can't alloc memory for 'effects\aircrafts\cockpits\markerouter': 440980 frames, 1 channel(s)
    2022-06-09 20:51:50.074 ERROR   DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY
    2022-06-09 20:51:50.074 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
    2022-06-09 20:51:50.074 INFO    EDCORE: try to write dump information
    2022-06-09 20:51:50.075 INFO    EDCORE: # -------------- 20220609-205150 --------------
    2022-06-09 20:51:50.075 INFO    EDCORE: DCS/2.7.14.24228 (x86_64; Windows NT 10.0.19044)
    2022-06-09 20:51:50.076 INFO    EDCORE: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
    2022-06-09 20:51:50.076 INFO    EDCORE: # -------------- 20220609-205150 --------------
    2022-06-09 20:51:50.076 INFO    EDCORE: DCS/2.7.14.24228 (x86_64; Windows NT 10.0.19044)
    2022-06-09 20:51:50.076 INFO    EDCORE: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
    2022-06-09 20:51:50.076 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 3FAD1989 00:00000000

    is your windows up to date? can you run dxdiag from run and post up the file?

    Windows is current, no pending updates.  I've attached dxdiag below

    DxDiag.txt

  7. For the past month, I'm getting constant CTD, usually on heavy MP missions, and seemingly for various reasons.  Limited memory/VRAM seems to come up regularly when it seelingly shouldn't.
    I've attached 4 logs below.  Often the log won't even show why the crash happened, and I've even had a blue screen happen once.

    Based on advice I've seen, the steps I've taken to alleviate issues, all to no avail:

    - Tried without mods

    - Lowered in-game settings (textures, clouds, preload radius)

    - Multiple slow repair and clean

    - Clear fxo and Metashader2 constantly

    - Reinstalled Nvida drivers (w/ DDU clean)

    - Removed GPU overclock

    - Run Nvidia debug mode

    - Rebuilt saved games folder twice

    - Moved pagefile from SSD to NVME

     

    I'm at a loss of what to do here

     

    dcs1.log dcs2.log dcs3.log dcs4.log

  8. From the mission linked description:
     

    Quote


    Designer notes.  Some artistic licencing is present in this collection of missions.  Most notably is the use of the F-16C as a stand in for the RNoAF F-16A.  In order to limit the C model capabilities, datalink, GPS, HMCS and AMRAAMs are not useable in these missions.

     

    I haven't played Nightly Silence, but as Sinclair_76 says above, and judging by the name,  if NVGs are installed, then HMCS will not be (it's an either-or case, and can be switched by talking to crew chief on the ground)

  9. Hey Home Fries,

    I'm getting the server not available error when trying to update.  Being from Europe, I remember a similar issue last or earlier this year that was solved for me by changing DNS to Google's servers. 

    I have been trying a few times a week at all sorts of hours, for the past couple months with no luck, as I've seen in this thread that the server may be down when you've been away.  (I'm still on 2.570)

    Any thoughts on how I might solve this?

  10. 2 hours ago, Gunfreak said:

     

    But I want the plane to realise countermeasures by itself when I'm on a bombing run. So as you approach a steerpoint or target the plane releases countermeasures. 

    This is something that can be dome in the F18 from what I understand.  But I haven't found anyway of doing it in an F16.

     

    Sounds like you're talking about the auto and semi modes, which release countermeasures with consent (enabled and disabled via CMS switch), based on current detected threat.  Not currently implemented, but are on the roadmap.

     

    In semi mode, when a threat is detected, the VMU will promt you with "counter", and you can CMS aft to dispense the program once.  In auto, you press CMS aft to enable, and the system will dispense the program as many times as needed, when needed, until the threat is gone.  CMS right disables auto dispense, but you'll still get the "counter" VMU warning.

     

    To my knowledge, steerpoints don't play into this (unless somehow planned into the DTC I guess?)

     

  11. 13 hours ago, Iceman555 said:

    Oh, so I have to memorize the channel programming if I want to flip through channels, or just look at the srs overlay.

     

    Unless playing a mission with preset frequencies programmed, it's usual to just punch in the freqency required on the COM 1 or 2 pages and they'll show up on the CNI page.

     

    Personally, when using presets, I also change them using the COM 1/2 pages as well instead of faffing with the dobber on the CNI page.  e.g:  COM 1 > 4 > Enter    done.

  12. You've posted the instructions on how to do exactly what you're looking to do...

     

    That CNI page on the DED is the "default page", and all you have to do is press Return on the dobber, no matter what other page you're on, to get back to it.

    • Like 1
  13. 43 minutes ago, Bunny Clark said:

    Interestingly, the F-35 is limited to a slower speed than either by its DSIs yet has a canopy bow. I'm not sure why that choice was necessary, without a HUD that would have been a hell of a view with an unobstructed canopy. 

     

    I imagine it's for added strength in case of a bird strike.  I know Japanese F-2s replaced the F-16's bubble canopy with a two-piece as they're used in a naval role, where I think bird strikes are more of a concern.  If it is the case with the 35, then it'll be another reason the B and C model commonality hold back the A

  14. 10 hours ago, KL0083 said:


    No related to start,but the aircraft was this "cold" when start mission from runway or parking-hot slot.

    And yes,I did purposely set the battery switch to autopilot mod switch on the Cougar and lefted it "ON" position for cure this rumor, and it's ever automatically press back to OFF when mission restart as seen on video.
     

     

     

    Look like it could be a binding issue?  In your video, you've got two seperate sets of buttons bound to Main Power (22/23 and 27/28), which look like they might be interfering with each other.   I'm not sure how you've set it up though, and I'm no bindings expert, so could be wrong.

     

    Try each of the following and see if it helps:

     

    - Remove one set of bindings (22/33 OR 27/28)

    - Remove all Main Pwr bindings

    - Run a DCS repair

     

    I've had a few odd issues like this clear up with a repair

    • Thanks 1
  15. 36 minutes ago, KL0083 said:


    No,not MP

    As mentioned before: online or offline!

    I've tested many times,just open the take-off quick mission,that's dark and cold the same!

     

    Tried a few hot start instant action missions just now, and everything works fine here.  Do you perhaps have the Elec Power switch mapped somewhere on your hotas, and it's left in the off postion?   Might be worth running a repair if not.

     

    Also, to get rid of the ELEC SYS caution on the panel, hit the Caution Reset button on the ELEC panel in your first picture.

     

    • Like 1
  16. 1 hour ago, Falconeer said:

    See Northstar's post. He explains it very well.

     

    The original design was a light weight fighter jet. It envolved to a multirole plane, by all the upgrades it received. The Danish F16's were not the first F16's build, they are Block 15's. First production model was the Block 1 with a black radome.

    Which meant they already received updates to a new standard. The F16 became "multirole" with the Block 15 upgrade in which they received a new radar and increased capacity for underwing hardpoints (to use AG weapons for example)

     

    So the Danish bought aircraft that had already have some AG capability. This was further enhanced with the Operational Capability Upgrade (OCU) and later the Mid Life Update (MLU), which brought them to the same standard as USAF Block 50/52's.

     

    The EPAF (European Participating Air Forces) F16's were in the first place intended to replace the F-104 Starfighter and the Danish F16's were also build by SABCA Belgium 

     

    Denmark received Block 1s, as well as 5s, 10s and 15s later. 

     

    US F-16s were entered into, and won, the Tactical Bombing Competition, Lossiemouth, in 1981.  The production F-16 Block 1 was not the YF-16, and was always A/G capable (to the lament of those who came up with the original design).  Block 15 added the intake hardpoints (5L/R), not underwing.

     

    Back on topic, SDBs would have been great.  But understandable why we won't be getting them.

     

    Edit: Also, the Israelis proved the A/G capabilties in combat, also in 1981, with Operation Opera/Babylon

    • Like 3
×
×
  • Create New...