Hovis

With current settings, I can fly an F-5 around Persian Gulf with 72 fps, no hiccups. F-16 Syria free flight usually around 60fps. Now however, only started noticed this since the last patch, if I load a vaguely heavy mission, the textures take a loong time to load, roughly 10 seconds. Previously this has always been instant (M.2). Once they load, VR will slow down to 10fps and the FPS counter will flick between CPU and GPU limited, with GPU limt showing theoretical fps of 40-60fps, which I'd expect normally. Going back to menu does not fix this, DCS is now stuck at 10fps with GPU limit flashing on/off. Log file attached shows the F-5 flight, then loading an F-14 campaign mission, carrier start. Specs Headset - Quest 2 CPU - Ryzen 5 5600x GPU - RTX 3070FE RAM - 32GB DDR4 2400MHz Mobo - B450F Gaming ii dcs.log

Trying out multiplayer servers, and nearly every server I'm able to load quickly and within 5-10 seconds DCS is running smoothly, I can run my mouse over the available slots and highlight each and every one, before selecting whatever I wish to fly. Tested serves include all the ThroughTheInfernos (inc.Syria), average fps in multiplayer Syria is 40-70 Not Enigma for some reason, tried with different settings, lower and raising preload radius - no dice. Log file shows an attempt where i let it run for 10 minutes in the select role screen. I was able to highlight 3 player slots. Maybe 8 frames loaded in the whole 10 minutes. Wat? Could somebody please explain what I'm missing here? Specs - Ryzen 5 5600x - 32gb 2400MHz DDR4 (thinking I need 64?) - RTX 3070 FE - B450F GamingII mobo dcs.log

Sorry Florian I have the same question, but I can answer Dish's question. Instead of having the helo as a static, place it as a normal AI and tick "uncontrolled". Then in the AI options go to the triggered actions tab (looks like a quadrocopter) and add the command "start". You can then trigger this command with a normal trigger, which will then place the pilot in the cockpit and he'll fly off on whatever mission you've given him.

I'm attempting top put together an Op using the Skynet IADS script, which I've used before (pre-2.7) to great effect, awesome script btw. However, now that I'm tweaking the IADS, I'm noticing some issues and some are replicated in old (unchanged) missions that used to work pre-2.7. The two things that are bugging me at the moment are - 1. The point defence units activate very late - a HARM fired from 20,000 within 25-30 miles? Nah, too slow to react. They'll turn on but it'll be moving too fast for it to intercept. 2. The command "GoLiveRangeInPercent" doesn't seem to apply. Trying to set an SA-11 and an SA-2 site to activate before max missile range doesn't work, if anything the SA-2 activates late (only once tgt is within 70% missile range). Combine this with the slow SA-15 reaction time means that there's no hope for the poor radar.# 3. All SAMs now remain active once a HARM is fired, even if i've set the option to false (option in point defence command), or removed the command altogether. I tried running an old Op which worked wonderfully, now all the above issues apply to that mission too. :( Am I missing something?

Hi! Loving it so far, however I my ineptitude may have found a couple of lil issues with missions 3 - the long range hit over Basra. In mission - tasking Smoke to hit the first tgt (truck) works fine, however when i tasked him to hit the second tgt (compound) he responded affirmative, had the calls from the JTAC but he just kept on orbiting. This broke it as I'd screwed both my drops due to issues of my own so I had to quit out, guns don't work on houses apparently. Second issue was regarding your save feature. Stated before tanking and partway through mission that should I leave, when I continued the campaign it would spawn me behind the tanker with full tanks ready to go... nope, it put me to the start of mission 4. Which is good I guess as it doesnt break the campaign, simply misses out my completion of mission 3 Cheers BD for a great campaign

Right now it is missing features across the board, however for air to air it's one of the best aircraft in my opinion. Situational awareness is unmatched, visibility is better than any other aircraft, it's a dream to fly and moves like a bat out of hell. Make of that what you will

Buddy and I were flying on Buddyspike PG with no issues When we both landed a harrier came in to land, my buddy looked up and zoomed in, screen froze and crashed to desktop. I looked out of my cockpit at the harrier as it touched down, screen froze, crashed to desktop. Crash log included dcs.log-20200421-161432.zip

Solved! Delete fxo and metashaders2 folders in the DCS saved games folder and all is well with the world

Update - there was an issue with hardware reserved RAM, now fixed and system using all 16gb, as shown in attached log But original problem still remains, caucasus is still crashing dcs.log-20200326-214432.zip

I built it, 16gb and it appears everywhere else Screenshot attached

Thats interesting, as I have 16gb or RAM.. Also that didn't work, I have an SSD with OS, a HDD and another SSD with DCS on it, tried 16gb pagefile on the HDD, with HDD and OS SSD and just on the OS SSD, same crash every time. Crash logs included again dcs.log-20200326-190729.zip

Pretty much what it says on the tin. Mission building all morning on Caucasus, no issues at all. Suddenly open a new editor with clean Caucasus and once i zoom in to a certain level the game will crash. Every time. No issues on PG or NTTR, both in-game and editor work fine. I've tried updating openbeta, and repairing several times. Any way to fix this without reinstalling everything? Logs attached dcs.log-20200326-164104.zip

Found a fun bug whilst playing on the buddyspike server Was flying the A-10 and got shot down while I had the litening pod warming up, switched to f-18 and the moment my centre MPCD came to life I've got the A-10 Litening warm up screen laid on top. It goes away after a time but it definitely should be there

Hi all, I'm very aware that the carrier spawn mechanics are changing and are this moment... funky... However I'm wondering if there's any current rhyme or reason for what's going on right now. Some times I can set 15+ aircraft to start on the carrier, sometimes it locks at 4, with others instantly snapping to other airfields (I'm sorry that mechanic is utterly retarded) I know the maximum number of active aircraft on the deck at one time is 10, however in multiplayer it seems like playing the lottery when it comes to getting the slots to actually work or just giving the "flight delayed" message. This becomes even more sketchy if I add statics to the deck, even if those statics are well clear of all spawn points/areas. I've tried a mixture of adding aircraft one at a time next to the carrier and individually setting them to ramp/parking hot, I've also tried making the whole group and then snapping them to the carrier. No matter the method if it works perfectly there's a good chance the exact same method it won't work at all the next time I do it. Help a brother out? (I'm assuming and honestly praying there's a new system coming in when the new carrier module drops?)

As the title says really: (Most) not all of the time when i switch to a unit and I've landed my huey, the AI will jump into my aircraft and take it away on some magical adventure... No idea where or why, is there a way to keep your aircraft where it is so you can come back to after the stint in the ground unit? Overall objective here is to land at a FOB, unload a unit using CTLD, use it as JTAC for a multiplayer mission, then jump back into the helo to carry on the mission

Ahhhha, found a conflicting keybind for the mouse wheel... fixed that... never thought about FoV, thanks

I'm looking to set up a mission using CTLD and the works, but in order for a player to effectively act as a JTAC they have to be able to lase a single target not just "something over there". The whole point of a pair of binoculars is to see further right? So why is my view when using so damn small, it's impossible to pick out a single target 1nm away unless it's a skyscraper. Searched and searched but I can't find any button or command to zoom in the binos, please tell me I'm missing something

When flying a simple custom mission with only one F-18 (me) and one Yak-40 uncontrolled on the ground my game will crash the moment i press the button to release the gbu-31. I have four on the wings, I can enter the coordinates no problem and it gives me all the cues, including the in range cue. As for the crash it simply froze, no sound, frozen frame of the cockpit, alt tabbing doesnt work, win tabbing doesn't work (DCS just re-opens over all windows), only way to close is to alt tab, then win tab and open a new desktop, from there I can open the task manager to end the process. No crash log is produced the and DCS text file doesn't go up to that point, stops a few seconds before it

When selecting PAL, VSL Hi or Low there is no indication on the HUD that the mode is active, however they do work, a lock is acquired I just have no idea when it will happen. However if I ask my human RIO to select VSL low I can see the indicator on HUD

Just saying I don't have this issue, I can use hot mic and override in both pilot and RIO seat without it sticking. If it's any help I use one button, hold it for ICS, mod1 + hold for comm 1, mod2+hold for comm 2

Hi, slightly confusing part in the manual which I would very much like a little light on. In the section regarding Pulse doppler single target track there a paragraph which reads: "Unlike in pulse STT however the AN/AWG-9 can send missile guidance commands in pulse doppler STT enabling launch of AIM-7 and AIM-54 in pulse doppler mode. This is the mode with the greatest launch ranges for those missiles with the disadvantage, in the case of the AIM-54, of only being able to engage one target at a time." At first glance my RIO and I both interpreted this to mean that AIM-7 and AIM-54 missiles can only be launched in pulse doppler mode as pulse does not supply missile guidance commands. I know this is not the case in sim as we've tested splashing 29s with both sparrows and phoenixes firing from just P-STT and PD-STT and then switching to P-STT post launch... all missiles hit Is the correct interpretation that PD-STT is capable of sending missile guidance "updates" to more accurately guide the missile and therefore increasing the missile's range?[/font]

I've been spending some time fiddling with times and dates for the perfect transition from evening to moonlight without several hours of pitch black in between. I'm using lunar tables to get the dates and trying days forwards and backwards to get the moon fairly high (full moon) but no matter what I do after sunset it goes pitch black for at least 2 hours then bang, moonlight with the moon high in the sky. Does anybody have a set time/date where it goes smoothly so I can finish an evening mission with a moonlight carrier landing without going completely blind in the process?

Literally... the manual http://www.heatblur.se/F-14Manual/index.html

With the canopy closed you cant hear the chief, trysetting ICS comms to hot mic so you can hear the response (if any) Then at least we know if the chief heard you

No.... not like this.... Is there a hole I can crawl into somewhere?