Jump to content

DP Spaz

Members
  • Posts

    55
  • Joined

  • Last visited

Everything posted by DP Spaz

  1. I confirm as well the canopy toggle keybind only opens the canopy, you have to manually close it with the mouse.
  2. Updated to the latest openbeta update, after loading the first single mission, jumped in F-14B parked hot, the wings automatically sweep forward, one at a time, not together... interesting. The handle position indicator showed full forward despite the handle being full aft, the wing position did not, but did move forward as the wings individually swept forward. Switched roles to a different location parked hot, wingsweep did the exact same. I'm thinking that the updated changed the wingsweep position when parked hot, not sure why it was moving the wings individually. No specific indication or warning, that behavior stopped and now the wingsweep remains full aft (parked) when selecting a role parked hot. The wingsweep handle still indicates full forward with the handle full aft. Have no idea why the wings swept forward, and no idea why it stopped, unfortunately did not have a recording that I could attach to this report. Asus ROG STRIX B550-F WIFI Motherboard AMD Ryzen 5 5600x CPU TEAMGROUP T-Force Delta 32GB DDR4 Samsung 980 Pro 1 TB M.2 SSD PowerColor RX 7600 XT 12GB RedDevil GPU Corsair RMx 750W 80+ Power Supply Windows 11 Pro 22H2 SAMSUNG Odyssey G7 Series 27-Inch Gaming Monitor
  3. Ahh ha!.. that did it! I really dont understand it because Rwy 32 works with zero wind as does the other ILS signals I've tired on that map. Why Rwy 14 is different, don't have any idea. Thank you @Minsky appreciate working through this with me.
  4. Interesting... I flew the F-16 and you will see the ILS is not active. However, when I switch to Rwy 32, it immediately goes active despite on Rwy 14 final. I did a repair to make sure my files are not corrupted. I tried 0 kts, 5 kts & 10 kts wind directly down the runway... the ILS is not active. If I modify the beacons.lua file to add ICLS channels, ICLS for Rwy 14 works perfectly. Makes no sense... Appreciate sending the .trk files, have no idea why it doesn't work on my system. 230703_NE_F16C_FCLP_001.trk
  5. Thanks @Flappie for the feedback, I read about that in some of the other posts I've found, this does not have an affect from the testing I've done. Runway 32 always works, I can't get 14 to work at all, regardless of no wind, little wind or lots of wind. @Minsky replied to my original post that was accidentally deleted by me, had a 10knt wind down the runway and some screenshots showing it was working... my test screenshots are shown above under the same conditions, showing runway 14 not functioning. I'm stumped!
  6. @Minsky I accidently deleted the thread... I loaded the A-10C II and still not able to get the ILS to function. I did a DCS Repair and still isn't working. I'm at a loss since yours is working. ILS does function properly in the opposite direction.
  7. Helo pad covered partially by helo pad
  8. I added the custom_args and that resolved the issue. Maybe that is something I should have had in my description.lua file all along lol. Thankful its an easy fix
  9. I looked at the forum, didn't locate specifically what I want to address. A while back, the wing sweep was changed that affected the wing sweep position based on the starting location. Prior to this change, the logic was more appropriate that what we have now. We've seen several patches since this change, no further changes have been made that I've caught. If "takeoff from ground" or "takeoff from parking", would expect the wing sweep to be aft. If the takeoff position is "takeoff from runway" or any "hot" position, makes sense that the wings should already be forward. 1. I'm still seeing the wings swept back when "takeoff from runway" Is this area being reviewed for update/changes?
  10. I'm seeing an issue with the latest release where the cockpit textures are not being displayed. I've checked F14, FA18C, F16C, P51, Spitfire and Huey. Some 3rd party mods are ok... the OV10A, T45C and MirageF1 display correctly. I checked using a default skin, same issue. Update: I just ran the repair tool and that fixed the texture problem. Maybe when I updated it corrupted the files?
  11. I've had this issue before where the P-51D keybinds don't load. Exit DCS and restart, they usually load. I found the cause & solution a while back, can't seem to locate that. Searched thru the P51D forum, did not find the exact issue I'm seeing. Appreciate any help with this issue.
  12. Anyone able to get a DME reading using a VOR/DME station? I've tried 2 maps, Nevada & South Atlantic, the DME shows offline. I get heading information, no distance. If I switch to a TACAN station, heading n distance working fine.
  13. Updated to version 2.8.0.32937 yesterday, mission load times on my system have degraded further. Finishing a mission and moving to another mission on another map also observing increased load times relative to the previous update. Asus ROG STRIX B550-F WIFI Motherboard AMD Ryzen 5 5600x CPU TEAMGROUP T-Force Delta 32GB DDR4 Samsung 980 PRo 1 TB M.2 SSD PowerColor RX 6700 XT 12GB Hellhound GPU Corsair RMx 750W 80+ Power Supply Windows 11 Pro 22H2 SAMSUNG Odyssey G7 Series 27-Inch Gaming Monitor
  14. I'm also experiencing very long texture load times with the current beta. I also noticed roughly a 5-10 fps performance hit across the board... which equates to roughly 10% on my system. Asus ROG STRIX B550-F WIFI Motherboard AMD Ryzen 5 5600x CPU TEAMGROUP T-Force Delta 32GB DDR4 Samsung 980 PRo 1 TB M.2 SSD PowerColor RX 6700 XT 12GB Hellhound GPU Corsair RMx 750W 80+ Power Supply Windows 11 Pro 22H2 SAMSUNG Odyssey G7 Series 27-Inch Gaming Monitor
  15. Does anyone have a copy of the static IFOLS with the working meatball? I am interested in looking into that specific equipment and attempt to get it functioning. Appreciate if anyone knows a means to obtain that.
  16. Thanks!.. that resolved it. Either my memory is awful, or the latest updated reset that option... or both... its working fine now.
  17. Identified yesterday the "Weapon Selector Up" & "Weapon Selector Down" no longer will select Phoenix missiles. I've used these keybinds since I got the Tomcat without issue. The only way to select the Phoenix now is using "Weapon Selector Sparrow and Phoenix Missiles" keybind.
  18. Release notes identify "Added Airfield Aeropuerto de Santa Cruz"... flew over the area, no airfield... you can see where it should be
  19. I'm using a TM T16000 Throttle, finally figured out the settings to make throttle response more usable. The afterburner kicks in exactly at my detent @75%. I have the slider modification installed that adds slide bearings and magnets to provide an afterburner detent, its not a stock configured TM16000 Throttle. Saturation X is set to 95 as the modification results in some loss of travel, this ensures you get 0%/100% at both extremes. I just figured it out, will do some flying with this setting and tweak as necessary. I'll post an update if there are any significant changes.
  20. I am posting to this thread as it talks about the USS Truman. I just purchased Viacom Pro and having difficulty with Super Carrier interface. As an example, "Truman" nor "Lone Warrior" does not show up in the profile. I've scanned thru the Real ATC Extension list, many of the recipients does not show up. Searching the forums has not resulted in a clear solution to this. Another issue I've seen is when I call the "ball", the LSO responds with wind over the deck, no further reports are received from the LSO. After I trap, I get no proper communications. Flying the Hornet module in these tests. Appreciate any help/assistance with this. --- I figured out that I needed to update my profile in VA... that resolved the issue. Please disregard my request. Thanks! Spaz
  21. @Hammer1-1 I am having the same issues with multiple aircraft, took me a while to realize what was happening. Start DCS, enter a mission the keybinds may or may not be there. If they are not, go into settings and that confirms they are not assigned. A DCS shutdown and restart is required, then they will reappear. I've made the mistake several times to re-set them up. Finally looking at the date/time stamp of the keybind files confirms they were saved, they are just not loading on occasion.
  22. Here are my current system settings... no framerate issues at all. Lesson learned... very early access, be sure to reduce system settings if you observe framerate issues
  23. Mine as well... lots more tweaking to do! Thanks to you as well!
  24. Hey @Toni Carrera I also am seeing a huge framerate hit of ~10fps when displaying video from the Pilot Seat... have not sat in the CPG seat yet. SSAA I have off, MSAA at 2x. My visibility is set at 150000 right now, only because I just reinstalled DCS. When displaying video in the Hornet, no issues... only the Apache. Since its pre-release, expect they will improve and optimize all that as development continues. And my GPU is a bit old, waiting for the chaos to end to upgrade! Still experimenting as well and will be tweaking the settings more to accommodate the Apache. I'll post updates as I continue to mess with my system settings.
  25. I believe identified the cause of this issue, at least on my system. Successfully created, eliminate and recreated the pauses with the Apache. It is tied to Textures and Terrain Textures settings in the Settings/System tab off the main startup screen. When I reinstalled DCS, both those setting were set to Low. My previous settings were Med and High respectively, had no issues prior to the Apache release. Flying the Apache in a mission, there were no hesitations/pauses and zero delay loading the TADS video to the MFD. When set to High, the hesitations/pauses occur regularly every ~20 seconds, as well as the game freezes for 3-5 seconds when displaying TADS video. Change both setting back to Low, the hesitations/pauses and the TADS video freezing the game for 3-5 seconds eliminated. Setting Textures to High and Terrain Textures to Low, the hesitations/pauses still occur as well as the TADS video delay, much less pronounced. Note: I do not see this issue with any other aircraft, including the F/A-18C included which has similar display capabilities to the Apache. Toni, give that a try on your system and see if you have similar results. Spaz
×
×
  • Create New...