DP Spaz

Thanks!.. that resolved it. Either my memory is awful, or the latest updated reset that option... or both... its working fine now.

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.

Release notes identify "Added Airfield Aeropuerto de Santa Cruz"... flew over the area, no airfield... you can see where it should be

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.

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

@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.

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

Mine as well... lots more tweaking to do! Thanks to you as well!

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.

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

@Bailey and Toni, I am experiencing the same thing, about every 20 seconds I get a significant hesitation, framerates drop to about 1/2 to almost zero then returns back to normal. As Toni mentions, it acts like a slideshow. My other missions have no issues until I put an Apache in it, then I experience the exact same thing... other aircraft do not have this issue. I've tried various driver versions, did a complete uninstall and reinstall twice with removing the saved games directory, the issue remains. I am working on the 3rd uninstall/reinstall this morning. Two other observations... when I set TADS video on the MFD, the sim literally stops for about 3-5 seconds. And when I'm only sitting idling on the ground hot and just watch the framerate, every time the hesitation/pause occurs and my framerates drop, the main rotor shadow on the ground reverses direction... CW to CCW then back to CW and so forth. My other flightsim IL-2, XP11 and MSFS have any issues... silky smooth across the board. I will try the Witching Utility if the 3rd reinstall doesn't resolve the issue. Appreciate any assistance with this issue! Thanks! Spaz System Configuration: AMD Ryzen 5 5600X 3.7 GHz 6-Core Processor Asus ROG STRIX B550-F GAMING (WI-FI) ATX AM4 Motherboard Team T-Force Delta RGB 32 GB (2 x 16 GB) DDR4-3600 CL18 Memory Samsung 980 Pro 1 TB M.2-2280 NVME Solid State Drive XFX Radeon RX 580 8 GB GTS Video Card Antec DF700 Flux ATX Mid Tower Case Corsair RMx (2021) 750 W 80+ Gold Certified Fully Modular ATX Power Supply Microsoft Windows 10 Pro OEM 64-bit

Too bad the Spruance mod doesn't work, The USS Kidd works for me with the latest openbeta. The only item I found is, when you land on the helo deck, you sink below until the fuselage bottom touches the deck. The rails are not damaged, you can takeoff again and visually verify they are fine.

Hi Flappie, I realized that I had the C130 mod installed this morning, so I uninstalled that mod, and the game started just fine. One thing I did notice is, Steam application updated first, so maybe they released an updated to fix that. Very strange that it worked fine about an hour before last night... then it didn't. I did uninstall the C130 Hercules mod before attempting to start this morning. I've since gone back and reinstalled that mod, everything is back to normal. OvGME is a blessing in this case Thanks so much... your response and assistance greatly appreciated!!! Spaz

Today I was playing DCS-Steam without issue, this evening it wont start, nothing changed since I ran it earlier. Here is the entire log file (very short) and screen capture of what I'm getting... anyone seen this and know how to correct it? === Log opened UTC 2021-10-08 04:05:39 2021-10-08 04:05:39.855 ALERT SECURITYCONTROL: Can't run Steam! 2021-10-08 04:05:39.858 INFO DCS: Command line: "G:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe" 2021-10-08 04:05:39.858 INFO DCS: DCS/2.7.6.13436 (x86_64; Windows NT 10.0.19043) 2021-10-08 04:05:39.858 INFO DCS: DCS revision: 193433 2021-10-08 04:05:39.858 INFO DCS: Renderer revision: 22322 2021-10-08 04:05:39.858 INFO DCS: Terrain revision: 22345 2021-10-08 04:05:39.858 INFO DCS: Build number: 662 2021-10-08 04:05:39.859 INFO DCS: CPU cores: 4, threads: 8, System RAM: 32664 MB, Pagefile: 2048 MB === Log closed.

ICLS is not implemented in the T-45... and my understanding is its not part of the real aircraft. Its a day CQ training aircraft only very similar to the T-2C, not designed for advanced CQ training.

Im running 2.7.3 without issue. I'm running CAM and MAM without issue as well. Are you seeing the T45 icon along the bottom of the main DCS screen? Directory structure where the mod is placed is the only time I've seen this issue. Hopefully DCS validation will find the problem.

What exactly is it doing? Any specifics that you can provide will help better understand the issue. What version of DCS are you running? Here are a couple things to immediately try: 1. Delete the mod in your .../users/<username>/Saved Games/<DCS Folder>/Mods/Aircraft, should be the "VNAO_T45" directory and do a fresh install 2. Do a local file verification if Steam or its equivalent for the standalone version. Send a follow-up and lets us know what happened.

I purchased this mod yesterday for doing some fun flying and recon the different regions for creating mission. When I placed it in one of my training missions, only the naked livery shows up. I did Steam validation, it checked ok. I found one forum thread on this issue, they were using a skin blocker which I don't know what this is, that caused the liveries not to show up I also noticed that the control stick movement is not smooth, rather it moves in increments in the direction you apply movement. Is that they way stick movement is implemented? Appreciate any help with these 2 issues!

I set trim at 5 when taking off from the boat, that seems to be right in the sweet spot. Likewise, in response to the other questions, boat traps with full flaps and speedbrakes out, its right around 5 depending on my grossweight which will change that slightly... trim to center in the "E" bracket. Field takeoffs I set at 3 degrees and that works well. I suppose I need to research and see if I can find some real numbers

I never flew the T-45, that came after me... for sure those weights will be in the NATOPS. I did find a indiafoxtecho T45 manual for MSFS, I dont know the accuracy of the information contained in it, but it does have a weight chart which I've attached. I have not done an internet search to try and verify.

Great you are back in the groove! On-speed AOA is key to making consistent traps! This sets the the hook at the best angle to catch a wire. And holding that all the way down to the deck, this is where you can loose that very quickly and result in bolters or waveoffs. This is extremely important! The fewer changes in close the higher probability you will catch a wire, provided you are in the groove. Get set early on downwind, and be on the numbers thru the downwind-to-final turn, and as you rollout on final... only minor corrections to maintain in the groove. Picking the right spot on the deck to assess your approach as you get closer is also key, as it helps with over-correcting rather than chasing the ball or the ICLS needles if the aircraft is equipped. Remember that on-speed AOA changes with gross weight, and the aircraft will definitely handle differently. I always check my gross weight before entering my approach, gives a heads-up on how things will go in the pattern.

I fly the T-45 regularly and have done many traps, not had any issues catching a wire. There has been an occasional bolter, very infrequent and would contribute that to my approach rather than an issue with the mod. There should not be any difference between aircraft with the IFLOLs, and have not noticed any in the aircraft I flown. I will say that I've observed at times the IFLOLs does not seem to match where I touchdown on deck, similar to what you are saying, this has been in the Hornet. It does not occur frequent enough for me to start really looking at this in detail.

Yeah, had I opened my eyes a bit wider, maybe I would have seen it. I really appreciate your help!!! I've worked some with this mission editor, not nearly like I have with IL-2, which I'm very comfortable with and have created some very kool missions! I'll keep working with this mission editor, and I'm slowly learning MIST... as I use the script ciribob created for my range practice. I would love to add smoke markers to the bomb hits... MOOSE is the only way I know that's been done... well out of reach for me right now lol. I've updated that specific mission with this change, and also pulled in the trailing Burke in to 1.5nm from the carrier. I saw a few downloads of the file, so maybe other may be interested in it. I've also attached my evening field carrier landing practice mission (FCLP) that makes use of the Navy Equipment mod which is really awesome! I sure wish the portable IFLOLS was working, thrilled that they got the lighting fixed as I've been using this to practice my low light approaches. I am very regimented, and use this often to prepare for going to the boat! Guess thats the Naval Aviator in me When VNAO release the T-45, that was a huge gap filler in Naval Aviation Flight Training. If we can get the protable IFLOLS working, then we are about complete. I did notice that when you change tail numbers on the T-45 with the VX-23 skin, the tail number does not change in the game. Not sure if that was coded in or something missed. Thanks again!!! Spaz Causacaus CVN71 CQ.miz Spaz PG Eve Tunb Kochak FCLP.miz

Ah... something simple yet elusive... thank you very much! Makes sense now as the Burke behind is that distance. Appreciate your help and identifying the problem. I knew it had to be something simple. This particular mission I mod'd from my friend specifically to practice CQs... the other mission its working I created from scratch. Good to know this little detail... save headaches down the road!!! Again thank you very much!!!

I have looked at this mission, no success identifying the cause of the TACAN error. This mission was created before the release of the T-45 and was added to it after its release. As mentioned, I have another mission, the TACAN reports correctly. Maybe you can identify the cause. Thanks! Spaz Causacaus CVN71 CQs.miz