Eagle7907

Is there any plans to allow in mission editor where planes spawn at the current spawn points? If we had this capability it would allow us mission builders to have more control in how the AI won’t cause problems when taxiing on the deck. It seems even when spawning at the default position you still have problems. Currently, this makes the SC seem more intended for MP than SP. Sent from my iPhone using Tapatalk Pro

mission files This happens both in F-14 and F-18. I have both files below. https://www.dropbox.com/s/1wb1b7vkliazygp/F14%20carrierops.miz?dl=0 https://www.dropbox.com/s/53gscu0z4pbmk9g/F18%20carrierops.miz?dl=0

With the SC release, I’ve been experimenting creating a crowded deck without using static objects. I’ve discovered that currently with the latest OB dated 5/20/20 that if you have AI selected ‘Uncontrolled’ from mission editor: 1) starts the mission 2) then opens mission planner and changes loadout 3) then closes mission planner 4) clicks start 5) then fly The ‘uncontrolled’ option becomes broken and AI default back to being immediately controlled and move about the deck. If the player repeats this process without entering the mission planner, the AI selected as ‘uncontrolled’ remain in the selected state. I’m thinking mission planner may break other set commands or options as well. Please investigate further. Sent from my iPhone using Tapatalk Pro

That’s what she said. Feel free to scroll through the endless opinions. I left mine and I haven’t gone back. That’s what that whole thread is. The opinion deposit. Sent from my iPhone using Tapatalk Pro

I think Kate said she will look into refunds if they don’t deliver in the two week timeframe. Sent from my iPhone using Tapatalk Pro

TWS-Auto Sent from my iPhone using Tapatalk Pro

Thank you. Still think about him. It was pretty sudden, too. Went in for just feeling ill, three weeks later, gone. Wasn’t covid19 for the inquiring. Sent from my iPhone using Tapatalk Pro

Last I heard, don’t use the “jester automatically uses PSTT”. It was found that this may cause a loss of lock and last I heard of as being looked into as a bug. My technique is to manually tell Jester to switch to PSTT and just keep the bandit higher than you. Don’t let him descend lower into the ground clutter. Also, be aware that there are times when you tell Jester to switch to PSTT, he will acknowledge it, but will not actually switch to PSTT. It is a bug. It’s best to always tell him to switch to PSTT. Then go back to Jester menu and see if it changed. It will say “switch to PDSTT” if Jester did do what he was told. If he does not switch, unfortunately you can hop to RIO position and you’ll have to STT lock then press the Pulse STT button. Good hunting! Sent from my iPhone using Tapatalk Pro

When they were first introduced on the Hornet, Wags videos mention about carrying speed of around 500kts in the dive and dive angle of around 20-30 degrees is how to get consistent results. Going outside of those parameters seems to show inconsistencies. Sent from my iPhone using Tapatalk Pro

My condolences. I had to do the same last month. Hopefully you’ll have a better outcome than me. Sent from my iPhone using Tapatalk Pro

Excellent idea. Ran into this problem a couple of times. Sent from my iPhone using Tapatalk Pro

Great write up guys! I can see why a complete revamp was decided upon. Very complex! Question though. When can we expect it next? Sent from my iPhone using Tapatalk Pro

Obviously. Thanks. Sent from my iPad using Tapatalk Pro

And the article about TWS-A. Mentioned an article being done in a few days. Sent from my iPhone using Tapatalk Pro

Hey Mike, Any insight on fixing Jester not switching to PSTT when commanded? I reported this back in, I think, September or October. Didn’t really see it mentioned above. Thanks! Sent from my iPhone using Tapatalk Pro

Haha. That’s great. Thanks BigNewy. Sent from my iPhone using Tapatalk Pro

April Fools! Humor is a tricky emotion. This is why my work recommends we don’t include humor in PAs to passengers. To some it might be funny. To others it might not. As for this Easter Egg, I don’t mind it. It’s cute. I’m curious though, will it continue this until the next update? If so, is there a way to disable it? Sent from my iPhone using Tapatalk Pro

So I did the mission again keeping trusty Swift's remarks in hand. It does appear he is correct. To account for the differences between the two target designations is the fact that the first is too far away for the Maverick seeker to lock. The second one is closer and therefore tracking a vehicle once the new target spot is designated. See below: I then undesignated, flew closer, designate again and watched the maverick video slew and then lock on one of the vehicles. I had much better success with the LGBs. The trick it seems is to keep updating the release calculations since the CCRP(or AUTO) point is based off of a stationary point. After release, I almost immediately start to lase. This way the bomb has plenty of time to correct its trajectory and make contact. This is a PITA for the Hornet. It seems like the best technique is to not use the TGP at all if the target is moving. Is there any better technique? Oh, LMAVs. But that's not good for killing defenses.

Mavericks slaved with Tpod Hey swift. I understand if that is the case and you may be right. But when this happened it was instantaneous. The “points”were way off by a pretty big margin for targeting. It’s not like I designated and waited a minute to slave the maverick. That also doesn’t account for when I undesignated waiting to get closer then designate again and they both matched. Sent from my iPhone using Tapatalk Pro

Hey all, I had another interesting find on OB the other day. I was doing a mission I created where I can attack moving ground targets using LGBs and Mavericks and a TGP. When over a waypoint the distance to where the convoy is moving is about 20 miles away. When I acquired the convoy on the TGP on the right DDI with the Mavericks video on left DDI, at great distance the cameras are not looking at the same point. I had the TGP zoomed in as far as it would go on a tank, but the Maverick would be looking slightly away from the convoy and to the right. I had to undesignated and designate again when closer because I couldn’t get the Mav to lock. (Standby for images and track.) Sent from my iPhone using Tapatalk Pro

F-15E? @Decoy Here. This post is dated 2015. He says he found posts about it dated further back to two years. By that logic and what has been happening with other modules and this one, we were at the halfway point. The rest was already explained for early access. Please explain how this is not correct. Sent from my iPhone using Tapatalk Pro

Seven years to get this far. I think it will be another 7 years to be completed. Take about 3 or 4 off that for early access. Sent from my iPhone using Tapatalk Pro

TWS Auto Coming Soon If you watch the video on YouTube you can see the altimeter climbing at a pretty decent rate. Basically TWS will work like the Hornet or Viper. You can maneuver the full azimuth of the radar. It’s good. Not sure about elevation. I’ll have to research that. Sent from my iPhone using Tapatalk Pro

TWS Auto Coming Soon It means you can beam up to the full azimuth of the radar while providing a track for multiple Phoenix launches. Currently you only get the fixed azimuth on TWS manual. Basically you can beam like the Hornet. Sent from my iPhone using Tapatalk Pro

Nice thread. I’ve been pondering this myself for several months. Sent from my iPhone using Tapatalk Pro