maxTRX

Around the immediate area of the lamps, not as a reflection on the surface 30m away. I'm currently on vacation from DCS so I'm not sure what's going on in that department, MT or ST.

I'm not sure how Wine does it. One thing I know is Windows time base was local, Ubuntu is UTC. When I had a dual boot setup on my rig (Ubuntu's Grub as bootloader), logging in to Windows after using Linux always caused time shift to UTC. All I had to do is sync it again. I got tired of this so I my buddy ChatGPT to show me the command line fix for this... not a big issue. Something tells me that this error 500 would still pop up

So, the modified file from the 8th was still giving you the warning? Yes... I know, you already 'repaired' and running. Just curious.

I'd be even more grateful if one of the internal testers pretended they are like the rest of us and before each update link up to the same d/l servers that we connect to and do a test run, before making updates available to the public (the real OB testers )

Like the baldie from davos said: 'You won't own anything and be happy'! I just had to...

I'm glad I held off from updating. Whether it's bogus or real... they need to straighten their s*** up. Well, I'm going to extend my little vacation from DCS

I actually did some of the test runs within seconds of each other: say, level run at 4k ft AGL, 480kts, followed by a quick climbing turn in the oblique, back toward the target, rolling out on a 40 deg dive, release at 4k AGL, 500kts (on rails). FLIR ranging in level, AGR in a dive. If any gyros were out of whack, it would be obvious in both drops. So, you don't see any issue with this on your rig, Tholozor?

OK BuzzU, we are all going in circles here, lol. I was never comparing accuracy of AUTO mode (Hornet term) vs. CCIP. I simply stated that using CCIP gave me an option to use my clumsy, fat thumb to release the bombs a split second late, in 30~40 deg dive. This way, instead of hitting short, I was correcting for inaccuracies of AUTO release cue computations (DCS thing). All systems aligned, GPS autocorrected (always on), AGR or FLIR ranging. Again, releasing the bombs from a LEVEL flight using AUTO mode, produces no error. Just about all hits dead on. I have no idea why the Hornet's computer can't do the same for dive or loft attacks. If the bombs get effected by the release angle, the computer should know that. Well BuzzU, the testing is on you now... take as long as you need to. My DCS install has to go TDY for a little while. I'll be checking the forum.

I'm with on that one... instead of silly dots, maybe some better (darker?) transition texture. This reminds me how hard it is sometimes to spot a grey jet from the ground or even the air, at around 3 ~ 4 miles away, in the sunny, blue sky. Sure, looking at the right part of the sky we can spot a small (non-smoking and non-reflecting) jet from a descent distance, look away for an instance and it takes a few seconds to spot him again, if lucky and a 10/20 vision , had it for a while... not anymore.

Just checked it, in the bright daylight. The Hornet with its position and strobe lights on, still looks like a glowing orb from miles away. I'm not talking about the strobe flashing on and off. The strobe is actually invisible from distance, overpowered by a 'blend' of steady position lights, especially annoying in VR. Dots or no dots... just tell the Hornet drivers to keep their ext. lights on and the spotting is no problem, even in bright daylight.

I don't know. I haven't flown the Hog in years, stubbornly sticking to Hornets. I might fire it up some day... gonna have to configure the controls again, from scratch.

There is also another reason why using AUTO in the current version of OB gives us advantage over CCIP, TD box on the target. Some time ago, we had an option to use CCIP over ground designations... very useful feature. The guns in CCIP mode can still be used on designated targets. Some people claimed that this can't be done in RW Hornet... for whatever weird reason. Having an option to switch to CCIP and still have a TD box visible was a tremendous help with SA. Why would I want to switch? Simple... AUTO mode was and still is causing short hits when diving. In CCIP I could press the pickle just right to compensate... As mentioned earlier, we do what we have to do to go around bugs. Now, at least in my tests, the level release is the winner (AUTO or CCIP) hence the title of this thread. Well, we're way beyond that, which is fine. A few OB builds ago, lofting in AUTO was the most accurate for me (at around 500kts). I liked it since I was able to sneak in and throw the bombs up at the target and drop down again quickly. ED makes these discrete changes without any notice and we have to play test pilots to find out.

I don't understand myself sometimes either... I just imagined some basic trig. What if the mission computer gave you a crab angle at some point after initial that would put you on a steady path (course) that would guide you toward the release point (already calculated roughly with ASL glued to it) for your a/s. Now, hell if I know how this worked in the ol' Hornet . One thing for sure, RW or game. In very rough weather, this type of weapon and attack direction would be iffy at best.

Now I see what the issue was when it was reported long time ago... the ASL doesn't show the lateral offset required 'at release point' and it gradually and constantly creeps toward the target as it gets closer. Currently, we have to anticipate and lead the ASL just before release. It creeps rapidly at very close range. So... it's pretty much 'Kentucky windage', ;). This become very obvious when dropping high drag bombs. When aligned with the wind, no problem. At 90 deg., stay ahead of the game. Yea, I still used 40 kt wind, I guess I was too lazy to change it. So for now, it's probably better to figure out an ingress route and attack direction more aligned with wind. Another thing... I released at only around 450 kts., since I wasn't sure if DCS factors in the limits for any kind of HD bombs or not.

It certainly acts different, well in my opinion. I haven't tested high drag setup yet, perhaps today. This scenario should definitely require different approach.

I think you'd be better off getting an explanation from a youngster... I'm probably not that far behind you but who's counting . Short explanation: Hornet weapon systems, JHMCS, release calculations and 'few' other things are still partially borked up... Sure, there are always ways to adjust to the bugs and develop your own ways to 'WIN'. From that angle, hackers are the most powerful weapon... Well, we are both too old to start on that path, lol... or are we? (jk)

OK, I had enough time for one test run, before my Reverb G2's cable started showing signs of wear and tear... well, it's the original one. Rockeyes x 4, 40kt wind. In the first attack, almost perfect tailwind, second run at 90 deg. Perfect hits both times. I left the burst ht at 300 (whether it matters or not). Well, the thread is drifting off a bit but ED doesn't pay too much attention anyway,

No, not yet... I wouldn't expect the same results though. With the same wind condition, the attack direction would 'probably' be a major factor, along with release altitude. Hopefully I'll have some time to run a test today.

You know what... after you brought it up, I went and tested it. Hmm, it looked a lot better now, as compared to an identical test I'd done over 2 years ago (damn, time flies!). The winds of course have to be set within certain limits... We can't use dumb bombs in 80 kt. crosswind component, well even smart bombs might have an issue... I tried it anyways, lol - no dice! OK, in my 'normal' test I had a 40 kt wind from my left 90. (same wind @1600ft, 6000ft and above) Target elevation was 4400ft. I released from a level flight at 9000ft, just below 500kts. I didn't worry about heading caret vs. tgt diamond on heading tape... seemed OK to me (I remember some folks reporting issues with that part in the past). Simply lined up VV on the ASL without making any major corrections as I approached release point. Spot on! As long as I released from level flight, nailed it every time. Some people might say that was a bit too optimistic? Not me, lol. I was happy. Now, releasing from a 30 deg. dive was always short.

In the latest OB, level release still rules, anything else is way off.

Regardless of designation method (FLIR, HUD/HMD), the TD box goes bonkers after couple of violent maneuvers. WPDSG (w/o correcting by slewing and re-designating with TDC) seems to be more stable. This target was designated by TDC on ATFLIR pod. Anyone else on ST DCS latest OB?

Hehe, it sure does. We all get there... well, the lucky ones do. Mission Computer should keep all sensors on the 'same page'. That elusive sensor fusion is not quite there yet.

We're past that point already... I'm running the game with SatNav box checked now. Why? I explained in one of the posts above. This thread started blooming into another issue, again... described earlier, just before I was offered to watch "How to improve my aim 10 x' Looks like it's time to lay off for a while and clean out my install.

No, that's not it.