Sublimearrepentido Posted May 3, 2020 Posted May 3, 2020 Ok in a DCE campaign. I was going to strike a EWR site. The waypoint for ip and surface target... were on point in f10. But led me way off if i followed the waypoint cues I had jester make a fixed point and other stuff. Its worked before endlessly. Not this time. No matter what I did I could not get that damn plane to see a waypoint in the right spot. It was convinced the WP and others were like 20 to 30 miles n9rth north east of where we were. It was very odd. No hard dogfighting or jinking before. I let jester do his set up and the plane was wired in with the carriers INS. Its worked every other mission. Hm. Ideas?
QuiGon Posted May 3, 2020 Posted May 3, 2020 Nav drift? 20-30 miles seems a bit too much for nav drift, unless it was at the end of a very long flight (multiple hours with air refuelings). Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
MBot Posted May 3, 2020 Posted May 3, 2020 Probably caused by carrier deck sliding, which breaks proper INS alignment.
Sublimearrepentido Posted May 3, 2020 Author Posted May 3, 2020 No not long flight. The entire mission would probably be 1 hour tops. The nab drift was noticeable after 15 minutes in the air it was clear the waypoint I was being steered to wasnt where the f10 was showing. I still have a copy of the campaign generated mission. I will report back after a nap (lol) and see if the problem repeated. I did cat off a deck but dont remember much sliding. I started noticing about 40nm off the coast I seemed... headed the wrong damn way. Sure enough when I got way closer.. the EWR site was off even from the waypoints I set using f10 on the location of where I knew the site was. The whole thing was so weird. If the problem happens again and anyone wants the mission I can send it.
overalien Posted May 4, 2020 Posted May 4, 2020 Same issue. Hsi points off by 15 to 20 degrees to target but the lantern and TID remain spot on. Sent from my iPhone using Tapatalk __________________ overalien Hog Driver starting to really like the Tomcat System specs: Intel i7-8700k - OC to 5.0 GHz | 32 GB RAM 3600 MHz | Nvidia 1080ti SLi | Mixed Storage - Win 10 and DCS on Samsung SSD 970 Pro Flightgear: 7 Displays (3 x 1440p, 1 X 1080p, 3 X Lilliput Touch) | 3 x Cougar MFDs | Warthog HOTAS | Thrustmaster TPR Pedals | iBEAM Shaker + Simshaker for Aviators w. Sound Module | Helios | VAICOM Pro + AIRIO | TrackIR 5
Bearfoot Posted May 4, 2020 Posted May 4, 2020 I've noticed this as well. Thought I was doing something wrong. If so, it seems like I am not the only one!
Sublimearrepentido Posted May 4, 2020 Author Posted May 4, 2020 Same issue. Hsi points off by 15 to 20 degrees to target but the lantern and TID remain spot on. Sent from my iPhone using Tapatalk Really weird! Ive been able to recreate it I reflew last night. Following the ghost steerpoints took me almost 100 miles NE of where I was supposed to be. Crappy thing? I actually manually flew back to where the real ewr site was, found the 3 rinky dink little radar trucks and started lazing one just to catch a SA8 to the face. Allegations of a rage quit are unclear at this time
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 Bump Heatblur or someone else Is this a dce issue or a game bug. It happened 2x in the same sortie AND in a totally different sortie altogether. Ims.pretty sure if you simply edit the 80s tf68 toninclude strikes youll ommediately notice the problem we are having. I dont see it being dce - why does LANTIRN know the correct WPs? Why wont adding new map WPs do ANYTHING?
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 Ill add I reflew the night sortie 2x to make sure i hadnt hard maneuvered without knowing. The day sortie actually now I think i flew 3x! This is a def problem and the others chiming in.. someone!?
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 Those missions were the first time I ever felt the air frame failed me and not thr other way around Ordering wingmen to engage target and rtb or rejoin .. did nothing
sublime Posted May 7, 2020 Posted May 7, 2020 Ugh look at other thread. Somethings up with the nav or the dce. I think something just broke the f14s nav
sublime Posted May 7, 2020 Posted May 7, 2020 You know what? Im gonna try catting off a different part of carrier. Who knows.
sublime Posted May 7, 2020 Posted May 7, 2020 I tried from diff cst and it works fine.. gotta try to find out if its samenon dce
Kondor77 Posted May 7, 2020 Posted May 7, 2020 Are these waypoints part of the mission itself or are you marking spots in the F10 map then telling Jester to type them in? I've had issues before when marking multiple spots in F10 map, then telling Jester to type them in, all at once. I've found that if I tell him to do one at a time (wait for him to finish inputting a waypoint) I can assign him the next one, etc, etc and it works fine.
Kondor77 Posted May 7, 2020 Posted May 7, 2020 Are these waypoints part of the mission itself or are you marking spots in the F10 map then telling Jester to type them in? I've had issues before when marking multiple spots in F10 map, then telling Jester to type them in, all at once. I've found that if I tell him to do one at a time (wait for him to finish inputting a waypoint) I can assign him the next one, etc, etc and it works fine.
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 Originally part of mission itself I try marking as desperation later. One mission was striking EWR onnthe coast with 500 lb gbus. Following the wps it became obvious It was taking me about 20 miles NE of target! Second time at night. Ewr strike. Deep though. This time 100 miles Northish of target! Before I stopped following
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 Yes Ive noticed flooding hester with wayloint input commands cab mess it up I even allowed for some sudden hard jink i mysteriously dont remember. But I flew both 5x times easily because I maddeningly could do the job if the waypoints were just right! Posting this and seeing others agree sealed it for me
overalien Posted May 7, 2020 Posted May 7, 2020 Are these waypoints part of the mission itself or are you marking spots in the F10 map then telling Jester to type them in? I've had issues before when marking multiple spots in F10 map, then telling Jester to type them in, all at once. I've found that if I tell him to do one at a time (wait for him to finish inputting a waypoint) I can assign him the next one, etc, etc and it works fine. most of my issues came from a single ST waypoint off the map given to jester to enter after alignment and before taxi. __________________ overalien Hog Driver starting to really like the Tomcat System specs: Intel i7-8700k - OC to 5.0 GHz | 32 GB RAM 3600 MHz | Nvidia 1080ti SLi | Mixed Storage - Win 10 and DCS on Samsung SSD 970 Pro Flightgear: 7 Displays (3 x 1440p, 1 X 1080p, 3 X Lilliput Touch) | 3 x Cougar MFDs | Warthog HOTAS | Thrustmaster TPR Pedals | iBEAM Shaker + Simshaker for Aviators w. Sound Module | Helios | VAICOM Pro + AIRIO | TrackIR 5
Bearfoot Posted May 7, 2020 Posted May 7, 2020 most of my issues came from a single ST waypoint off the map given to jester to enter after alignment and before taxi. Same.
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 I had similar issues. However I tried it without editting anything and with the default mission settings youre still sent wildly off. Once it showed on map we were flying to.. nowhere. I editted the map then. But Im 100% one sortie I didnt alter anything until I was 30 plus min feet dry over russia and 100 NM North EAST of my target before I desperately started punching in steerpoints. Its the first time in my life in the F14 I felt let down somehow by the airfrane and not me. Im over friggin RUSSIA and my goddamn INS is telling me the wrong stuff and I cant follow my idiot wingman. What a mess. Ok so i said I flew eacha few times. One was daytime coast EWR 2nd was ewr site 501 its inland and more to the south. Anyways I know also on 2nd mission ANOTHER retry involved having jester, slowly one at a time.listening to him.enter numbers (AND ANOTHER WAITING UNTIL IT SAID 8 MIN AGO FOR EACH!) and still waaay off. Hiw the hell does LANTIRN know thiugh? Finally I also did the taxi; but usually I dont mess about with that. Dont get me wrong. Ive tried it. But normally now I leave everything alone except startup until airborne and climbing. A guy miguel21 who got dce working for me ( @miguel21 ) said Mbot and him encountered similar problems and he solved it by waiting for the CARRIER TO MAKE A TURN INTO THE WIND. Can anyone verify how Id even know how this happens? He said Mbots got a script for it. Look under dce campaigns in user made missions and canpaigbs. Guys this is either a bug or dce bug but back me up on this fellas dont let it just die
Sublimearrepentido Posted May 7, 2020 Author Posted May 7, 2020 To be clear @Kondor77. The first time I encountered this bug I flew the entire sortie according to mission plan. And ended up wildly off course. So wildly off course and discombobulated I quit after 15 minutes of mucking around. About 15 sorties later (6 or 7 in that alone ) the next strike error happens. I was making jester wps. Some on xarrier most in flight always one at a time qnd slowly. But one of the sorties I sakd "f it maybe its me lets see where it takes me" Lets just say when I was overflying the Caucauses Mtns near Mozdok over 100 miles from the coast qnd 100 miles N Eastish of the target that I started manially flying by using kneepad and the mark location cheat
Sublimearrepentido Posted May 8, 2020 Author Posted May 8, 2020 Ok bearfoot and overalien can you please try a strike mission where you dont mess with the WPs so I dont seem like the omly one? You guys did note Miguel21 said it had to do with the carrier turning and Mbot had a script right? Miguel knows his shit
Sublimearrepentido Posted May 8, 2020 Author Posted May 8, 2020 Fellas I got the answer. If you were flying TF 68bor a new DCE mission. The carrier detects or the script derects a new plane. The cardier turns to the wind. May take 1 to 5 min. The advice is this - DONT start your engines until you see the bearing in your backup compass stop turning. Then begin! Hered the quote Hi, The Mbot file is this one Saved Games\DCS\Mods\tech\DCE\ScriptsMod\Mission Scripts\CarrierIntoWindScript.lua As soon as the script notices a spawn or an engine start or the presence of an airplane at less than 6000ft and 20km: it rotates to get into the wind (as in real life). It takes about 1mn to 5 mn, depending on whether he has to make a 5° or 180° turn. What I was doing: I'm calling ground crew to connect Ground Electric Power and Air Pressure I'm looking at the bearing on the BDHI When the bearing is steady, I start the engines and Jester starts INS alignment.
Sublimearrepentido Posted May 8, 2020 Author Posted May 8, 2020 Gentlemen its solved thanks to miguel21 Dont touch your cat. Hit f2 or watch in cocnpit backup compass. Give it 5 min tops. The carrier WILL stop turning. Then start up!
Recommended Posts