nootshell

bump

It became ever so clear to me that invisible FARPs by-design remove trees/objects around them without an option to turn this off. In my attempts to create a sort of "hidden" FARP in a forest I've also found out that in doing so the invisible FARP entry decides to clear entire chunks of the forest without much care for range or shape. Please improve how the tree/object removal is being done, or better yet make it optional for entities that do so in a hardcoded fashion. I'd love to make use of invisible FARPs, but simply cannot in this case. I've attached a small test mission for you to try and reproduce this yourself. The following screenshot is the result when I run it on my machine (smoke = FARP): LumberjackFARP.miz

Particularly annoying for when one uses invisible FARPs:

bump, very very annoying. please make this optional or remove it from the invisible farp entity entirely as OP suggested.

bump

Joking aside, this would open the doors to a lot more logistics operations where we can slingload statics/units as well. Not only do I desperately want to slingload cows, I also want to slingload humvees and whatnot. Although when it comes to slingloading things, cattle obviously has a priority.

No one said this has to be done first. No one said this is a priority.

Sauce:

Definitely required for proper immersion. +many

From the amount of people I've helped on the discord I can tell you that most people with issues are using standalone, probably as per the statistic when it comes to number of standalone users vs Steam users. Now, on topic, as a Steam user myself (cue the pitchfork pilots) I have a few reasons of why I'm using the Steam version: Truly automatic updates: I don't need to launch DCS to pull in updates, nor do i need to dive into the task scheduler to schedule an update every n hours. This is a very big one for me as I'd like to turn my PC on in the morning, grab a coffee, and get back to my PC with DCS fully up to date. In the morning (or after a long day of work) I really don't want to bother starting update processes. Dual licensing makes me feel a bit safer: I own a significant number of modules, it has cost me quite a bit. That slight feeling of being on the safer side is just a plus for me. Playtime tracking: not a significant part of the experience, but clearly something that is lacking in standalone. Here's to hoping that'll get improved. Store experience: browsing the DCS page on the Steam store just feels so much better and user-friendlier than the E-shop. Checkout is also much much less of a pain as Steam properly supports my bank whereas last time I checked, for the E-shop I basically have to do everything through PayPal. On top of this I'd like to add that Steam already has access to my billing information whereas ED does not, where possible I like to restrict that information as not every organization needs access to that. The ability to refund: I've never had to refund anything, but I can't stand being unable to do so. Standalone support is absolutely awesome tho, allowing swapsies/miles in some cases. Download speed and stability: while standalone has really improved their speeds, it's still not up to par with Steam yet for me with standalone pulling about 80% of what Steam would pull bandwidth-wise. Same with stability, for standalone I'd occasionally have a dropped connection whereas Steam only does so rarely. Not a big problem, but still something I consider noteworthy. However, for new pilots I most definitely recommend they get the standalone version, and here's why: Trials. Also, trials. Yeah, trials. The trial system ED has introduced has seriously been a game changer, testing out modules and getting a good hands-on experience before you buy them has been invaluable to so many people already.

That does sound peculiar to me as well, that's almost as if the disk it was installed on barfed while steam was verifying the integrity of the files. So long as it's an isolated occurrence I wouldn't worry about it, if it does happen again though it may be worth looking into a specific cause (in which case you may ping me if you so desire).

Pre-orders themselves are not transferrable, but once the module is released they are able to be transferred precisely as mentioned above. Nothing to necessarily worry about, and refunding/rebuying is also far from a necessity.

By allowing us to play audio from a 3D point, we can make significantly more immersive missions. One fairly simple example, and actually my main use case right now, is alarms that are going off at an airbase in case of a QRF launch. Other uses would be adding custom background chatter in various mission-related locations to improve the quality and level of immersion. Additionally, being able to attach sound to other units would add in another level of possible immersion as one can add warning/curfew/emergency related sounds to units.

Thank you for your suggestion, that's what I've tried before only to get the same results. Plus from all the options I'd have to remap to a different key combo, I'd run out of key combinations eventually. I'd rather just disable what I don't need. I'm also all in for DCS not resetting binds.

It's been several times now that I had to manually clear the keybind that enables the camera to automatically track a launched weapon, it interferes with gameplay and ruins immersion and recordings. While I'm ok clearing the keybinds manually this isn't always (ever) possible, as I only find out it's bound again when it's already a problem. Completely disabling certain keybinds would prevent this issue, along with the issue of having keybinds that conflict with other software reappear over time, forever.