Snakedoc

I am experiencing the same issue with the latest OB build 2.5.6.50979. Funny thing is that when you hit "esc" and get into the pause menu the performance is back to normal! As soon as I resume playing then it drops significantly. This is reflected also in the task manager. GPU utilization drops to around 15% with subsequent huge performance loss after playing for a while, but then when I hit "esc" and pause the game it goes back up to 100% and fps are back to normal :huh: Restarting DCS fixes it

2.5.6.50979 OB seems to have improved the initial loading time. Not quite at 2.5.5 levels but it's an improvement!

I second that! I think it would be a successful way of updating the game and squashing bugs. The hot fixes will focus only on fixing bugs for the existing features while new content will be added only once a month, giving the team more time to make sure they don't break the game if they add them too early :thumbup:

[2D REPORTED] HUD: A picture is worth a thousand words?

pinkie switch (on the left throttle) must be fwd to turn on ext lights regardless of the knob position ;)

some of this makes sense, but then why is the bomb missing the target if lased onto it in presence of strong winds? The study on Deliberate Force in Bosnia posted earlier says that real military pilots back then had issues in dropping LGB in high winds and had to change their delivery parameters to record better hits If you look at my post #40 I tried to change the release technique and lasing-timing reproducing what was discovered in that study and I was able to hit the target without lasing upwind. You need however a low altitude and high speed plus continuous-lasing to give the bomb the energy and time needed to maneuver itself, and this may not be possible during some deliveries (e.g. low-level threats, a/c type, etc) So I think that the lasing upwind technique is more relevant to high altitude, "slow" speed release like for example if you drop it with the A-10C and that's why this technique is mentioned in that training mission. I don't think they would insert such a statement if this wouldn't be accurate and the initial release of that campaign was around 2015. It would be interesting to know where they sourced that information, maybe the original designers of that campaign can chime in? I know DCS has an history of long-lasting bugs but I don't think this is a bug at all. There are also a couple of other threads discussing this where they mention this upwind correction, they are quite old but they exists: What are the wind speed limitations of LGB ordinance? LGB help I'm not saying that lasing upwind is the only technique to be used in case of LGB releases in high-winds, but in some cases it is needed if you don't give or you can't give the bomb enough energy and/or time to correct itself onto the target. Now, what is odd is the auto-set windshear at 1600ft that DCS imposes based on the surface wind which again, in my opinion is somewhat unrealistic. For a surface wind of 30kts, DCS auto-sets a 64kts wind at 1600ft, that is a lot. But this is OT

Yes indeed that's the exact logic behind the LGB. :thumbup: Agreed and that would make sense also if the target would be lased by someone else, you'd just worry to drop the bomb "dumb" as accurate as you can over the target, manually aiming upwind using CCIP. Then once locked onto the laser it would just track the target doing minimal corrections. However, all the release in these tests are done in CCRP and I think the issue is the Release point of the bomb and it's kinetic energy at that moment. When you designate the target using the TGP (in the hornet) to then drop a bomb in CCRP as far as I know it doesn't account for any wind, and the Release Point is calculated with ballistic trajectory. To follow your suggestion you'd have to drop the bomb "late" past the CCRP calculated auto-released point to have the bomb falling ballistic over the target and then use the laser to aim it at the target and it makes sense! In case of strong surface wind, if you drop the bomb at the "no-wind" CCRP release point it may not have enough energy to correct its trajectory with the laser and land downwind of the intended point. If you correct your laser aimpoint upwind it would solve this problem Now I don't know if you can tell the a/c what's the surface wind for CCRP release or if it takes it automatically, I think in the A10C you can but I am not too familiar with the procedure. This could probably explain why in the maple flag mission it says to aim upwind even for LGB, in order to get a "wind corrected" CCRP release point without going into too much details for the wind correction in the CDU. *update* I tried in the same 30kts surface wind test mission with this conditions: 13000ft, M.095, no upwind correction I waited to pass the CCRP release point and then dropped the bomb late (eyeballing it) Continuous-lasing until impact but the bomb still falls downwind of the target I also tried to designate a TGT point upwind of the target to have an accurate Release point cue, released the bomb, slew the TGP back on the target, lasing but the bomb still falls downwind. at this point lasing upwind seems to be the most effective technique to record a hit with strong surface winds under certain release parameters

Very interesting study thank you! I quote some of the text I found on this document related to LGB employment in high winds. As you said no mentioning of aimpoint technique unfortunately p.320/321 p.322 Taken from the above I changed my release parameters on the same 20kts test mission I posted earlier and instead of releasing the GBU12 at higher altitude I did it with the following parameters: low-altitude (5000ft), high speed (550kts), auto-lase 10sec and boom, right on target! interestingly enough then I tried: 13000ft, M.95 release with continuous-lasing (simulating what the F15 crews did from the study did during Deliberate Force in Bosnia) and boom, right on target again. :) I tried next with stronger winds so I loaded up the 30kts surface wind test mission: low-altitude (5000ft), high speed (550kts), auto-lase 10sec, the bomb lands downwind of the target so upwind correction is still a factor here. 13000ft, M.95 release with continuous-lasing, GBU-12 lands downwind of the target so upwind correction is still a factor here. However, I then tried a high speed (550+kts), low altitude (4000ft) release with continuous-lasing and even with 30kts of surface wind, boom! right on target :) upwind correction is not a factor here I guess then it's a combination of factors which depends on various release parameters. In some cases of strong surface winds upwind correction is needed, some other times if coupled with more kinetic energy at the release point plus continuous-lasing technique then is not needed. This is possible on the F/A-18C because is capable of high speed flying, in the warthog however upwind correction is a more incisive factor due to its slower speed. The more you know :)

Agreed on the correction for aiming point, which is what I mentioned before and it is highlighted on the training mission briefing which I posted earlier, I'll attached it here again: It is stating that "Adjust the laser aimpoint one foot upwind per knot of wind. In case of strong surface winds you may have to aim off target to record a hit" I also agree on the concept of lasing too ealry/too late. In the test I am using auto lasing for the last 10 seconds which is in line with the recommendation for LGBs. I have also used manual lasing for the same last 10 seconds but the end result is the same *update* I have also manually lased for the last 20 seconds for longer guidance time in presence of wind and the bomb still falls downwind of the target Now, onto the wind values: Yes, they are storm winds, I am well aware. We saw those winds speeds at altitude in Europe when flying around storm Ciara last winter. Some challenging landings at 30+ kts of crosswind I had to do in southern England and we weren't in any tactical mission, just a regular commercial line flight. With a surface wind in the region of 30kts, winds at altitude veers and increases in intensity, so yes even at 5000ft you can have speeds of around 40-50kts. The only unrealistic setting which DCS weather engine imposes is an automatic assignment of the wind at 1600ft based on the surface wind. If you set a 30kts surface wind DCS will auto-set a steady 64kts wind at 1600ft which is unrealistic in my opinion and in my RL flying experience I have yet to see. Would you go out on a tactical mission in the presence of those winds? Probably not, but here we are talking about a different subject. So: lets repeat the test with more mild winds. OP said he had a surface wind of 20kts, so here is the same mission and track file with the following winds: surface 260/20kts 1600ft 260/43kts (auto-set by the mission editor, nothing I can do about this) 6600ft 265/25kts 26000ft 270/30kts TGP designating exactly over the target (WYP1) CCRP release at 425kts, approx 12500ft with auto-lase for the last 10 seconds. The bomb impacts downwind of the target because no upwind correction was applied, splash damage damages the BTR attached track and mission file for anyone to have a go You don't think or you don't know? I have provided evidence of the wind correction for laser aimpoint based on one of the training missions prepared by Maple Flag. I have no idea where they sourced that information but so far it has been proven accurate and valid. If you have an official (and unclassified) source of information that states that you don't correct for wind with LGB releases I will be more than happy to see it. So far the only published info I could find is the one from Maple Flag mission. GBU12 wind test F18-20kts.trk GBU12 mission wind test F18 20kts.miz

can't wait!! :D

If what you experience is not what you expect it doesn't make it a bug minute 1:21 This is taken from Mission 9 of the AFTQ campaign for the A-10C Correction for LGB lasing is approx 1ft upwind per knot of wind Have a look at some real world wind charts before calling it "unrealistic and nonsense". While not common, high winds at lower altitude do exists and they are directly correlated to surface wind (wind will be veering or backing as altitude increase depending if you're on the northern or southern hemisphere, and it will increase in intensity as your altitude increases) A simple google search will shine some light on the subject if you're keen to discover it I did hit the target on my second pass when aiming upwind. If you look at my F18 track you can see it yourself ;)

I set the surface wind at 260/30kts, what you see in the mission brief is 8000mts. the winds I set are surface 256/30kts 1600ft 256/64kts (this is auto set by the mission editor) 6600ft 286/80kts 26000ft 308/90kts of course I set a strong wind to showcase the concept

Same mission file and track but swapped for an F/A-18C instead ;) conditions are as above, surface wind 260/30kts, course 080. GBU12 mission wind test F18.miz GBU12 wind test F18.trk

technically its a bomb ;) the GBU12 is the laser guided version of the MK82 general purpose bomb, not a missile if you're lasing for a missile (like the LMAV) then its correct, you don't lead for those

try this for yourself: ;) I made even a short mission with a track attached where I make on purpose the mistake of not compensating for the wind. I used the A-10C but the concept is the same, I'll try to do one in the F/A-18C also. **update**: F/A-18C mission and track here - Surface wind is 260/30kts, from the direction I set up the aircraft thats straight headwind. - WYP 1 is co-located with the TGT - I am lasing exactly over the TGT, but because of the wind the bomb is falling short (downwind of the TGT) To hit the target you need to lase upwind. I can't remember which training mission it was where it was explaining this concept but there is a way to figure out how much "lead" you need to give into the wind; I can't remember it right know, I'll update here if I find it **update** See post #25 here found it: Correction for LGB lasing is approx 1ft upwind per knot of wind. Training mission is M.09 from Maple Flag A-10C AFTQ GBU12 wind test.trk GBU12 mission wind test.miz

not quite ;) if you do some research you'll see what I'm talking about

I'm quite sure you'll need to compensate your point of aim for wind ;) i.e. upwind on top of this I see from your video that your target is moving. That will also affect where your point of aim should be i.e. where the target will be at the time the bomb will impact

yeah it seems to be related to widescreen resolutions only but no fix yet... in my case when you zoom in it gets better but then it defeats the purpose of having a widescreen. strange thing is that it happens only with this module, on the A10C of F16C for example is fine

Yes I have experienced the same but unfortunately no track. I will try to save it if it happens again. I noticed that when it got stuck I could only move in in TWS MAN mode. All the other modes weren't working. I manage to "unstuck" it by cycling though various modes, and eventually turning off AA mode worked (I think, as it happen during an engagement with 4 bandits and I was fumbling through every button lol) after it got unstuck it was working like this: TWS AUTO: no movement TWS MAN: elevation movement possible RWS: elevation movement possible Is it correct behavior not to be able to move the antenna elevation while in TWS auto?

same here! Could it be that the new glass reflection issue is also affecting the HUD, UFC and DDIs? Glass effect on instruments broken too It would only partially explain the issue cause the background panel lighting is very dim now, when before was extra bright. IRL however when you turn on background panel lighting on a/c the effect is very subtle and looks similar to what we have now in the sim during a bright sunny day. (never seen a F18 cockpit in real life, but I fly the 737 and I can vouch for that).

THIS!! ^^ I play on a 34' display in 21:9 and I experience the same issue. other 3d reporting the same issue: [uNABLE TO REPRODUCE] hud and mfcd not really readable [REPORTED] Larger, blurry HUD and DDI fonts ED, can you give us an update on this? The thread about the blurry HUD and DDI lines has been tagged [REPORTED] but it's now closed and nobody can post anymore. Correct scaling of HUD/DDI text is a much needed feature for us playing on widescreen displays

Short answer: yes! Long answer: the A10C is probably the most complete and fun module for a modern aircraft which is not in EA for DCS. It will give you lots of challenges and requires some manual studying before you'll be able to fully enjoy it but trust me it is totally worth it! Obviously you need to like ground attack sorties as that's its main function but you can have some fun also in AA engagement. There are plenty of amazing 3rd party campaigns which allow you to fully explore its functions and potentials but you'll need to purchase them. I would recommend 100% "The enemy within 3.0" from Baltic Dragon. Bear in mind that these campaign require a decent understanding of all a/c systems. Included in the module there is a very fun campaign called the "Georgian hammer" and another one called "sturmovik" which are perfect for a beginner and let you explore one by one all the a/c functions. Also there are multiple training missions to learn the basic systems. to get started I would play all the above in this general order: - Training missions - Sturmovik - Georgian Hammer - The Enemy Within 3.0 Good luck and have fun if you decide to go for it ;) *edit: all the buttons comes mapped for the TM warthog so you'll probably only need to adjust the main axis and curves. I don't play in VR so can't answer that but regarding readability I think it depends on your VR headset. The cockpit has been redesigned and retextured recently so you can expect an HD cockpit on par with the other modern modules

same here

DCS 2.5.6.49718 Open Beta hot fix: same issue when launching from CVN-72. 210+kts at the end of the cat CVN-71 is fine

DCS 2.5.6.49718 Open Beta hot fix: Case I recovery mission qualification: IFLOLS overlay doesn't pop up anymore. Run a repair but no change. Any fix? PS: I haven't touched the .lua