Leaderboard

All, For those who are not yet aware, @Hollywood_315 has placed the Vaicom source on github this morning and is therefore no longer supporting it. We are in the process of pulling together an ongoing development and community management team and will update as further details become available. Massive thanks to @Hollywood_315 for having produced such a great tool and supported it for so long. Sent from my SM-T835 using Tapatalk

We are working on a more permenat fix now that Hollywood has open sourced it. We are also putting together a Dev team to keep it running and potentially add to it. It will take us a few days to get a clean .dll that will make it functional in DCS 2.8.xxxxx with minimal messing around. At the moment there is a fix on our Discord. (with messing around) https://discord.gg/7c22BHNSCS I would like to publically acknowledge Hollywood_315 for the awesome advancement of VR flying in DCS. Without his work VR DCS would still be fringe at best. He bridged the gap with Vaicom Pro. Thankyou on behalf of the rest of us.

Gang, don't delete your Vaicom just yet. There is a fix that is being worked on in the Discord Vaicom community. They have got Vaicom working correctly again and are putting together a zipped file and install directions. It has been tested and everything seems to work. Should be out in a day or two.

Good to hear you have enjoyed, its important to have a little fun now and again

I'd like to share this picture I took of our Phantom this past weekend. We tugged her out to the ramp for display at our local air show (Wings Over Houston), and she attracted a lot of interest!

Option for the Mission Editor.

Normandy 2.0

Didn't think you'd notice so quickly. But you didn't see the second hand on the clock. @Fred901@Magic Zach Thanks for the help. We are trying to make Normandy 2 one of the best DCS maps. We will be grateful for any information.

LoL, I was flying my new MB-339Pan in Vegas when i did a Fly by in F3 view over the strip.. when the sound of the plane started to fade, I could hear monster, wolves, ghost etc playing in the background ? Really ED ? LoL, well played, well played.

Great news that Hollywood is ok. WIsh he would still continue with it. I would pay for updates or more functionality from him. After loosing it for 2 days I realized the value of his work was more than I thought. Hope he is busy and continues playing DCS though.

It will be a good idea get a option in specials where disable all easter eggs, more user fliendly

GLP means that even ED can now fork it and integrate it into DCS Core. The possibilities are immense. This could give ED a headstart of a few years in its Voice/ATC overhaul development.

Not in any way, shape, or form.

Hi no_easter_eggs = true in autoexec.cfg in the saved games DCS config folder. autoexec.cfg

JF-17 new weapons

Hello, A-4E-C pilots! We hope you are well. We'd like to highlight a few important items about this update, and salute the newest group of contributors to the A-4E-C project, whose names appear in the changelog below: This update, A-4E-C 2.1.0, and all subsequent updates will not be compatible with DCS versions before 2.8.0.32066. Our last update, A-4E-C 2.0.1, is not compatible with DCS versions after 2.7.18.30765. The most common effects of these incompatibilities are client-side crashes. Always ensure servers, clients, and DCS versions employed are the most compatible options available! If you enjoy suppression of enemy air defences (SEAD) in the A-4E-C, we've provided new functionality and depth to the audio environment of the AN/APR-25 Radar Homing and Warning System. New sounds specific to radar types and individual units in the DCS World theatre make getting locked up a whole new ballgame. Additionally, ECM is modelled when the AN/APR-25 function selector is in the RPT position. Additional documentation is provided in the changelog below and in the kneeboard manual. We've added new audio feedback for braking. This feedback is extremely useful for understanding ground handling response: If you hear a tire skidding, you are locking up the nosewheel by over-braking, and you should take this as a cue to release the brake, before tapping the brake toward your desired turn (and add a little throttle if you need to). This update also includes efforts to make piloting more accessible. Dozens of new input bindings for keyboard, mouse, and joystick inputs offer a wealth of opportunities for custom controller builders. Users with extensive input bindings might need to do a bit of housekeeping, but we hope the new additions make up any efforts you have to undertake! If you are interested in adding to the module's accessibility options, please reach out on Discord! Thank you for flying the A-4E-C! Download A-4E-C Version 2.1.0 - 30 Oct 2022 Added Systems: AN/APR-25 RHWS (ECM) With the AN/APR-25 Function Selector Switch set to REC and the APR-25 Switch in the ON position, a baseline system hum and response audio from a wide variety of radar-equipped units is produced at a volume determined by the the (inner) AN/APR-25 PRF Volume knob. When the APR-27 Switch is in the ON position, detected missile launches from SA-2 S-75 "Fan Song" will produce an oscillating alert tone at a volume determined by the (outer) AN/APR-25 Missile Alert Volume knob. The system's bit test is available to perform. With the AN/APR-25 Function Selector Switch set to REC, press the APR-27 Test button to initiate the bit test. With the system in AN/APR-25 Function Selector Switch set to RPT, ECM will attempt to jam incoming radar signals. The green RPT light will enable when the system transmits. Liveries: Community A-4E V: Blue Team, 2022 (Fictional) Community A-4E V: Red Team, 2022 (Fictional) USN VX-5 Vampires, 1986 (Fictional) USMC Naval Weapons Evaluation Facility, 1974 Operational-era USN and USMC liveries now have a customized, well-worn LAU-10 launcher. Quality of Life: Input accessibility options: Added two UI Override inputs, which allow joysticks, gamepads, and other input devices to utilize mouse functions, or to use as modifiers in input layouts. Input options previously available only on keyboards or joystick devices can now be bound to mouse button inputs. Throttle - Slew axis. Dual-axis rudder inputs (Rudder Left and Rudder Right). Zoom axis inputs for fine zoom control across devices: Zoom View In, Zoom View Out, Zoom View - Slew, Zoom View In - Slew, and Zoom Out - Slew. Throttle Increment slider in the special menu is available to adjust throttle rate for Throttle Increment/Decrement inputs. A Custom Throttle Rate slider in the special menu allows you to adjust the acceleration rate for the new Custom Throttle Rate inputs. The keyboard defaults for these are RCTRL+PageUp and RCTRL+PageDown, respectively. A Wheelbrake Differential axis is useful for mapping a single axis to the opposing left and right wheelbrakes. Trim Speeds in the special menu are now adjustable by individually for elevator (pitch), aileron (roll), and rudder (yaw), with percentage sliders. These settings also affect the Trim Reset (Hold) speed. (thanks Drofseh) A pair of comprehensive gamepad input presets for Xbox and PS4 controllers are included, which utilize many of the above functions. Once you are up and running in the pit, you can enjoy flying the A-4E-C with nothing but a humble gamepad and no additional software needed. (Thanks, Tuuvas) Single inputs for the Canopy Lever. You can close the canopy with LSHIFT+C, and open it LSHIFT+LCTRL+C. (thanks Tanuki44) Single and else inputs for Throttle Position Lock. Input option for cycling the Bomb Arm Switch between the OFF, NOSE & TAIL and TAIL positions. The keyboard default for this input is 6. Single inputs for the AWRS Quantity Selector Switch, AWRS Drop Interval Knob, and AWRS Mode Selector Switch. Single inputs for AN/ARN-52 TACAN Mode switch. Absolute and slew axis inputs for AN/APR-53A Radar Indicator Brilliance, Detail, Gain, Reticule, and Storage knobs. Radar Antenna Tilt Continuous CW and Radar Antenna Tilt Continuous CCW have been assigned a keyboard default (- and =, respectively). Inputs for APR-27 Test, APR-27 Light buttons. Absolute and slew axis inputs for AN/APR-25 Missile Alert Volume, AWRS Drop Interval Knob, Gunsight Elevation Control, Gunsight Light Control, Instrument Lights Control, Shrike/Sidewinder Volume Knob, TACAN Volume Knob, and White Floodlights Control. Some non-axis inputs associated with these have been renamed. Users with extensive control schemes should adjust their controls to resolve any conflicts. (thanks gcask) Input for Chaff Dispenser Select - Toggle 1/2. Inputs for common communications, including A/A refuelling - "Ready for precontact" radio call, and Ask AWACS available tanker. (thanks gcask) When the aircraft has power, the Seat Adjustment Switch can be used to move the baseline pilot head position up and down in the cockpit. (thanks nima3333) Kneeboard Manual: A a chart of weapon stations and their associated loadout options (page 3-7) in the kneeboard manual. An overview of the included Xbox1 and PS4 gamepad layouts are available at the end of the kneeboard manual (pages 6-6 and 6-7). Sounds: AN/APR-25 RHWS (ECM): AAA: New sounds are produced in response to the Fire Can SON-9 fire director radar. Aircraft: New sounds are produced in response to aircraft search and tracking radars. EWRs and Ships: Unique sound sets are produced in response to ground and ship EWRs. A new sound is also produced in response to ship tracking radars. SAMs: New sounds are produced in response to the P19 "Flat Face" and S-200 ST-68U "Tin Shield" and SA-2 S-75 "Fan Song" sarch and tracking radars. Some Fan Song units will sound different, simulating the sound of different radar bands used in the field. New sounds are also produced in response to the SA-3 S-125 "Low Blow", SA-5 S-200 "Square Pair", and SA-6 Kub "Straight Flush" units. The number of different sounds a each radar produces varies by unit, so pilots will need to learn what their ears are telling them about what type SAM is targeting them, and how much launch warning that SAM provides from its PRF audio. SPAAA Vehicles: New sounds are produced in response to the Gepard, Vulcan M163, and ZSU-23-4 Shilka "Gun Dish" radars. Sounds are produced if the left or right wheels are skidding. Use this feedback to help you learn to taxi (as a sound you don't generally want to hear), and to avoid damaging the wheels or locking up the brakes by keeping them depressed for too long. Seat adjustment hydraulic motor. Fixed Systems: Setting the AN/ARN-52 TACAN mode to REC no longer crashes the client. Addressing this issue means that A-4E-C 2.0.1 is not compatible with DCS versions after 2.7.18.30765, and A-4E-C 2.1.0 and later is not be compatible with DCS versions before 2.8.0.32066. AN/APG-53A Radar Terrain Clearance - PROFILE/PLAN switch input binding functions properly. Input from non-axis throttle inputs now cause the APC system to disengage properly. Liveries: Community A-4E III: Forever Free livery displays two digits on the flaps, matching the nose and tail. Weapons and Loadouts: CBU-2B/A pod weights are calculated correctly. Weapon release and spread cause fewer collision-based self-destructs when the weapon is released. Quality of Life: Throttle Increment and Throttle Decrement inputs function properly. The trim reset input now properly adjusts the position of the Rudder Trim Switch. Kneeboard Manual: Waypoints on the navigation page enumerate 11 waypoints, and can't overrun the instructions on the page. Placing a 300 gallon tank on the centre pylon enumerates properly on the kneeboard loadout page. Corrected erroneously listed procedures for ground radar. Corrected erroneous procedures for air refuelling. VR hand positions: Users are encouraged to enable Use Hand Controllers, Hand controllers use Cockpit Stick, and Hand Controllers use Cockpit Throttle, and Hand Interaction Only When Palm Grip is Obtained. Be aware that it is easy to accidently power down the engine if you touch it with your virtual index finger while holding the grip button. Always approach the throttle with your finger above it. Changed Missions: Changed a few liveries in the included mission sets to better reflect available livery sets. Liveries: Unmarked and Community liveries are now available to a wider selection of countries. Updated USN VC-1 Challengers. Updated a few knob textures. Weapons and Loadouts: In multiplayer, the serve, and any connected clients must all use this version of the module (or later) in order to prevent weapon conflicts arising from custom weapons. Quality of Life: Default inputs for Throttle Position Lock are set to RCTRL+HOME (Step Up) and RCTRL+END (Step Down). Emergency Stores Release Handle default input changed to LCTRL+J. (think J for jettison!) Differential wheelbrake inputs default inputs are changed to LCTRL+W (left) and LALT+W (right). The controls indicator's nosewheel caster indicator now displays logarithmically, making it easier to see those early changes in castering and better reflect nosewheel sensitivity to turn rate. (thanks, Drofseh). Refactored the special menu for easier editing in the future. Kneeboard Manual: Added additional guidance and notes on AN/APR-25 RHWS (ECM) operation. Sounds: Improved input response and dynamic range of AN/APR-25 PRF Volume, AN/APR-25 Missile Alert Volume, Shrike/Sidewinder Volume, and TACAN Volume knobs. Reduced the relative volume of the AN/APR-25 operational "hum".

Thanks for the fun here ED. I appreciate putting in some fun for the holidays. Don't listen too much to the naysayers who want to extract light hearted and temporary fun out of everything. I look forward to the next Easter eggs.

FEAR THE BONES

pinned an hour ago

So sad to hear this. The best fun I've had in DCS over the years has been on this server. It had a unique mix, hard to put your finger on any one thing but when blended together it was really magical. Much attention was given to the role of combined arms something I've yet to find on any other MP server. It made for many intensive battles requiring communication & coordination between air/land units it was oh so good. The server also attracted a great bunch of people some of whom have become friends and for that I am very grateful. All the best & hats off to Alpenwolf for all the great times and I hope that maybe sometime in the future as a DCS heavyweight he'll make a comeback. Best wishes, CVA

Сегодня Helloween! Посмотрите что творится на авианосцах.

Okay, back from benching. Thanks to @mbucchia i was able to do it more properly. Test scenarios were the following: F18 @ Caucasus, F16 @ Syria and AH-64 @ Marianas. Here are the results: F18 Caucasus CPU FT 2.7: 6.1, CPU FT 2.8: 6.4, Diffrenece: -4.8% GPT FT 2.7: 13.4, GPU FT 2.8: 14.8, Differece: -10.3% F16 Syria CPU FT 2.7: 7.38, CPU FT 2.8: 7.35, Diffrenece: +0.43% GPT FT 2.7: 14.62, GPU FT 2.8: 16.23, Differece: -11.64% AH-64 Marianas CPU FT 2.7: 9.82, CPU FT 2.8: 10.54, Diffrenece: -7.31% GPT FT 2.7: 19.60, GPU FT 2.8: 21.34, Differece: -8.91% It's worth to note that i left secondary shadows 'off' for a better comparison. All in all it's roughly a 10% decrease in GPU Frametimes while CPU may vary. I'll provide the tracks for you guys to test as well if you want to. F16 SYRIA BENCH.trkAH64 MARIANAS BENCH.trk @BIGNEWY None of the people i know saw increases in performance and given the number of answears to this threat, i assume the vast majority of the people using DCS won't see any. Nevertheless, it's good to know that ED is looking into it. It's not about people like me who have lost around 10% (that would be perfectly okay for the visual improvements that came with the patch). It's about the people losing 15 FPS total under VR making the game unplayable for them under VR. Couldn't attach the last track because of the 5MB limitation. So here it is: F18 CAUCASUS BENCH.trk Cheers!

added Halloween taxi light Jack O'Lantern:

Hi, we do test, personally I had a slight fps increase, but not by much. Others have also seen and increase, but also others have seen a decrease. We are investigating. thanks

Just a quick post to let people know that Hollywood at least appears to be alive. I know many of us were worried for his health and hoping things were ok. At least I'm assuming it's the same Hollywood that has now archived Vaicom on GitHub. If you haven't yet, join the Discord with Pene's link above - I for one am hoping people with better C# and lua skills than I can take Hollywood's great project and develop it further under GPL.

I was not aware about halloween feature until after mission i checked other planes status by F2, it was pretty creepy to see my wingman laying dead in the cockpit of his burning fighter and hear those crawling sounds and creepy music...had a good laugh! But i understand some guys just want everything be always so serious and boring;)

Completely unnecessary...

I cant believe it, I just jumped into a plane and started hearing voices and creepy sounds... Please tell me that the developers couldnt have better spent their time fixing the Apache FM...

It's the same silly arguments every time... It's political... make vulkan first... ED invest 3D modelers time to re-create pilot model for their aircraft (F-16/8 at the moment per their statements) - so creating a woman face or black face - ain't that big of a task. It got nothing to do with vulkan for that matter. Absolutely different engineers. Moreover, there is nothing political about it. The community contain black people and woman. Be it my daughter that fly's the sim from time to time or anyone else. With that much effort being invested to increase immersion - that is an important feature (BTW, there are black super carrier crew... So it's already been done by ED... They just need to do it on the pilot models as well). *ED found time to model 3D skeletons for Halloween... before finishing vulkan So modeling a few faces for their pilot models... RAZBAM could be the first one to do it and that could be very cool.

Since I've made some of these Liveries in question, I can tell you that I'm terms of quality, here's a bit of a sneak peak behind the curtain to the process. As I work on a livery, it's authenticity is scrutinized by the livery team via update pics, questions, vast historical research photos etc, other artists weighing in. Eventually, it's given the thumbs up once it meets the standard. With the tools, creativity of the artists and the absolute accessibility and plain common sense and consideration that Cobra gives to the individual team member's input, I can't imagine a more forward thinking and reasonable group of people to work with than what I've experienced working with the HB team. If any words describe best their mission, the words Precision, detailed, accurate, and thorough come to mind regarding the quality of their products. The very fiber of the DNA of the people who populate this team simply won't allow them to produce something of lesser quality than that which can ultimately be achieved. I've been in the simming world for over 25 years and I've never seen anything like what we have now. DCS and Heatblur, are on the leading edge of simming. Anyway, If there's something "sub par" about my Liveries, let me know with specifics. Thanks.

null

Playing with reshade at the same time:

Normandy 2.0 Update

Hi, I want to report a general decrease of framerate by about 13%. This might be to the new cloud and lighting effects, however I think It might be useful to let you know this. Since the 2.7.6 to 2.7.7 - Performance-Loss Bug I have a small replay I regularly check before updates. These are now the differences: 2.7.18 27-10-2022, 16:05:09 DCS.exe benchmark completed, 8549 frames rendered in 101.203 s Average framerate : 84.4 FPS Minimum framerate : 56.9 FPS Maximum framerate : 109.9 FPS 1% low framerate : 58.7 FPS 0.1% low framerate : 33.7 FPS 2.8.0 30-10-2022, 20:50:31 DCS.exe benchmark completed, 7452 frames rendered in 101.015 s Average framerate : 73.7 FPS Minimum framerate : 51.4 FPS Maximum framerate : 92.6 FPS 1% low framerate : 52.8 FPS 0.1% low framerate : 47.7 FPS My PC in short: Ryzen 7 3700X, AMD 6900XT (Adrenalin 22.10.2), 64GB RAM, Windows 10 21H2 Unfortunately, I can only share a actual 2.8 log file (attached). Currently I try to make space on my drive, to update the stable and -counterverify the original numbers. I will post the log for this later. What I've done so far: - Delete fxo - Delete metashader2 - Removed Scripts-Folder As soon as the stable is ready I'll try diffent settings to compare the impacts. But meanwhile, if someone has valuable suggestions, I am open for tipps. EDIT: I finally could find some place for the stable and installed it. I've created two more flight, one in very bad weather, the other without. Also changed the modules. But the results are very compareable. 30-10-2022, 22:11:55 DCS.exe benchmark completed, 5598 frames rendered in 74.672 s 2.7.18 Beirut_4_2 Average framerate : 74.9 FPS Minimum framerate : 56.6 FPS Maximum framerate : 99.8 FPS 1% low framerate : 56.6 FPS 0.1% low framerate : 55.1 FPS 30-10-2022, 22:15:30 DCS.exe benchmark completed, 6445 frames rendered in 63.859 s 2.7.18 Beirut_4_3 Average framerate : 100.9 FPS Minimum framerate : 72.7 FPS Maximum framerate : 137.7 FPS 1% low framerate : 72.4 FPS 0.1% low framerate : 70.8 FPS 30-10-2022, 22:19:27 DCS.exe benchmark completed, 4906 frames rendered in 74.469 s 2.8.0 Beirut_4_2 Average framerate : 65.8 FPS Minimum framerate : 52.2 FPS Maximum framerate : 87.3 FPS 1% low framerate : 51.6 FPS 0.1% low framerate : 47.5 FPS 30-10-2022, 22:21:04 DCS.exe benchmark completed, 5590 frames rendered in 63.438 s 2.8.0 Beirut_4_3 Average framerate : 88.1 FPS Minimum framerate : 60.8 FPS Maximum framerate : 115.7 FPS 1% low framerate : 60.1 FPS 0.1% low framerate : 58.6 FPS EDIT2: Updated Title EDIT3: Corrected GPU Number dcs.log Performance_Fly_4_1_Beirut.trk Performance_Fly_4_2_Beirut.trk Performance_Fly_4_3_Beirut.trk dcs_2.7.18.log

I was able to reproduce internally and will report, thanks all!

Starting from now, Vaicom is no longer supported by its original developer. For answers to questions please either head to the Vaicom Discord (https://discord.gg/7c22BHNSCS) or contact either @MAXsennaor me via these forums (either posted or as a DM) and we will do our best to help. A team of volunteers is already forming to take this product forward but it will take us a few weeks to get fully up to speed.

I've paid the tool but I have nothing to regret if the community driven new vaicom will be free for all, following the genuine philosophy behind the open source software. Due to a lot of bugs accumulated in the last months, I think I'm going to uninstall the current vaicom and I'll wait to see the first sort of "stable" effort of the community. I'd like to help myself the development, but I have absolutely no coding knowledge. At least I know vaicom will work again in the near future.

My understanding (and hope) is that now it is open source it will be free! I’m sure the community is excited to be able to keep working on it as freeware (though I’d happily donate if there is a patreon or something). Personally I’m more than happy to have paid @Hollywood_315for his awesome work at the time and have got plenty of use out of it over the last 18 months so don’t begrudge a penny! I’m pretty sure most people feel the same way! Also to jump on the bandwagon and add my thanks to the both Hollywood and the community for keeping this amazing tool alive!

DCS is an entertainment product. Our professional products are not DCS. But thank you for the feedback. We do understand those who dont enjoy it, which is why it can be disabled. I also appreciate those who are enjoying it. thank you

Thank you for posting this. I had done testing with 2.7.18 vs 2.8.0 and saw similar results. Below is one of my test runs from PG with clear weather. People really need to do an actual benchmark test before claiming performance is better/worse/same. In 2.8 it's certainly worse and not related to VR. Windows 11 22H2 (latest updates), Nvidia Driver 516.94, I9-10900K, 64G RAM, RTX 3090 30-10-2022, 12:06:21 DCS.exe benchmark completed, 6735 frames rendered in 89.234 s (Open Beta 2.8.0) Average framerate : 75.4 FPS Minimum framerate : 62.4 FPS Maximum framerate : 92.1 FPS 1% low framerate : 62.7 FPS 0.1% low framerate : 61.7 FPS 30-10-2022, 12:09:50 DCS.exe benchmark completed, 7888 frames rendered in 92.141 s (Stable 2.7.18) Average framerate : 85.6 FPS Minimum framerate : 69.7 FPS Maximum framerate : 105.4 FPS 1% low framerate : 70.1 FPS 0.1% low framerate : 68.8 FPS

I don't want to make controversy or start sterile debates, but I think similar features in a flight simulator completely out of place. There should be an option for those who want to activate these features and not vice versa, for those who don't want to have them. However, thanks to Bignewy (for autoexec.cfg) to remove these, in my opinion, senseless features.

https://github.com/Hollywood315/VAICOMPRO-GPL VAICOM PRO under GPL License. Worthy of donations!

Now you're just whining. Yes, your ridiculous 19Gb is trivial. BEYOND trivial. Again, a good SSD drive is about 100 bucks for 2TB. Ergo your 19Gb crisis, works out to cost you 95 cents... you've wasted more electricity on this forum complaining about it than the space it consumes actually costs.

Love the Halloween stuff! Did a night mission with my group tonight, about 8 to 10 guys, and we noticed the moon was bigger, then as it got darker everything got..... greener. Flares, lights, afterburner, everything. After the mission as the canopies came up and the engines spooled down we heard the ghouls and zombies and witches. Fantastic! Absolutely loved it. I hope you keep the big moon because it looks incredible. P.S. I hope you guys keep doing stuff like this for more holidays. Sent from my SM-G960U using Tapatalk

Well done ED. Pretty cool!!

The F-14's textures are not unreasonably heavy @XCNuse, you have repeated this assertion a fair bit in this thread without a proper understanding of your argument. It's simply untrue. Just remeasured now to refresh my own memory- it's pegged (on average) at 480 px/m for the exterior. This is less than a typical hero vehicle standard of 512 px/m in AAA games on console. We pick our resource usage very carefully. I can't recall the amount of hours I've spent planning and optimizing the F-14- but it's a lot. You're welcome to dump the F-14 cockpit into wireframe view and see how we've even stripped some triangles to avoid long and thin faces (super slow on the GPU). Every texture is sorted rather meticilously compression wise and we maintain relatively average industry average texel densities across the board. The main reason you are seeing significantly heavier total texture usage in the F-14 is because it's simply bigger. The total surface area to cover with textures in the F-14 is far far bigger than the F-16. It's a completely silly comparison. In the near future, some of the liveries that ship custom normals will be reduced in size as some liveries added custom normals for various fixes or special considerations. Because even the most expensive NVME m.2 SSD storage costs you 0.2c per GB, so at most we're "wasting" $2.4 worth of diskspace. Happy to continue discussing the technical specifics for any concerns you may have.

Please do point out where I have been rude to anyone. The fact remains that we are well within industry standard, and not even on the upper end compared to other sim modules on the general flight sim market - if that is arrogant for you, I am sorry, but we disagree. And I also disagree that providing higher quality skins, which are still smaller than the largest skin in DCS, and simply demand a larger size, is being arrogant. If disagreeing with you is considered rude, then sorry, but I don't know what to tell you. And what you consider meme skins, others do not, and they are exactly 2, and if removed would make a difference of precisely 291,6 MB combined. The vast majority of the community wants more skins, not less, and better skins, not worse. Requests for more and new skins are among the most frequent requests we get. The many iconic F-14 liveries are also part of the Tomcat culture, and thus expected of us. Stating these facts, in my book, is not rude. My apologies if you think it is.

Dear Sir, You forgot air density... And guess what, if you divide your result (1.65) by 1.225 (approx air density at sea level) you find 1.34

Small criticism: Remove the bomb carts as static objects that are permanently placed on the map and put them in the WWII asset pack as a placeable object. Its very strange and unnerving to start up, taxi by, takeoff, fly for 2-3 hours, land, taxi in…. And still see those bombs sitting off the side of the ramp… forgotten in time. Sitting in the sun during summer… rained and snowed on in the winter…. Time goes on and those bombs just sit there. In real life they’re either in the munitions bunker away from the infrastructure, or they’re being loaded on the aircraft. If the armorers brought too many and there were extra bombs, they’d be taken back to the bunker….. not just pushed off to the grass and left forever. Also… do the clocks inside the hanger actually tell correct time? If not remove them too. It’s a nice detail but if it’s just static there’s no reason to include them. It’s just a constant reminder of something that’s wrong in an otherwise awesomely detailed hanger.

Hi Today we will visit some British and French airfields. This will be 3 English original airfields: Ford Funtington West Malling and 3 French original airfields: Creil Beauvais-Tille Villacoublay