Daemoc

Aye, the reason for the FARP is so I can dictate where it lands. If I don't use the FARP it just decides to land wherever. It used to work before, I wonder what has changed? Again, it's not that big of a deal. I can work around it. Thanks for confirming and reporting though. Much appreciated.

I forgot how stable the C-101 was as a ground attack platform. I just did a quick ground attack mission today and even without using it for a long while, it was like using easy mode.

Sometimes things take a while to get used to. I know everyone says it's one of the easiest modules to learn, and for the basics that is probably true, but it takes a while to learn how to fly it well. If you really are interested in flying it, just take your time and get used to the quirks. If not, there is nothing wrong with being disappointed with the F-5. Maybe it's not your jam? Nothing wrong with that. As you noted, it's not very forgiving. At higher speed it's twitchy. At lower speeds and high AoA rudder is essential. It has a high approach speed. And while it has the potential to carry a metric *** ton of ordinance, it's a brick when fully loaded. Personally, I love the f-5. If you look at comparable modules like the MiG-21, I find the F-5 to be the best of the bunch. She is not perfect, but if you learn to treat her right she will show you a good time.

Just checking in, did the attached .trk result in a crash on take off on your end? Not that this is an emergency or game breaking, just curious.

The sound file I ended up using was this one pictured here in the attachment. Just copy the AV8B sound file shown to your C101 sound directory and rename it "TFE731_growl.wav". You can rename the original growl sound to something like Growl_O so you can undo it later if you wish.

Got it, it is the wind that is causing the crash. If I remove the wind it does take off. But this map has had wind for a LONG time. I have been working on this particular map on and off for almost a year. The new "wobbly" ch47 take off is new. I am not sure which update it was, but it never wobbled that bad before now. The wobble + the wind causes it to crash. I have videos on my youtube channel demonstrating both instances if you need to see before and after. ch47.trk

I have been having this weird issue with the CH-47 AI crashing on take off. I have a few custom missions with a few CH-47's and after the last update, I noticed they keep crashing on take off. It's as though the rear rotor is not creating any lift and they just nose up and back flip instantly. I know I am supposed to attach a replay track, but I am not in front of my DCS machine at the moment. I was just wondering if I am the only one experiencing this issue. I will get a replay track when I get a chance.

I have both and like both. A very simple boiled down version of my experience would be the L-39 is a little more nimble and the C-101 is a little more stable. Both have very little combat utility outside of light strike. (Maybe recon or FAC-A if the mission allows? The loiter time of a C-101 is quite impressive.) Both are fun to fly though IMO. The only real negative I would place on the L-39 is the training missions being in Russian. As a non-native speaker it makes learning the aircraft that much harder trying to observe/manipulate the aircraft and read subtitles at the same time. Edit: I almost forgot, the negative I would give the C-101 is the Garrett/Honeywell TFE731 Growl. I get that is a real thing, but the noise it makes in the cockpit makes me want to poke out my eardrums. I replaced the growl sound file with one of the AV8B fan noises and it sounds similar without making my ears bleed. Just something to keep in mind. My vote would be get both though.

I would also check to make sure your toe brake axis is not mapped backwards. Mine were by default.

A pixel at 4k is a 1/4 of the size of a pixel at 1080 assuming the monitors are equal in size. Running 4k without dots is easier to spot aircraft than 1080 without dots. Especially with a larger screen. Your pixel density is higher at 4k so the object can be rendered smaller/farther away. (or 4x the detail at any given range) The dots are easier to see than a single pixel of an object and they are rendered closer at lower resolutions. Looking at a 4k screenshot on a 1080 monitor without a zoom function loses all that fancy pixel density which is probably why the KoN still can't see them. Lastly, the difference between "label dots" and the visual aid "distance dots" is the label dots are always rendered, even when the object is right in your face. You don't have that invisible object range between dot and no dot. The down side is that label dots can be seen through clouds, buildings, trees, and at 100 miles away.

Thanks, that worked like a charm! I can finally move on. I did not know we had access to those mission files. I never bothered to look. Had I known I would have attempted to fix it myself. Thanks again for the quick fix, I appreciate it.

This is honestly my biggest issue with the entire dot mechanic. Your monitor resolution has a direct impact on your visual distance of an object. Once an object can no longer be rendered because of your monitors pixel density, they switch to the dot to compensate. That transition period between the dot an model though, the object just seems to vanish. Then you spend the next few minutes zooming out to find the dot, then zooming in to find the model. I don't know what the fix is to be honest, but the way the dot works now is not ideal. If I could force the basic black "label dots" that were occluded by geometry, distance and clouds I would be happy though.

Thanks for the confirmation. Also thanks for posting the track, that is above and beyond. I probably should have done that myself, but I was so frustrated at the time I did not think about it. At least I know I am not missing something or doing something wrong. Hopefully there is an easy fix/update in the future.

Pretty much what the title said. I have tried this twice and it stops at the same place. It states to move the stick left and right and in never goes to the next step. I have tried the HOTAS obviously as well as the keyboard. I even tried the trim. I would really like to know what this is expecting so I can move on. This is like 30 minutes into the mission. If you look up frustration in the dictionary, this would be there.

Yes, but you will need more than one sound device in Windows. HDMI/GPU sound out On Board Soundcard sound out USB headset sound out If you have a traditional 1/8" TRS/TRRS headset plugged into your onboard soundcard and trying to use your onboard soundcard for speaker output as well, that is a no go. If you have a USB headset, you can change your default "sound" device to the onboard for speakers and default "communication" device to the USB headset in windows.

Agree with all of the above, especially the troops in the back. Although, I would settle with a little AI tweak that would stop troops from running straight for a tail rotor whenever they see one. "Ohhh, look a spinning shiny!" :You have committed fratricide:

Can confirm. I just tried the latest 23.3.1 Adrenalin with the latest open beta and it no longer crashes on my end.

Oddly enough, the payload window did not crash it for me, it was when I clicked on a "static" unit. That opened the little 3d preview window which caused an instant flashing lightshow again and CTD. FYI for others, the latest stable driver I can use on both the 6800XT and 6950XT is 22.5.1 04/28/22. Edit: I also forgot to mention, rolling back the drivers was not enough. Windows 10 would consistently re-install the new driver even with driver updates off. I even have hardware updates off in group policy. You have to go into the control panel/device manager and manually install the old driver through there. That was my experience anyway.

Disabling the models in the editor worked for me until I clicked on a static unit that opened the little 3d model window, then it would instantly crash again. As stated above, I also had to open a blank mission first. Also noted in my post, the new driver works flawlessly on my RX Vega 56 in my laptop, but crashes on both my RX 6800 XT and 6950 XT's. I had to roll back the driver to get those stable. Again, no overclocks. I am not sure what the issue is, but there is definitely an issue.

HA! Of course that thread would be hiding right here after a week of pulling my hair out. I did do a quick search for this, but I was convinced the new GPU was somehow going bad and focused my search on that and not the editor. Oh well, I am just glad it is all sorted and my GPU is not the issue. Hopefully either AMD and/or ED can get this worked out.

Holy horse crap batman! I think I got it! I used DDU before the swap. Also the options.lua was blown away when I nuked the game install and all traces during my troubleshooting. I do appreciate the help though. I was about ready to give up. Anyway, back to the fix. During my Nth test run today I actually got the editor to hang rather than CTD. This time I had more information in the log file and it crated a crash dump finally. There was some sort of access violation with a amdxx64.dll. On a whim I just tried a previous driver version and it opens the mission fine now. No more screen flashing on map load either. Why the laptop's Vega56 opens the mission with the latest driver and the desktop's 6800XT does not is beyond me, but I'll take it. I have been at this for well over a week.

One last bit of info, this is the last list of entries in the log file after opening the custom map... 2023-01-09 13:10:22.615 INFO ANIMATOR (Main): load_basic() started 2023-01-09 13:10:22.996 ERROR EDCORE (Main): Can't open file: /animations/typev.anim. 2023-01-09 13:10:33.739 INFO ANIMATOR (Main): Loading graphs: 2023-01-09 13:10:33.828 INFO ANIMATOR (Main): load_basic() ended 2023-01-09 13:10:33.828 INFO ANIMATOR (Main): load_main() started 2023-01-09 13:10:34.014 INFO ANIMATOR (Main): load_main() ended 2023-01-09 13:10:35.941 INFO ANIMATOR (Main): load_basic() started 2023-01-09 13:10:36.212 INFO ANIMATOR (Main): load_basic() ended 2023-01-09 13:10:36.212 INFO ANIMATOR (Main): load_main() started 2023-01-09 13:10:36.557 INFO ANIMATOR (Main): load_main() ended 2023-01-09 13:10:40.703 ERROR NGMODEL (2920): Can't load lod //models/invisiblefarp.edm of model invisiblefarp. Reason: Model has invalid bounding box. 2023-01-09 13:10:57.560 INFO APP (Main): Screen: MissionEditor 2023-01-09 13:10:57.564 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1366, 768] 2023-01-09 13:11:15.408 INFO GUI_MAP (Main): levelformap=1 2023-01-09 13:11:36.275 INFO GUI_MAP (Main): levelformap=0 2023-01-09 13:11:52.902 ERROR_ONCE DX11BACKEND (3008): texture 'zil135l_spec' not found. Asked from '' 2023-01-09 13:11:58.716 ERROR_ONCE DX11BACKEND (3008): texture 'mi_8_tex_spec' not found. Asked from '' 2023-01-09 13:12:34.791 ERROR_ONCE DX11BACKEND (3008): texture 'f-5e3_cockpit_normal.bmp' not found. Asked from '' 2023-01-09 13:12:34.791 ERROR_ONCE DX11BACKEND (3008): texture 'f-5e3_cockpit_spec.bmp' not found. Asked from '' 2023-01-09 13:14:17.943 INFO GUI_MAP (Main): levelformap=1 2023-01-09 13:15:12.790 INFO GUI_MAP (Main): levelformap=0 2023-01-09 13:15:13.570 INFO GUI_MAP (Main): levelformap=1 2023-01-09 13:15:15.910 INFO GUI_MAP (Main): levelformap=0 2023-01-09 13:15:18.998 INFO GUI_MAP (Main): levelformap=1 2023-01-09 13:15:21.063 INFO GUI_MAP (Main): levelformap=0 2023-01-09 13:15:23.188 INFO GUI_MAP (Main): levelformap=1 The above is taken from my laptop after the mission completely loads. The desktop log is identical except this is the last line after crashing... 2023-01-09 13:10:57.564 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1366, 768] Any ideas?

First, a little background information. I have DCS on two computers, my Desktop and my Laptop. I have been working on a rather large custom mission without issue on either for hundreds of hours. I just installed a new GPU in my desktop and now the custom mission will CTD every time I try to load the map. It still works fine on my laptop. I have done a crap load of troubleshooting and narrowed it down to the editor when it loads the 3d models in either the model viewer or if I enable show 3d models in the editor map window. I have checked the logs and there are a few errors, but I get the same errors on my laptop which does not crash. I don't think they are causing the crash. There is one error that sticks out though... 2023-01-05 19:08:22.892 INFO GRAPHICSVISTA (Main): renderer: 'dx11backend.dll' 2023-01-05 19:08:22.944 INFO DX11BACKEND (Main): DX11Renderer initialization (w:1920 h:1080 fullscrn:1 vsync:0 adapter:0 monitor:0 shaderErrors:1) 2023-01-05 19:08:23.237 INFO DX11BACKEND (Main): Driver Concurrent Creates - 1 2023-01-05 19:08:23.237 INFO DX11BACKEND (Main): Driver Command Lists - 0 2023-01-05 19:08:23.242 INFO DX11BACKEND (Main): NvAPI_Initialize Error: 2023-01-05 19:08:23.304 INFO DX11BACKEND (Main): ATI Adapter AMD Radeon RX 6800 XT 2023-01-05 19:08:23.304 INFO DX11BACKEND (Main): ATI Driver Version 22.20.29.10-221130a-386458C-AMD-Software-Adrenalin-Edition 2023-01-05 19:08:23.304 INFO DX11BACKEND (Main): AGS Version 3.2.0 2023-01-05 19:08:23.304 INFO DX11BACKEND (Main): GPU count:1 2023-01-05 19:08:23.484 INFO DX11BACKEND (Main): commonPool: 48-128, cbPool: 4-14 2023-01-05 19:08:23.484 INFO DX11BACKEND (Main): samplerPool: 5-16 2023-01-05 19:08:23.484 INFO METASHADER (Main): Init filesystem: G 2023-01-05 19:08:23.491 INFO DX11BACKEND (Main): DX11ShaderBinaries::loadCache Bazar/shaders/fxo/fxo.zip 2023-01-05 19:08:24.982 INFO DX11BACKEND (Main): DX11ShaderBinaries::loadCache done. Loaded 1854/1855. 2023-01-05 19:08:24.990 INFO DX11BACKEND (Main): DX11ShaderBinaries::loadCache C:\Users\*****\Saved Games\DCS\fxo 2023-01-05 19:08:25.001 INFO DX11BACKEND (Main): DX11ShaderBinaries::loadCache done. Loaded 119/119. 2023-01-05 19:08:25.017 INFO VISUALIZER (Main): SceneManager initialization 2023-01-05 19:08:25.254 INFO VISUALIZER (Main): cascade shadows init (preset:'default' quality:4 layers:4 size:4096) See that shader error? Also 1854/1855 shaders loaded. I am not sure that is the cause, just the only thing that stands out to me. Also this stands out in the mission editor section... 2023-01-05 19:08:51.289 INFO EDTERRAINGRAPHICS41 (Main): ITerrainGraphicsImpl4::openTerrain() END 1.083557 s 2023-01-05 19:08:51.289 ERROR_ONCE DX11BACKEND (Main): render target 'cloudShadows' not found 2023-01-05 19:08:51.289 ERROR_ONCE DX11BACKEND (Main): render target 'mainDepthBuffer_copy' not found 2023-01-05 19:08:51.289 ERROR_ONCE DX11BACKEND (Main): render target 'DummyShadowMap' not found 2023-01-05 19:08:51.308 DEBUG LuaGUI (Main): Mission G:\SteamLibrary\steamapps\common\DCSWorld\Saves\Missions\CanyonRun.miz loaded ...This happens on the smaller missions too though that do not cause a CTD. I have purged all shader caches in Windows and through the GPU drivers. I have completely unistalled the game, deleted all user save file folders and in the user appdata folders. (made backups of the mission files first) I have tried the recommeded page file settings in the pinned thread. I pulled the two mod's I had installed as well. (A4 and T45) Although neither are in the custom mission that is crashing. Note: I can play replays of these missions and play the missions themselves fine. No issues. Partial Workaround: If I open a new mission in the editor, turn off 3d models and switch the map type to "Map" rather than "Alt" I can then open the custom mission without crashing. That is until I click on a static unit that opens the model viewer window. That will instantly cause a CTD. One last bit of info. When I try to open the custom mission file first, or when I click on a static unit and the model window pops up, the entire screen flashes like it is loading and refreshing the screen really fast a bunch of times. Something I do not experience on the laptop or this desktop with the old GPU. FYI, the computer is 100% stable during DCS mission modules, instant action and on other high demand games and high GPU load. I have also ran multiple Furmark burn ins and have had zero issues under 100% load. Nothing overclocked. Desktop: Windows 10 i7 7700k 32g DDR4 RX 6800 XT new (GTX1080 old) SSD OS and Game install location Laptop: Windows 10 Acer Preditor Helios 500 Ryzen7 2700 16g DDR4 RX Vega 56 SSD OS and HDD game install locations