MrShooty

The Hellfire L on the Apache is able to lock onto search radar towers but always flies and misses long. You can lock the tower up either on the Apache FCR or using TADS and laser and then input the target data. But following launch the missile always misses and flies and hits past the target by a good way.

It’s great your asset pack is being added as standard to DCS. Congratulations and thanks. With Afghanistan on the way we could do with some additional units. Since in both NATO and Russian wars the opposition was an insurgent force hiding within a civilian population it’s clear we really don’t have a great variety of suitable assets. If you read many real life accounts a large part of the challenge was to pick out insurgents and avoid civilian deaths and collateral damage. I’d be particularly interested in Afghan civilian units - people, animals, buildings, motorbikes, cars, trucks, agricultural equipment. At the moment if a person is placed on the map they are all (apart from the air show crowd) of a military disposition.

I'm getting this issue after the last update. I never had it previously. No mods added recently - it happened immediately on getting the latest update. Coming out of F10 or F2 views into F1 cockpit the FPS drops from 40-ish to literally 1 or 2 fps. It can hold at that for several minutes as it tries to catch up. I have 64GB ram and run a 3080ti and a G2 VR headset. I'll try cleaning a few folders and uninstalling some mods.

Thanks again, Flappie. Yes, this worked. Interesting that the ST version dropped about 10fps with the update. But now MT with DLSS is up to where ST was before - around 45 fps - so it's a wash and I'm OK with that. MT now looks a bit better than ST too. Sorry I posted on it again last night - I didn't see your response.

The single thread version of 2.9 - both before and after the hotfix - does not open into VR (VR option selected as usual). Meanwhile the MT version works just fine in VR. The log is attached and on the line where VR is called it actually says to ask for support! System (as you can see in the log) is i9-12900, 3080ti, 64RAM, Reverb G2, OpenXR, Windows 11. Thanks for your thoughts dcs.log

I confirm that I am running OpenXR. Strange thing is that it runs fine in VR in Multi-thread but not in SIngleThread where it defaults to flat screen. I want to run ST since I'm only getting 35 FPS in game using MT and about twice that in ST.

Update - after Flappie told me to get a full log (that step isn't intuitive so your instruction was good) I read it and saw my NVidia driver was not allowing DLSS. I checked that the driver was up to date in Windows 11 settings and it said it was the latest. Then I checked directly with Nvidia and found it was 2 years out of date! There's a lesson. So I updated it manually and now DLSS works. I get 35 FPs so it is still less than my single thread version but it is operable. I'll investigate more but for now I guess my query on DLSS is solved. Many thanks I found that my Nvidia driver needed to be updated. WIndows was telling me it was fine but a manual check proved otherwise. I can now use DLSS (but my FPS still sucks).

Did this do the trick. I was starting the game without VR/WMR - DLSS is still greyed out but the FPS count is a healthy 180 now. dcs.log

Log attached. Confirm that mods removed, cleanup and repair. dcs.log

Confirm mods removed, cleanup and repair. Issue remains. Log attached. dcs.log

As the title says - despite having VR enabled in the VR section - Single Thread standalone OB now will not open to VR and defaults to flat screen. The Reverb G2 is left showing the WMR cliffhouse whilst DCS opens on the screen. It's done this repeatedly. I'll repeat the process and attach a log shortly.

Using the MT version it's not possible to select DLSS - it remains greyed out. FSR and NIS are selectable but seem to have no effect. System is i9-12900k 3.2Ghz, 64k RAM, RTX3080ti, Reverb G2. CPU 26%, GPU 68%, FPS 14. Definitely using MT stand alone. OpenXR. Note that even in MT 2.8 my FPS was half the rate I got in Single Thread - 25 vs 50. But now in MT it's dire and my ST version now will not open into WMR VR.

For the record, George the Pilot regularly just drops the plane into the ground. You don't need to be doing anything very smart - just asking him to slow down to a hover will do it.

When George CPG comes up with a list of possible targets he uses the Russian nomenclature. So instead of him reporting a "Fan Song track radar" he reports an SNR75. I'm sure as a NATO pilot he'd be using NATO nomenclature but it also makes it difficult to work out on the list what the targets actually are and so decide on priorities. Clarity and rapid recognition is exactly why NATO creates code words for enemy equipment.

This gets my vote. If George could give me a range to target it would be most helpful.

I should test mine in 2D vs VR too. But the rest of your story sounds similar to mine.

I'm getting 45-50 FPS in ST and dropping to a lower quality 18FPS in MT. Consistent across modules and maps. CPU, GPU and RAM are 22, 63, 45% utilisation in MT and 13, 98, 50% in ST. I'm feeling that CPU should be much higher if MT was working - but I'm a novice so advaice would help. I have a i9 12900k, 64Gb RAM, 3080Ti and use a Reverb G2. I've fiddled around with the NVida control panel as recommneded by SpecialK above, cleared the fxo and shaders2 files in saved games, run a cleanup and (fast) repair. I'm about to do a slow repair. But at each stage when I've checked th e FPS in MT remains absolutely rock solid at 18-19 FPS - surprisingly consistent. Any suggestions will be much appreciated.

So for the hard of learning - what does ASW stand for? Anti Submarine Warfare when I last looked but I presume it's different. What does it do and where are the settings for it? Thanks

It's early days but the effect of MT for me is to drop FPS to 40-50% of usual. I normally get around 45-50fps and the MT version drops me to around 18 in game. In the opening hanger it goes from 50 to 25. I've tested in Caucus and Syria and with the Harrier and the Apache and all in single player with simple user generated test flights with only a few units. I've not done any tweaking of settings so far - not sure what to tweak - but I have most settings up towards the high end anyway. My system is: i9-12900K 3.20 GHz, 64.0 GB (63.8 GB usable), RTX 3080 Ti, Windows11 running a Reverb G2. I have a few modules like SAM asset pack and the Bronoc, Starfighter, Hercules but no modifications to the game system. I keep the DCSopenbeta file clean and only add stuff to the saved games. Are there any diagnostics that I should run to get more of a picture of what is happening? Are there any files I can send to help ED programmers?

Mission 1 is very confusing. I started on the land and flew to WP1 on the ship - supposedly to meet the helos I was escorting. But it seemed they had long gone and I'm guessing I should have started on the Tarawa and flown them into the land? But I'm still confused. Why did I start on the land then? Needs clearer explanation in the mission breifing since that first run was a total waste of 30 mins. But of the game mechanics that I saw it worked just fine and looked good.

When I press the autopilot reset button it usually disables one or more of the axes on my cyclic or tail rotor pedals. I'll be flying and set the force trim (autopilot hat forward) and can fly with the force trim engaged. But when I want to reset the trim and depress the trim had accordingly it almost always disables one of the four cyclic directions - usually cyclic forward. The consequence is of course that the helicopter, trimmed for forward flight now rears up and does not respond when the cyclic is pushed forward to correct it. If I look down at the cyclic and what where it is moving it will move in the other directions but looks like it is locked from moving forward. The solution is to pull in the opposite direction (ie. backwards on the cyclic) and then when I push forwards it responds normally (although by this time I've gained 200 ft in altitude and lost 30kts airspeed). I've experienced the same with the rotor pedals and you can see that one of them has locked and will not move - you need to press the other to free it up. Whether it is connected or not I also note the the Attitude hold mode (trim hat left) is useless in the hover - simply doesn't work like it does for Wags in the video. It used to work a few weeks ago but now seems to do nothing.

f410, you're a bloody genius. The latest beta downloaded and it's now working with DCS. Many, many thanks. i'll make a donation.

Many thanks. I’ll download the Beta then.

I tried setting the network file to write protect but it just sends up an error and then doesn't fix the issue. Here's the log from doing that. As ever, any tips or tricks are most welcome - I really want to get simshaker running for DCS. Export.lua dcs.log