104th_Money

Glad its working for you. I cant even make a mission anymore without the MIST/CTLD, CSAR and JTAC scripts. They make them so much more entertaining.

Can confirm its still working. Are you sure you set the proper laser code in the do script and are using the same in the aircraft? ctld.JTACAutoLase('Mad Dog 11 AFAC', 1688) I use this with no issues.

@cfrag I have been trying to implement CSAR script into my missions to go with MIST/CTLD. I followed the CSAR test mission example and it show up in F10, I can pick up the pilot but for some reason I can’t drop him off. I landed at invisible FARP, created a blue mash unit and it just doesn’t happen. Could send me one of your missions so I can see what I might be doing wrong? Will check it out when I get home from work. Appreciate the help bud! Appreciate the help bud!

@cfrag I have been trying to implement CSAR script into my missions to go with MIST/CTLD. I followed the CSAR test mission example and it show up in F10, I can pick up the pilot but for some reason I can’t drop him off. I landed at invisible FARP, created a blue mash unit and it just doesn’t happen. Could send me one of your missions so I can see what I might be doing wrong?

When i put tankers in a mission, alt is usually 18,000-25,000' and if you put the speed of 430, at 25,000 thats about 290 during tanking. At 18,000 it pushes up a bit higher. If you are using an orbit, make sure that you set that speed the same as waypoints in the advance waypoints section.

Ive been having crazy fps issues since I built my new pc, 13900k/3090/64gb ram. I disabled Tacview and I have no more issues...

@NineLine Unfortunately this particular mission is heavily based on triggered actions and the helos and planes don't come into play without at least a few people on and certain taskings completed. So would not be easy for me to duplicate unless I were to just make a mission with solely those assets in there.

I am no modder for certain, I know next to nothing about 3d stuff, meshes etc, but as a mission maker I can tell you that current state of AI/Static objects in general is very much in disarray. AI aircraft damage modelling is absolutely terrible. I recently built a mission that has a 4 ship of Mi-24p, 4 ship of SU-24s and Su-25s attacking a large FOB at various intervals. Air defenses are NASAMS, Bradley Linebacker M6 and the Vulcan point defense vehicle. I watched as the Mi-24s ate so many missiles, so many gun rounds and just kept on flying, same with SU-24s, just taking impossible amounts of damage without killing them. Trying to make a realistic scenario in which you would strike C3, POL, air bases, railways, etc is impossible to do even remotely. The only thing there really is to do is just shoot AI ground vehicles all day in a mission or transport supplies. Thats not to mention static objects, the inability to late activate or group them and unable to "kill" them, getting kill messages or trigger actions from. Only a few generic static buildings are able to be destroyed. To hear that it takes time to do all of these things is understandable but to fix these issues alone would be to increase the immersion level 10 fold. Im sure im going to get incoming trash about this but it is the truth nonetheless.

@NeoBlue That is a long way to restart your mission. I name my missions X.XA and X.XB. Say I want it to restart after 8 hours. Add a once trigger>time more 28800>load mission. Then I load the B version. Then go back to B version and load A version. Mission restarts no problem every 8 hours

@Gunslinger52 Sorry for late reply, was searching something else and happened upon this post. With Fog of War and Visual Recon Mode enabled, if you go into Visual Recon Mode and click when you are looking at the targets from your aircraft, it gives a bullseye call and then shows the units on F10 map. If there are alot of units to view, you may need to click in the target vicinity multiple times to recon all targets, only the first recon gives a bullseye coordinate. Other than that, if you are not specifically trying to use Fog of War/Visual Recon mode then what cfrag said as far as late activation with aircraft in trigger zone to spawn would be the easiest way.

@cfrag @jonsky7 Thank you both for taking the time to provide a look into how to accomplish this. @cfrag I never knew that lua had the ability to do that, unfortunately my entire lua scripting skill is just editing a lua file...When i look at lua scripts I just get lost like its a foreign language to me. I do know that its very powerful and can accomplish things that cant be done in the ME. What I will do is look at other peoples lua scripts that may be similar and see if I can adapt or figure out how to do it. @jonsky7 Thanks for taking the time to put that example together for me, I did not know how to do a radio item remove. Looking at your mission file sparked a possible idea that would make what I am trying to do less resource intensive and easier. I appreciate both of you.

Ok guys, so what I am trying to do is set up a mission which uses the F10 menu to let players know where there are target taskings available. So for instance, I would like to have 20 target areas each inside of its own trigger zone. In those trigger zones if there is part of a coalition in zone I would like to have a radio item in the F10 menu that displays a message to coalition with target priority, target types and grid coordinates for each of the occupied trigger zones and leave out trigger zones that do not have part of coalition in zone. I would also like this to be up to date information so if a target area is destroyed and there are no part of coalition in zone, every time the player checks the F10 menu for available targets, it would only display messages with current targets. So say target area 1, 3 and 5 have targets, using the part of coalition in zone conditions would put those 3 messages to coalition in F10 menu. If the other 17 target areas do not have part of coalition in zone, no messages would be displayed for those target areas. If units then moved into 5 other unoccupied trigger zones but left 1 other previously occupied trigger zone it would show messages for the 5 new trigger zones, the 2 previously still occupied zones and remove the message for the 1 now unoccupied zone for a total of 7 messages. Im not even sure if I am making sense in what I am asking but my only experience with this is to spawn units with radio menu items. Any help or suggestions would be greatly appreciated.

@Czar66 Sorry for taking so long to get back to you. You are correct, in the air the control surfaces match the movement of my aircraft and the movements are instantaneous. Thanks for the help bud. @Rudel_chw Thanks for the suggestion, I tried Czar66's suggestion first and it worked. Thank you for trying to help. @Theodore42 I fly with no axis tune in the Seagle, same as with the Hornet. Full joystick movement and it seems to work fine...In the Viper I have max control surface deflection at a little less than half joystick movement. It is very sensitive but it just seems to work better in the Viper like that for me.

Thanks for the responses guys. I will have to check that out when I get home from work. I never suspected that it might be something like that. I have had this issue in other planes but was able to take care of it through axis tune.

So I was in external view and noticed that there is a pretty decent delay in the movement of the joystick to how the stabilizers respond. At full rear deflection if I let go of the stick very quickly it takes almost a full second to return to the neutral position. I tried adjusting saturation and curvature on stick but nothing seems to work to give immediate control response. In the roll axis, the ailerons respond and return to neutral immediately. Is this something they are working on or am I missing something here?

88,915' is highest I could get it. Engines quit on the way down and unable to restart...

Have you done any overclocking recently? Changed or reset any settings in BIOS? I built a new PC recently with an i7-12700k/Evga Nvidia 3090 FTW3 Ultra Gaming-slight overclock/64gb ram DDR-4-3600/1000watt psu/liquid cooling and had a slight overclock to it. I then decided to go with the i9-13900k processor. I reset bios but my mobo had some default settings that removed some power limits. It caused alot of crashing and what appeared to be memory or driver related issues. I did alot of what you had tried as well but to no avail...in the midst of it all, there was a windows update and an Nvidia driver update that I had to suspect as well. In the end, I figured out that due to the mobo default power limit removal, my CPU (the 13900k uses quite a bit more power)and GPU were both spiking up enough when loading DCS that the PSU could not handle it and caused crashes. I was getting different BSOD messages including for memory issues and nothing I was doing helped. Finally, after googling PSU spikes I realized that this was the issue. After turning back on power limits in BIOS, all issues were resolved immediately... Hope this helps

@razo+r So sorry bud, I had asked this question quite awhile back and for some reason never even saw your response. Finally decided to tackle this issue again and found my own post... I just tried this out and its exactly what I needed. Thanks!

In my quest to get the smoothest play at the highest possible settings with my 13900k/3090/64gb ram/trackir/2k display combo I have still been getting the slightest stutters in MT. I did 3 things that gave me the best performance and the last one stopped the stuttering. First, I turned shadows to flat only...during sunrise in an Apache(seems other aircraft use about 15-20% less resources that the Apache) flying over Raqqa on the Syria map with shadows setting on high would push my 3090 to 100% usage whenever I was flying into the sun. Second, I changed my cpu affinity setting so that DCS would not run on my e-cores, disabling 16-31 threads which only lets DCS run on my P-core threads. But I did notice that at any given time, half of my cores were parked which is an energy saving feature. Its strange, the parked cores varied with different threads being active then parking and so on and on. Drawback is that I have to set affinity each time I boot up DCS after I am in the cockpit... Third is that I went into the registry editor and disabled all core parking. This got rid of my stutters, as well as dropping the GPU usage by about 10% and spreading all of the work across the 8 p-cores 16 threads which dropped usage per thread for the first 8 threads from almost 100% to about 65%, the 9-12th threads up to about 85% usage and the remaining 4 threads to to about 65% usage with GPU usage maxing out at about 73%. Hope this helps someone...

Bumping post since no replies...

I'm a little late to the party here but just read through all the posts... The DCS Viper currently has several issues that is affecting its performance... First, the joystick. I have my warthog set to that maximum roll deflection is at about half of the roll axis of the stick. Pitch is a little more at about 3/4 of the pitch axis of the stick. It makes it very sensitive and took a bit to get used to but the quicker inputs to full deflection clearly give me an advantage against someone who does not. Second, the performance or lack of concerning bleeding off speed and regaining energy. I don't need a chart to tell me that it is off, no I've never flown a Viper in real life and I take into consideration that former pilots on YT may have a slightly faded memory after awhile or have a difference of opinion based on their perceptions. Viper HUD videos also don't necessarily give you a certainty of which block they are flying as some models have better performance than others, although you can somewhat deduce that newer 4k videos are probably being flown in newer block jets. That being said, I do believe that it bleeds off speed too quickly and does not regain energy as quickly in a rate fight. How can I be certain? Well, even a Viper driver that hasn't been in the cockpit for 10 years as GGTharos said, may not be able to remember the EXACT FEEL of the aircraft but he will definitely remember the hard numbers that were drilled into him about what airspeeds give what performance at a given fuel weight, weapons loadout, altitude and airspeed and what those numbers need to be when flying against a particular jet. So when they say, this is off quite a bit, that still compensates for the "feel" memory loss of the pilot. But numerous pilots have already been quoted saying that it is off. What we don't know is whether the SME's are able to give the exact performance information and in fact ED should make some of them available for discussion so we can hear their side of the story. Another thing not to do with the Viper that people are griping about is that it can't beat the Hornet in DCS. That's because the Hornet is definitely overpowered and should not be able to rate like the Viper. Its strength is in its exceptional nose pointing ability at low speed which it gets from its fcs allowing it to pull way more AOA than the Viper, not its sustained turn rate. This is why you do not want to get into a slow speed phone booth fight in a Viper against the Hornet and the Hornet does not want to get into a rate fight with a Viper. I promise you will never hear a story from a real Hornet driver saying "I remember fighting this F-16 in a rate fight pulling 7.5G at corner while he was pulling 9g at his corner, we were on the spiral down toward the deck and I was just rating right around on him." The real Hornet bleeds energy like crazy and takes time to get it back, period. Its almost like they need to give swap certain parts of the flight models out between the 2 jets. Third, the FCS is off in the Viper more than likely causing the lack of performance. I can say for certain that in CATIII mode, the roll rate is not reduced after 90 degrees of roll. It should give up to 324 degrees per second roll rate for the first 90 degrees of roll regardless of CATI or CATIII and at that point if it is in CATIII should reduce the roll rate by a certain percentage. Ours just keeps on spinning around. I certainly don't envy ED for having to model all of these things correctly with all the performance numbers matching up. Fourth, the blackout model is not accurate. Why this hasn't been changed is beyond me. We have been knowing it is not accurate for a decade or more with no changes other than adding G warmups to the blackout model. And yes, you do know that if you pull max G with no G warm up (I believe its 10 seconds at above 5g?) you will black out much quicker in all planes. Of course the ability to pull G varies greatly between individuals and a pilot that can pull 9g for 30 plus seconds one day might not have gotten a good night of sleep, ate properly or had been going through something stressful that day or the day before would only pull 9g for 10-15 seconds or GLOC from rapid G onset quicker. Knowing all of this, once G warmup has been accomplished we should be able to at least sustain 9g for 20 seconds to average it out. I have posted numerous times about the Lockheed Martin online magazine called Code One that had an excellent series on the F-16. Of course that was many years ago and certain things may or may not have changed since then but the author went into detail about pulling G and claimed he could hold 9G for 45 seconds and would be happy to prove it to anyone. Considering he was one of the test pilots of the early models, I would tend to give weight to his statement and call him a subject matter expert. Either that or ED needs to sell an addon that weighs you, takes a blood test and monitors your heart rate and blood pressure then uses those numbers to give you a variable G resistance every time you fly. Your triglyceride levels are too high, you ain't pulling much G today lol. Fifth, as discussed in this topic already. People need to learn the complicated skill of dogfighting and all of the nuances that come with it. Learn to maintain corner speed but know when you need to be at a different speed. Use the vertical, out of plane maneuvering etc. It takes so much practice to recognize the energy states and sight pictures to know when to do what effectively.

I’m not flying in VR but was recently a bit disappointed that my i7-12700k/3090/64gb ram was getting stutters in the Syria map flying the Apache over Al-Raqqa during sunrise with all settings on high when everywhere else and all other maps were not an issue. Found with aircraft testing that the Apache seems to use about 15-20% more resources than any other aircraft at same location. I recently upgraded to the i9-13900k and experimented with several settings and found that by leaving all settings maxed out but turning shadows from high to flat only stopped all stuttering and actually gave my 3090 some extra headroom while strangely pushing my CPU from average overall usage of 25-30% to about 40-45%. So maybe try just turning shadows off. I guess only a 4090 will run DCS at its absolute bestest.

Not sure if this is posted in the right section… was wondering if anyone had experimented with unparking the CPU cores and if so did it help at all with FPS.