-
Posts
11788 -
Joined
-
Last visited
-
Days Won
59
Content Type
Profiles
Forums
Events
Everything posted by Wags
-
Weekend before last I spent a good 8 to 10 hours online on various servers (under an alias). I did see this on a few, but with others I never saw it. Given this, I suspect it has something to do with how the mission was created. I'm afraid though that I don't have an answer yet as to what mission creation variable is causing this for some online servers. Thanks
-
In initial testing, the deck crew and carrier model have very little impact on performance. The bigger impact can be the number of aircraft the mission create places on the deck. Even with a crowded deck, I've never had a "slideshow". Thanks
-
It would be quite silly to copy and paste the JF-15 AG radar as it operates quite differently than that of the Hornet. However, the JF-17 uses the AG radar API we created, so it will look quite similar. Thanks
-
I don't think putting targeting pod work on hold so we can push on AG radar would go over well... to say the least. Again, we need to focus on priorities, and the targeting pod improvements are critical. Thanks
-
Actually, if you go back and review past newsletters, that is exactly what we did. Thanks
-
[MISSING TRACK FILE] Radar arc on HSD not displayed properly
Wags replied to QuiGon's topic in Bugs and Problems
Thanks for the report, but it's working okay here. A track file showing the error for you would be helpful. Thanks -
It is a "must" to be addressed for the project release. Thanks
-
We originally had a Supercarrier project with a much narrower feature scope. We decided to put in the extra time and money to create something special. The deck crew and full carrier comms were greatly expanded. Thanks
-
Hi, Based on client feedback many, many more are looking forward to further AA radar and TGP development. Also, for aircraft like the Viper and Hornet, the AG radar has very limited utility these days. Most of the AG sensor work is done with the pod now. Thanks
-
Hi Cinatra, The strategy is simply based on priorities. The current Viper and Hornet priorities are the AA radar and TGP. AG radar is lower priority. We'll get to it though. Thanks
-
Colt 11 and Colt 12 are the donors that were telling you of those contacts. Thanks
-
Colt 11 and Colt 12 as the donors for a contact on the FCR. Thanks
-
In our march to added TWS on 18 December for the Hornet, we've now added SCAN RAID and EXP (Expand) sub-modes to TWS. Expand (EXP). When there is an L&S target in TWS mode and EXP is pressed, the display will change to a 10 nm range with a 20-degree azimuth scan. The display range on the right side of the display will indicate the 10 nm scan area (for example: 30 at the top and 20 at the bottom). Despite the 20-degree azimuth scan, the legend will still indicate the previous setting and the b-sweep line will not freeze on the L&S. This mode simply zooms in on that area, but the TWS scan operation, target rankings, etc. does not change. Filed tracks that are outside of the display will be on the edge of the display and flash. SCAN RAID Mode. This is selected from the SCAN RAID button on the throttle and it concentrates the TWS scan to a small area to break out closely spaced targets. When enabled, the scan is centered on the L&S target. It is displayed in a standard range and azimuth format in 10 nm zoomed in display at 22-degrees of azimuth, with a 2-bar elevation. The b-sweep line is frozen on the L&S target and SCAN RAID appears at the bottom of the display. When in this mode, track files and raw hits are displayed. If a new L&S target is designated, the RAID SCAN will move to that location. Filed tracks that are outside of the display will be on the edge of the display and flash. When selected, AUTO scan centering is automatically selected and cannot be unselected while in this mode. --- We will continue de-bugging these and TWS as a whole, and we still need to add L&S HUD indications when in TWS. Thanks
-
I should have been more clear. The brakes were set by the available charts and then the SMEs confirmed that all looked fine. We try to double check such matters. Thanks
-
I’ve had a couple F-16 pilots take a look at this for me and both indicted it was fine. Thanks
-
10 nm is an average range and the range and lock times have been adjusted for the next update. Thanks
-
Hi everyone, A little update on TWS for the Hornet... Progress has been very fast with the remaining items just being: 1- L&S HUD steering 2- Expand (EXP) sub-mode 3- SCAN RAID sub-mode Other than that, it is functionally complete, and certainly on track for later this month. Thanks
-
I've asked our project lead to re-examine. Thanks
-
We have the no-kidding rate charts for CAT III and they match. Thanks
-
Feel free to PM the source and we'll be happy to take a look. Based on our current documentation, there is no such language. Thanks
-
While I was able to reproduce this in your track, playing the same mission in our internal version did not reproduce this error. Please try again after the next OB update. Thanks
-
With an AoA limiter of 25 degrees, there should be little shudder/shake. We've confirmed this with multiple Viper pilots. When you attach a camera to the aircraft, any shake gets greatly exaggerated in the video playback. Thanks
-
Thanks. We have duplicated this and it will be resolved.
-
It's modeled correctly thanks.
-
For some ALRs yes, but NOT this one. We have very good and clear information on this matter. there is zero mention of signal strength as a display factor. Thanks