chinpok

I did the test stock vs IC pass now with the FPS counter turned on. The fps drop is more or less the same but it's less "visible" without the mod as my FPS is already low. I did a 4v4 tank battle and the white puff smokes (when a tank is hit but not destroyed) are very bad for performance I dropped from 60 to 30-40. After that the standard fire/smoke is bad too but not that much: 50-55 fps. So it's actually not the fault of the mod but maybe something what the mod could also improve.

Thanks for the quick reply. I don't have any other mods, I meant stock DCS version. I'll retest with stock, non-IC when I have time.

The IC pass version works perfectly until there is smoke (e.g. vehicle killed) then my FPS drops very low even worse than the standard shaders. If there are many smokes it becomes unplayable. This is not an issue with the standard shaders (smoke doesn't help there either but it stays playable). Is this a known issue or somehow local to my instance?

Issue still present for clouds and distant airplanes (when they are reduced to a pixel or close to that). CV1 / Quest 2.

Thanks, I'm glad it's not a bug.

For refueling and rearming the plane needs to be shut down when it comes back up master arm is beeping and the FCS goes stupid, the plane is bobing much longer (LEF are dropping up/down) even ~500 -600 kph. Rearm the second time it gets even worse. Is this a bug or I miss something?

This is an old at least 3 month old bug. When VSYNC is enabled and I switch to ground radar in any plane the fps drops to 1-2 then gets a bit better ~10(sometimes the game crashes). I thought it is a general bug but recently I turned VSYNC off and the problem disappeared. How to reproduce: VSYNC on, switch to ground radar, monitor FPS drop.

Check SD-10 in tacview when it goes straight it has almost 0 drag, only loses some energy in turns. Off-topic "answers/comments": It can be defeated relatively easily with chaff and notching tho. AIM-120B guidance is stupid and feels like it loses too much energy in turns. RWR works in the rear hemisphere(for me), maybe not perfect but when I spot a hawk launch and do a 180 it picks up everything(radar, missile, tracking etc).

I don't have logs but our guess is that one of the reasons could be related to ships(OHP or the Russian destroyer or maybe any ship). I personally had my longest session without ships on the map(all destroyed) if we have any I crash after 5-10 mins.

My only guess so far is SD-10 hit/target switch: I did a test to check if I run out of memory(32GB and no I still had ~6GB left) and I crashed approx when my missile hit the target, this happened at least twice. To be precise freeze/then crash, no send report window. My guesstimate is when the missile goes for chaff it hits a "nullptr", but I don't have tacview yet maybe it did hit. And I have random crashes from joining a server to after 40 mins. Note: I don't fly other planes now, so it can be general DCS problem too. dcs.txt

No addons here, and I don't see how any addon could produce this behavior.

OB, no one plays on "stable".

I can confirm this bug is there for like 3+ month now, before that AP worked perfectly. So indication and slow descent, rarely it works and holds altitude but 90% time it isn't. And I firmly remember it worked perfectly earlier - you pressed it and it was holding the alt ofc within reasonable limits not 80deg climbing.

Update: Nevermind it is working: Create autoexec.cfg in C:\Users\USER\Saved Games\DCS.openbeta\Config Add line options.graphics.Camera.Extreme.dynamic = {300, 70000} Extreme is the render distance setting in the options Change 70000 to the render distance you want.

On my CH products HOTAS I can map buttons to keyboard keys so I map 3 on my throttle to ALT, CRTL, SHIFT so I have almost 3 times more buttons(plus you can even use ALT+CRTL etc. combos then even more). I'm not sure if it is possible to do that with a regular joystick but I think it should be with JoyToKey.

Apparently I miss something as no one thinks this is a good idea, could you please share what is the trick? or simply everyone has a spare axis for Track IR FOV?

Add a "Zoom in(Hold)" action which will zoom in until it is pressed. When released set the FOV back to the previous value(so not to some default value). The zoom in FOV could be set in a lua file(best would be somewhere in the options menu of course). The zoom in FOV is higher(so less zoomed in) in VR I think then the current "Zoom in" action, which is too much, so it would be nice to be able to configure the zoom in fov value ourselves or at least set it to a reasonable value. This feature works very well in VR and it is so convenient and useful in any situation from looking down to a DDI to dogfighting/spotting. I don't like to use an axis to control TrackIR FOV(so I don't use it at all) and e.g. in the harrier I don't have an extra axis to spare anyway and I have a full CH Products HOTAS setup. Actually I don't believe this is still not implemented, it seemed so obvious after it was done for VR.

I did some test ~3 patch ago it's not the latest patch for sure probably a very old bug. Btw this low signature means in dogfight the mirage just pops one flare and the missile is defeated.

I'm pretty sure it is bugged, on AB your heat signature should be huge no matter what airplane, I suggest you to report it in the mirage bug section as you already prepared a track file, thanks. It is the same for 9M too so it is the mirage(we tested it recently).

When you locked something you get a circle move the target inside, it will IFF. I'm pretty sure this a bug too. And I hope it is a bug too that you have to lock them up.

2-3sec is enough but you have to have the target in front of you. If you use AIM-7 put it in the circle(if you can without loosing lock...). I suggest not to lock up until you have it at your 12 o'clock(this way at least you don't annoy friendlies with buddyspikes too long). Plus there is a bug where you lock the target but it looses lock immediately which results the targeting "info" will freeze(square don't move distance same)... quite annoying.

I use "the big rockets" and they are very effective, I prefer them vs bombs(with single rocket fire you can destroy more targets and you don't have to trim). I can always hit the target, it is very easy to use so to be honest I don't know what are you talking about. Of course dive angle and "in range" is important. Try to do the same with the F-5 :)

+1 I was suprised to see AMRAAM is coming instead of first fixing the radar, this is clearly a bug, there are several threads and video proof about it, it is not working correctly. There are hornet footage too I posted in another thread. With this radar performance no hornet would never shot down anything. I had kills with AIM-7 only when someone distracted the target and I was able to fly directly at it. Plus the radar stucks on the edge bug is clearly a programming fault. Right now the hornet is no match for anything because of the buggy radar. If this gets fixed I think we can live with the EA hornet and wait for the updates but in this state it is very frustrating to fly this plane.

All mine gone too, checked the folder the bindings are removed from the file so we don't have any chance for a hotfix bringing it back.... this is a very noob mistake and for not the first time. Probably I will put DCS on hold too... I wasted enough time on configuring this ....... Eagle dynamics can be happy they already have my money, good job :thumbup: I go and play with the other sim instead (I can't say it's name or my post gets deleted :thumbup: ) .

Lot of people say it easy and I was like I must be retarded because it was very hard for me but compared to the harrier it is hard(so this is for the newbies: it is not easy :D). I play with the throttle too(back and forth) but I still find it difficult, however I can do it almost every time now. I have the CH pro throttle and it has a quite short travel but it shouldn't matter when you "play" with it, the main problem is the lazy engine like 1-3 sec reaction time, harrier is almost instant 0.3-1 sec. I have the zoom problem too so now I approach very slowly(probably too slow) but it works.