jeffham222

So here's a link to the video... Any ideas?

Nothing there when I clicked on it but a description of the building.

Do you mean in ME? The info bit that pops up on the right of the screen when you click an object? If so, I'll check this.

So I just attempted this again. Load out is 2 J82s, a J84 and a J109. J82s were set up for feet for elevation, while the J84 and J109 were set up for meters. One J82 hit it's target, the other missed and the J84 and J109 also hit their targets. It's like the game is AI or something and learns to get better. Nothing changed. GPS Coords were confirmed. Video to confirm all hits. Hit me up if ya wanna see it.

Yes, Sir, I did confirm that. This was my own mission brief that was "triple checked" for accuracy. I used the coordinates off of the Mission Editor map. Harlikwin--Excellent for you! Still jacked up for me. Also, when I put the GPS coordinates in the JDAM mission profile, I also noticed as I was inbound to the target, the diamonds in the HUD were on the ground when I used feet, and in the air when I used meters--which is how it SHOULD show. They just land short when I use feet... I have run several "repairs" as well. I'll try again with a mixed load out of weapons and feet and meters and see what ones hit and fall short. I am confident I will see the same thing.

Negative, Grease... INS alignment is good to go.

Yeah, I have video of all three hitting 100's of feet short. It's a mystery to me why my bombs are all off. I have the latest OpenBeta update--2.5.5.31917. I was dropping from 20k' at about 350-360KIAS. To get the most accurate Lat/Long, I zoomed in to 10' on the map in ME and put the cursor in the center of the target. Verified Lat/Long on JDAM Mission page before taxiing. Also, I'm using the "Precise Lat/Long" under "Misc." for "Coordinate Display" in settings. Would mods cause this? I am running the Echo (I think it's called) engine sound mod, and have some custom skins I'm running... I wouldn't think this would affect it at all...

Yeah, it seems kinda steep...

Nice, dude!

That was exactly it. I don't know how that got checked. I certainly didn't do it as I had to search for where to find it! I hope someone may be able to verify that the new patch didn't switch this automatically somehow. PS--Thanks, Whaaw!

For potentially more info (though a bit different--hope it doesn't add confusion)-- I had a similar issue where if I weapon designated the target's way point on the HSI, the seeker head on the missile would snap back up to the caged position after releasing the TDC button when attempting to lock up a target. I had to deselect the weapon designate option on the HSI for the way point to make the seeker head travel properly and lock up a target I believe after I restarted my computer, it worked fine with the way point target designated. BTW, I am using keyboard arrow buttons to slew the seeker head while pressing the TDC button on my throttle.

So I got back on it, and moved the targets from a little valley and into wide open spaces... Out of 8 LGBs, 3 hit--one miss was because I screwed up and forgot to make the "IN" call, but the other 4 were all something else. Tried checking out then checking back in. First time I dropped after a good shack when I got the "shift" call from AFAC, didn't realize what it meant and missed on second pass. Next round hit. Shifted and a miss. Meh... lots of time for lots of missed ordnance. Guess I need more hours. Does anyone else have issues with multiple targets at the same WP?

They seem to be tracking... "better"... Also--and I don't think it matters--I set the speed of the WP to as low as it would go (~126kts). Does the TYPE of WP matter--eg, flyover vice turning point? I didn't notice any "swaying", but I may have gotten to the wep view too late... so probably just the ballistic arc. Everything seemed good to go from the AFAC. INS and everything else was good to go as well. Thanks for the assistance this far, Backspace! I gotta go to bed--work tonight--but I'll be on again after work to sort this pig out!

Had that issue, Fisherman... Ok so I set the altitude of the WP to the ground elevation, still off, but sort of close... only a quarter of a mile off now! Lol...

Yeah, it was set to about 18k'... I guess that could make a huge difference, eh? Lemme go try and fly this pig again and I'll report back in a bit...

Ok, so I had the same problem... I think I MAY have a fix--or at least this is what I did and it ended up working... I repaired the OB install, restarted my computer and went back into my mission I created (a simple cold and dark start-up in Nellis). Started up (there was some lag in ground crew vox--responding after they had attached power and air), extended my nose strut (is this a real world thing? I followed Jabbers tutorial and took notes on everything he did and this was not one of them), then selected NWS and went to an outside view to see if the nosewheel was turning. It wasn't turning that much. But when I added power and got rolling, I had full NSW steering authority. I'll also say the first time I tried this prior to repairing the install and restarting I went into full AB and didn't move one bit. I also had zero external lights (which is still unresolved), but I'll be looking for a fix to that in here.

I agree Atsugi... Just sit in it and play with all the stuff... lol... So it's looks like (if Backspace340 is correct) at least another hour and a half here at the least until we get it... So stoked.

imacken--nice review man--I really appreciate the blunt and frank honesty!

Roger, Wags... I'm also checking with guys I served with for full-on correction!!! I figure I might as well get slammed real-world... I'll also get into the pubs next week at work as I should know this... but am missing it. Thanks!

First, I am not trying to start a fight or bicker or anything... Even though you seem to be an AME, apparently (former AT, myself)--lol... I follow what you say, but I think that is jumping to conclusions, maybe... especially about initiating Fire Loop B after Fire Loop A... and there aren't "tapes" to my knowledge--it should be all solid state/flash tones/bitchin' betty... Maybe a processing issue with MCs as they ARE slow compared to (even back in ~2000) PCs. It HAS been about 15 years since I worked on my turn qual on F/A-18A-F's, but I don't remember this being an issue. Rather, I believe the issue is with the actual wording getting reversed randomly and either on Fire Loop A the first time I ran it or on Fire Loop B right after I ran Fire Loop A in the DCS sim itself--I'll check with a former ADCS buddy to confirm though to see if this is actual real world and shall report back. To clarify, sometimes it works both loops first time up, but others, seems like it doesn't, so even before verifying, I will give you that... I know I usually jump in the cockpit and get right at it. Regardless, if I am wrong, I will admit it. I've been wrong before and the goal of this post is not to put my junk against anyone else's, but to find out what I may be doing wrong. Thanks, for the feedback, AMEDooley!

Can I get an explanation of what I am doing wrong since sometimes the Fire Loop Tests say the correct thing and sometimes they don't?

Set up tanker mission via mission editor last night (before the OpenBeta update to 2.5.4.28090), used default TACAN of 1X and it didn't work--got spinning TACAN in T/R. Punched in 1Y and it seemed to work fine. Will try with new update to OpenBeta.

Awesome, imacken! Looking forward to hearing your comparison review! Also, some1 is on point with that meme!

Man I would say if you are happy with what ya have and they work as you'd expect, stay with it! I don't have any rudder pedals, which is why I posted the question. Speaking of that, thanks for all the input from everyone! I look forward to more input/comments etc!

For that much money (really anything over $100) without toe brakes they are useless, IMO. Do any of you guys run the TM Warthog stick and throttle? Had any issues with everything being programmable? I read where if you used the TM Warthog stick and throttle you ran out of something or other needed to program all the peripherals due to DirectX limitations...