It’s not something to sell it. It’s a Basic overview if you knew nothing
hilarious in it’s own way
@Smin1080p_WT Hey Smin, sorry to bother you, but I’m finally able to talk on the forums again after a decently long absence. So, I have two questions:
-
With the A-7H getting the AERO-1D 300 gallon drop tank, are there plans to introduce it for other planes this patch that used it (such as the 3x A-7Es, 1x A-7D, 1x A-7K, some of the A-4 Skyhawks, A-6E TRAM Intruder, and A-1H Skyraider), or is it just planned for the A-7H for the time being?
-
Seeing as both F/A-18A Hornets had the AGM-84D Harpoon added on dev, are there plans to add it for the Tigershark as well (seeing as it was advertised as being able to carry up to 3x)? If not, would you at least be willing to pass this bug report of mine for them on to bug report moderator?
Community Bug Reporting System
1 Like
I guess no dev-update today?
one on the centerline pylon?
Rafale nerf blog today
they already did that this update without needing a blog for it sadly
1 Like
what was nerfed?
AASM release speed limited to Mach 1 now instead of Mach 1.4, and then the gun’s explosive mass nerfed, and then they reduced the instructor overload (which tbf also affected other aircraft too). So that’s about 3 different nerfs right there.
1x Centerline, 2x on either outboard wing pylon.
All photos of Tigersharks carrying Harpoons were on the centerline pylon, but there is some stuff that supports it being useable/equippable on all three
2 Likes
May be a bit late to this but im dying of laughter, Is that what the devs think robust is? 40mm?
where dev updoot?
1 Like
Guys, tonight i am going to write and tell my feelings to my love of my life. I am more scared to write it then play againd BMPT
2 Likes
best of luck :)
1 Like
Leopard 2A5 and 2A6 can not be compared to Strv 122s and Leopard 2A7s, though.
2A5 and 2A6 are 12.3s (if 2A5 is, so is 2A6, damn it), while the 122s and 2A7s are 12.7s that would be 13.0-13.3 if there was some decompression.
Leclercs as currently depicted are 12.3 material AT MOST. And if “performance” proves anything, is that the “12.7” Leclercs are performing similarly to 12.3 Leopards, so there you go.
You ate it.
How are you gonna tell ur feelings to an M1A2 sepv3?
1 Like
Hoping for some insight here. With bug reports like this and some ive posted, i dont understand the point of reports being closed for not enough info. This seems like a very backwards way, inefficient and potentially demoralizing for the community members putting in the work on these reports.
My main issue is with closing a report when asking for more information. I had a very big report a while back regarding rwr bugs, it had a significant amount of traction built up over a few days. This report was closed for not enough info similar to Rons here. Admittedly they had good reason for mine, requesting game logs from matches. Very easy fix.
The issue is these reports then close with no way for us to reopen the orginal post and add the requested info besides bugging managers here to possibly re open. This means we have to create a whole additional post from scratch, and attempt to regain all the traction lost from the previous. Forcing posters to open a second or even third post with the additional info can be very offputing to players. Potentially resulting in them just not doing it with the fear itll just get closed again requesting some more info. These threads shouldnt function this way.
If we could lock the posts to the masses but allow the original poster to possibly update the original post with whatever info is requested, that would be significantly more effecient. Less overall posts, less time required from posters and even less time for the bug report team to have to read through an entirely new post. If we were allowed to just add additional info to our previously locked thread, then only that new info would need to be reviewed.
Overall it just seems very inefficient and frustrating for all involved.
Sorry for the rant, just looking for some insight on maybe why this is the system and if possible how this could be improved.
3 Likes
yeah but you see bug reports dont actually become visible to the team if they dont fit gaijin’s plans yet
Counter-argument, there is only a limited amount of technical moderators and their time is also limited as many of them are unpaid volunteers. Closing reports immediately rather than requesting the additional information makes it more likely that you’ll get future reports right from the very start, and the bug-reporting service should be a very strict environment as there’s already too many useless reports to deal with.