Jump to content

snocc_

Members
  • Posts

    76
  • Joined

  • Last visited

Everything posted by snocc_

  1. same here, would be perfect as a separate add-on variant if it cant be part of the main chinook module
  2. +1, ch-47C would help mission makers out immensely and would fit in perfectly with a lot of our current maps and conflicts where only having the F available can get a little awkward like the falklands or the persian gulf while we wait for vietnam
  3. hello make the B-17 on the newsletter screenshots a full module thank you
  4. that's fine with me, i'd still rather see our current module improved before more versions are added
  5. it would be very cool to have both the UH-1H and a UH-1N or other huey versions but at the moment i'd much rather see a UH-1H module overhaul before adding more variants into the mix
  6. it would really be amazing to see more light antitank aircraft as unique as this ingame, hopefully it can be made in the near future as it has some strong potential to open up some very interesting new gameplay possibilities for the red side especially
  7. Completely agree with the original post, it would be great to have more variants of the spitfire ingame in general
  8. having an option to mount and dismount the ale-40 through the rearming screen or as a mission editor option on our current mirage F1 versions would be very nice to have to better represent how these aircraft were equipped in the earlier half of the 80s and before on our missions, with phimat pods on the roadmap it'd also be nice to be able to fly with phimats only
  9. very nice update! is there any chance we could also see RAF church stanton on this map at some point in the future? it'd be very nice to have more airfields covering the western parts of the map
  10. the DCS huey needs a full rework at this point, hopefully if we ever do get it we can get all these little options added in, i'd be willing to pay for a huey 2 upgrade that addresses the problems our current version has and brings in a little more customizability to it or brings in a full early/late version package like the post says
  11. would love to see ED lean more into multi-variant modules like a couple 3rd parties have and deliver an early 47D or C after the F is out, i really like the idea of getting a chinook in DCS but the F doesn't do much for me
  12. snocc_

    aim-9P-3

    Will we be getting the new aim-9P-3 on the F1 in a future patch? it had been used on the spanish F1s starting in the early 1980s but its currently not available ingame
  13. its not just a matter of it not being bought or used, there were no modifications made to the F1M with the exocet in mind and its not really any more capable of using it than the F1CE or EE, i'd much rather aerges release an EQ-5 or 6 with real exocet capability along with all it's differences from the spanish variants and all the other extra weapons as an add-on or as part of a different F1 pack later on
  14. afaik iran has been having a lot of trouble integrating much of anything they have on the F1, so far i've only been able to find pics and info of them flying with external fuel tanks taken from the F-5, im not aware of any other weapon they can carry from iranian inventory theoretically it should still be able to carry anything the F1EQs carried in iraqi service, but most of those weapons are not currently present in iranian inventory
  15. as of a recent patch the br.250's textures have gone down in quality after being taken out of the game and put back in also, using quaggles' datamine for reference both the br.250's and br.500's explosive mass seems much lower than their counterparts of similar weight and filler like the mk-82 or mk-83 https://github.com/Quaggles/dcs-lua-datamine/releases/tag/2.8.8.43489 BR.250 (left) - https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/bombs/BR_250.lua BR.500 (right) - https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/bombs/BR_500.lua mk-82 (left) - https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/warheads/Mk_82.lua mk-83 (right) - https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/warheads/Mk_83.lua a small check up from the devs to bring the BR series of bombs up to the standard of the rest of bombs ingame would be greatly appreciated
  16. bump, would be very interesting to see more of jordan in the map, especially those bases left within the map's constraints
  17. If we had that + nitehawk it'd be a different story and i probably wouldnt be asking for this like i am, but since we dont and im going to ask i'd rather ask for a full product i'd like to see with all the bits and pieces over a compromise like this Either way we already have an answer from ED and if its not planned its not planned, hopefully it can be considered in the future
  18. F1AZ and/or EQ-5/6 would be great for DCS, hopefully aerges can continue making F1 variants and packs after our main package is done so we can get closer to the full F1 experience
  19. They wouldnt be, like multiple users have already pointed out our biggest problem with fitting the DCS hornet in these early scenarios are the link-16 and the JHMCS and like vampyre already said PvP scenarios before these systems were added into the module did just fine, an option to restrict these systems would go a long way but if im to ask i'd rather get the full early hornet package with the rest of the little bits and pieces that differ from ours what i want is an F-18A from the mid/late 80s or the very early 90s as said in the title and first post
  20. thank you , im a little more biased towards the early 18A than the C but i'd be more than happy with either version prior to stuff like the apg-73 being introduced
  21. if we wanted to take on these earlier scenarios with the current DCS hornet we would need to restrict crap our version has because as already mentioned the F-18 in DCS has systems it didnt have access to in the 80s and 90s and while it was a very good and capable plane in it's time regardless these systems give it quite an edge that it simply should not have in these timeframes, its not even just about balanced pubbie pvp servers but also about being able to enjoy authentic scenarios with authentic aircraft in general whether it be pve, pvp or singleplayer missions without having to worry about the plane you're flying being too new there's a reason for this there's been a number of pvp cold war servers that have tried adding the hornet and other blue mid 2000s aircraft in an attempt to have them stand in as the iconic earlier cold war versions DCS lacks while keeping red to period appropriate soviet aircraft. They usually die off after a short time unless some other important changes are made to who used what aircraft at what time for public pvp server balance as otherwise red players will quickly realize they're stuck on a steep uphill battle against aircraft that are 20+ years newer than the timeframe the mission is supposed to be set in let alone the aircraft they are allowed to use on these scenarios and just leave
  22. for sure, some people may believe that and they'd be wrong but nothing like an "F-5 cockpit version of the hornet" was ever a point i was trying to make on the conversation, there was never any mention of it being anything like a shrunken F-4 or an overgrown F-5 or an early viper A, im not sure where you're getting this idea from on my posts, im aware the F-18A and C are similar aircraft what im asking for is a hornet version that can more easily fit into these earlier scenarios without outclassing the actual period appropriate aircraft on either side just by virtue of having systems 10~20 years newer that they should simply not have access to on these timeframes, mainly jhmcs and link 16 and sometimes some of the tgps when they're needed to stand-in for the nitehawk, this is not necessarily a problem with our current hornet since it simply has the equipment the F-18 ED is modelling is supposed to have but more of a problem caused by the lack of an earlier hornet version that can really complement it and take good care of these earlier time periods "just dont use link-16/jhmcs" isnt a very solid argument either since as already mentioned there's no real way to restrict the use of these systems on these scenarios, the only "later"-ish addition you can really restrict on our hornet beyond weapons and stores is the GPS but that isnt as nearly a big of a deal and afaik was already a thing on the C hornets by the time they started flying so it doesnt really matter anyway, them being so similar just means ED will have to do less work on the 18A and we'll get it faster after our C is finished
  23. i am aware the 18A and 18C are overall pretty similar aircraft, that doesnt change what i said or think, the current DCS hornet still struggles to fit into early scenarios due to reasons i've already mentioned, i am not asking for a late 90s A either but something closer to the end of the 80s or the beginning of the 90s the practical reason for an early hornet variant is having a hornet that fits early scenarios
×
×
  • Create New...