Snakedoc

Yes I’ve noticed this as well and can confirm it. If you look on wags videos on the A10C II however the gun boresight and compass tape is visible... maybe he's using a different dev build than the OB

Cool thanks!:thumbup:

in your pics the STPT info in the bottom right and bottom left are both masked partially by the frame of the hud and the image projector, one in the left eye view and one with the right eye view.. how could you be reading those info even in your stereoscopic vision? I get the heading tape which is viewed correctly, but those info above seems to be masked anyway partially

Did you delete your snapviews.lua from saved games folder? If its still there you might have the old view saved as default and you won't get the new one https://forums.eagle.ru/showpost.php?p=4498984&postcount=234

ok so after reading these contradictory messages I went back in DCS and messed around with few settings: indeed the new view point and other updates made it to this build even if they're not reported in the changelog. the reason why the first time I didn't see any difference is because if you have set a custom snap view point like many of us in the saved files folder it overrides the default (new) one in DCS So I went ahead and removed the snapviews.lua in Saved Games/DCS.openbeta/Config/View and bang! the new viewpoint is now available in game I really don't understand why ED didn't include this in the changelog together with a note about deleting your existing snapviews.lua to enable the "fix"... would have made a lot of good publicity and definitely avoid much confusion in many of us! Other fixes that made it in this build that I've noticed so far are: - new viewpoint - left/right click logic changed in many switches - master caution aural warning logic updated - possibily new G-tollerance to buffet onset but have to do more testing - stby ADÌ cage/uncage bug fixed Below 2 screenshot of the "old" vs "new" view, both same OB build without touching any zoom/view point, just had to delete the snapview.lua hope this helps whoever was struggling with this

Thank you for you inputs and help! Looking forward to the V2.0 :D

check this section of the forum which is dedicated to the Raven 1 campaign ;) DLC Campaign Raven 1 subforum also, BD just published an update on his website including workaround to these bugs while we wait for the next patch. Raven 1 campaign status No fix for mission 9 mentioned here but maybe I'll be updated

First of all WOW! What an amazing experience! Flew mission 1 and 2 and the immersion is surreal! Listening to the PA on the deck gave me goosebumps first time I heard that! :D On with this 3d: I found just a minor discrepancy between the brief/kneeboard times and the actual in-game time. There is a 2h discrepancy: kneeboard says LNCH at 8:00 but in game when you spawn in the actual time is 10:00 (all times local) I think ED changed the sunrise time few patches ago and it might have something to do with this. fix for voiceovers and initial trigger First time I played this mission I found that if I wouldn't press the spacebar as soon as the message to do a radiocheck with Saint is displayed this would be removed seconds later and replaced with the message "Press space bar to confirm you have a tone on Saint/ If you're hit by Saint report it via F10 etc.." If you wait until the aircraft is ready and then press spacebar nothing happens (I assume because the game thinks spacebar at that stage = sidewinder tone on Saint). If you press spacebar as soon as the first message (radio check) appears it works as intended but it's impossible to have the airplane ready, especially with the new INS alignment (even the "fast" alignment isn't fast enough). Saint starts to taxi/launch and then shouts at you cause you're out of formation :music_whistling: Also later on during the mission many voiceovers would overlap eachother making it difficult to follow a conversation. Fix: run a a repair on DCS and that's it. Fixed both issues for me:) Just wanted to give everyone a heads up in case you have the same issue. Thank you BD for this amazing campaign! Looking forward to continue it! :D

ED just dropped the trailer on their YT channel the hype is real!! :D

nah today should be the release date for the public hence why is in the patch note of today's OB: ED probably hasn't updated the e-shop yet, my post was supposed to be ironic :P

It's out!!! :D but where do I buy it? :D If I search it on the e-shop I get a message "available to beta testers only"

yep, this bug has been there since the release of the hornet doesn't look like ED wants to do anything about it HUD & MFD Font Symbollogy Thickness [uNABLE TO REPRODUCE] hud and mfcd not really readable [REPORTED] Larger, blurry HUD and DDI fonts there is a user mod which makes the HUD lines thinner by modifying the .lua file but is not 100% perfect and it looks still weird at some zoom levels

From the A-10C II sub forum: however as BIGNEWY said

looking forward to it!! thank you for doing this!!

Just completed mission 1.... WOW! The level of details and how you interact with comms and tasks reminded me of TEW campaign from BD! High quality stuff here! Well done!! Looking forward to play Mission 2 and the rest of the campaign as you release it! PS: If I would change one thing I would have the coordinates given in MGRS form rather than LAT/LONG when your lead is instructing you to navigate to WYP 4 ;) It's quicker and it adds realism. I think in the real military that's how they use it :)

Had the same issue and this fixed it for me ;) https://forums.eagle.ru/showpost.php?p=4239975&postcount=2

I had it while playing TEW 3.0 with the A-10C. I did fly the F/A-18C previously in that session

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 :)