-
Posts
3927 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Everything posted by Kev2go
-
F100D "late" isn't really a new production, but a culmination of post production refits that occurred around past a certain time frame. Its nice to get different versions although late model i would think is the best option because who doesn't want a hun with an RWR? I also take consideration for capabilities that will make it more appealing. BUt ideally it since to get multiple version of the F-100D because not much is changing apart from come internal avionics like addition RWR, coupled with some rearrangement and replacement of a fewpanels pertaining to armament and such. Nothing that will impact flight model. Its not just 3rd parties like HB that are making multiple versions of a an aircraft family. Even ED has don so. I mean look at the L39. We got two version C and ZA and those were more significantly different, and for the P47 ED is making 3 versions of it. D30 Early, D30 late ( what we have now in EA) and D40.
-
so relative to the 1993 manual that Razbam had refereced as a source years ago, ( and the one i happen to have copy of) What did suite 4 introduce in 2002-2003 period? GPS aided navigation plus JDAM? link 16? newer targeting pod like litening 2? ( was referenced as an interim solution for a brief period until Sniper could be fielded)
-
i find it interesting that according to ED rockets are exclusive only to D40s when there are reports of HVARS being officially issued for use as early as July 1944 by 9th air force P47's during the battle of St LO. And even prior to that they were using M10 Bazooka rocket packs with earlier razorbacks
-
many? ONly in 2011 was low rate intitial production approved and at that time it was still going through evaluation. . By 2014 only 6 APG82's had been delivered. By 2016 a production batch of 28 radars was approved. l 2017 that was the first year AESA strike eagles took part in thier first red flag exercise. The final deliveries of those 28 radars didnt complete until 2019. SO the majority of Strike eagles were and are are still using APG70, since according to the USAF official website their total Fleet of F15E's are 219. SO a a new UFC doesn't mean AESA. http://raytheon.mediaroom.com/index.php?s=43&item=2170 https://theaviationgeekclub.com/f-15es-apg-82-aesa-radars-deploy-red-flag-alaska-first-time/ https://www.militaryaerospace.com/computers/article/16714836/boeing-wins-halfbilliondollar-order-to-upgrade-radar-on-air-force-f15cd-and-f15e-combat-jets
-
That is true, but youd be surprised how similar they are in operation ( IF i showed Av8b plus excerpts of MFD Radar page/modes and claimed it as APG73 illustration from the Hornet i bet id be able to fool a fair bit of people) . Utilizing an API doesn't mean 100% exact copy paste. TBH i can't help but think think the APG73 designations was more marketing. ITs honestly more like an APG65 V2.0. Its not a new radar design. Its basically the same antenna but upgraded digital components like more processing power and memory storage etc. LIke genuinely if you compare photos of APG65 radar and APG73 radar, There are probably only very subtle differences. I mean same way he F16c's went through upgraded iteration of the same radar family IE APG68 V1-V9
-
whatever it is certainly not worse than the APG73 radar
-
Honestly itl be mostly aesthetics. The UFC on the F15E is not fancy like the UFC on the Super Hornet where it can also act as another MFD display for various MFD pages. From what i have seen it basically fills same function and similar overlay as the physical UFC, but on a screen. IF razbam has the nessary documentation to model it or want to put in the extra effort good for them. But seems to me the physical UFC is a safer choice especially as they already have completed 3d model of it.
-
IS this in game However according to research including using UH1H flight manuals as references this sight picture is fictional. M60 reflext sight should look like this Ironically even ED inadvertently admit from their very own dcs huey manual the prototype designation of preceding XM60/XM60E1 are supposed to look like this Sourced from pg 103 of the DCS Uh1H manual
-
ITs nice to hear new bomb options like AN-M57, AN/M65 1000 pounders are coming in. Although OT would ED consider slapping those onto the F86F sabre module since it could use those IRL?
-
It seems P47 release is just around the corner. I have not seen any of the youtubers that have gotten the preview build of the P47D showcasing ground attack aside from guns strafing. So will the P47 have general purpose bombs and HVAR rockets included at its day 1 launch? or only after "early access" is complete ?
-
It would be nice if we actually got the correct M60 reflex sight for the pilot......
-
Did real F-86F Sabre radar assisted gunsight "calculated" lead?
Kev2go replied to avenger82's topic in DCS: F-86F Sabre
The A4 isn' t from ww2. Its korean era tec. The A4 replaced the earlier A1CM gunsight ( which was more problematic) from F86A and F86E's -
yea thats the "browse imagery" ddi page. Essentially imagery that can be uploaded unto the SuperHornet and stored in memory hardrive via Data cartridge or sent over via Link 16 network, which can be viewed, edited or re transmitted. Not sure if Tactical imagery integration eventually made it into the legacy Hornets as well. but if they did its probably not a circa "2005" era Hornet, as 2005-2006 is when this feature was just being put into use in Super Hornets.
-
The only fundemental difference that i can think of between ER and AT is datalinking and recorder capabilities. Same sensor suite otherwise the same. the Litening 2 pod we have on the Hornet is ( or was) supposed to be the AT version. 100% certainty it is not the initial l2 pod ( pre ER) as it had a much worse resolution and did not have as much zoom. ER after all stood for extended range. 2 FOV plus 9 zoom levels is the ER and AT are capable of. This is what is in common all across the board in the A10C, F16C, harrier and Hornet. Although no TGP DL sharing, that may be only because the Hornet is still EA. A10C certainly is the AT version you can share information from TGP with other A10's. This was the model we had been lead to believe was being used for the Hornet, because it was already present on the A10C with only tweaks being made for the differences in its interfacing for the specific platform. Considering "more advanced versions" like the Litening 2 G4 were not put on the market until 2008 and from what i have been able to gather not adopted for usmc until as late as 2012. Those images still of USMC TGP IRRC that were used in the other thread by this same OP were from pre 2008 footage. Thus we can deduce that they are not " more advanced" than ER or AT versions https://forums.eagle.ru/showpost.php?p=4255869&postcount=25 https://forums.eagle.ru/showpost.php?p=4340336&postcount=16
-
So your saying you dont have the flexibility to use open sources to your main documentation make tweaks to make to look more like the USMC Litening pod? IN this case its been shown even SAF L2 shows coordinantes. Im not buying it, especially as the story keeps changing and we have been mislead
-
But its weird since somehow a USAF interface of L2 for A10C is used, as well as for the F16C, and USMC interface of L2 for Harrier all have coordinates in their screen and not a generic export one? Why would ED be so persistent of using a Spanish Hornet L2 version ( even if thats documentation that they have) and not fill in the blanks on how the interface should work with USMC version to make our DCS hornet more akin to the version its supposed to be replicating? Based on what we have seen in videos even from around "mid 2000'S we have a good comparison to to show the differences. Of all things lacking We really auht to have those coordinates listed on the screen, becuase it seems even the spanish one can still display them as another user posted earlier , but simply in different part of the FLIR page https://forums.eagle.ru/showpost.php?p=4345352&postcount=133
-
if any OV10 Bronco is made as a module Id prefer the OV10D. 1980s- gulf war Would fit more DCS scenarios as it was a model that has FLIR targeting sensor, laser guided muntions of various sorts, like Hellfires and LGBU's.
-
Yes It takes time to get places. The game needs to evolve. It can't stay the same forever. Ive been around longer than you i remember the pre DC 2.5 EDGe days. I have the benefit of perspective of seeing the evolution and appreciating the changes made. There are those who have been around even longer than me. And this game is fundamentally better now than it was back when DCS V1.2 was a thing. Dynamic Campaign and many other features for better "battlespace simulation" is eventually going to be a thing. IF you think DCS is so poor at everything, why bother playing DCS or using ED products?
-
Dcs ww1 would be a niche within an already niche community. IF you think helicopters are slow....
-
To curb the misconception that Dekka included thier own A/G radar solution. They released a nearly complete module at release. Good for them that really isn't raising the bar. . And IMHO the 3d interior cockpit detail is somewhat bland compared to ED and 3rd parties. But maybe that's just me. HEatblur can be said to have gone above and beyond because they put in the effort to make their own A/G radar for the Viggen, and also the effort put into making Jester AI for the tomcat, allowing single play use. After the tomcat i don't know if HB has any further plans in DCS. I recall something about members of the HB being hired by another company to do work in another software. IF that's true then i suspect DCS will become a sideshow to them after their obligations for tomcat , carrier, and AI A6 Intruder are complete. You may not agree with ED EA route ( even I am wary of Ed drifting into a habit of a cycle of countless EA products) but it is what it is. that being said the idea behind the SC module is really nice. IT goes well with this focus on Naval aviation. IT will give greater immersio, will benefit those using 3rd party naval aviation modules like the Tomcat, and very likely inclusion of compatibility future ones like the A7, and not just those who own the Hornet.
-
Heatblur and Dekka dont have an entire game engine to support and expand upon. They have the luxuary of only making modules.
-
Actually Dekka RBM mapping mode is based off ED ground radar API. Its not an in house solution. ED has not simply adjusted it yet to the Hornet at the time, but it is certainly soon to release in the next patch as per screenshots that wags shared. Even so The Radars on the JF17 and Hornet are far more sophisticated and have more A/G mode types and processes then viggen.
-
WSO is there for workload reduction. as pointed out unlike F14, the Pilot can do everything a WSO can. There is not the sort of dependency you have in the Tomcat where a pilot can't so much as wipe his own arse without a RIO. An AI WSO would have been nice but not mandatory for this sort of platform compared to the F14. IRRC there was a study ( originating with the USMC) that found 2 seater WSO concept is only really offers enough improvements in efficiency and workload reduction to justify the cost of 2nd person is for low level or austere weather condition A/G work. And even so the USMC F/A18D's have a unique role of also specializing as a aerial FAC, as well as performing reconnaissance beyond generic A/G, where the second pair of eyes and someone to manage radio coordination is more nessary. With regards why the USAF chose the 2 seat for the mudhen is to consider when it was designed. It was designed in the 80s where targeting pods were barely a thing ( and much more limited compared to present day ones) , and at the time there was far greater emphasis on relying on Radar as primary sensor for A/G strike compared to today. That being said the OP does have a point to an extent. the Strike eagle will appeal to in sales to a greater portion of the community likely because it is a multipurpose plane and because of a more modern digital interfacing.
-
Although razbam didnt officialy confirm or deny it, I have been following the thread, and they said they were using a 1993 publication as the basis of the strike eagle development. And coupled with some WSO commentary from that thread made it clear that first JHMCS didnt become fielded into strike eagles until around 2009, with AIm9X not being integrated until suite 8 upgrades ( circa 2018 ) so yeah with such recent upgrades for that specific platform, it is highly improbable Razbam will stick in JHMCS and Aim9x, especially when there are other changes regards to software, hardware and other weapons types that were implemented between 1993 and by 2018. https://www.mountainhome.af.mil/News/Article-Display/Article/1479980/366th-fighter-wing-receives-new-weapon-for-f-15e/
-
The F15C if made a full fidelty module would have a edge in a2a to the F15E due to potential JHMCs and Aim9X integration. F15E's got them later relative to the C's , and AFAIK it seems the Razbam F15E won't be getting those.