Schwarzfeld

Not sure why my original post of these skin shots got deleted but uh....

When your consumer demand is about a hundred people, half of whom still live in their mother's basement and think they're a fur real pilot etc, you (the business manufacturing this stuff) will have to jack some pricing up a tad to make your ROI (return on investment) within a reasonable timeframe. In addition, your startup cost to design and manufacturer (also underwrite a warranty, which is not free) a proprietary piece of gaming hardware that nobody else makes (read: you can't buy it off the shelf) is relatively high, plus your business risk is high due to the niche nature of the demographic, and the fact that the LTV (lifetime value) of said customer is quite low for you the mfr because once you've bought a set of Cougar MFDs or Apache MFDs, the chances of that customer coming back for a second set are pretty much zero. There's more, but business is business, and if I'm making and selling products, I'm in business to make money. Therefore, I will price my product as high as the market will bear (the highest price the target customer is willing to pay) and then try to sell as many as possible. My startup cost to manufacture and ship all over the world, even it if its a proprietary "button box" is still high, and I probably borrowed that money from a bank. The bank wants that money back by date X, there's a minimum monthly payment I'm obligated to make for debt service, and the sooner I pay that loan down the sooner I stop losing money to them paying interest, and the sooner I can actually pocket money to put a roof over my head, food on my table, and then reinvest in making more cool products that also turn a profit, repeat until golden brown. If the essay above still doesn't help on why this stuff is priced the way it is, remember that when I make a controller for an XBox or a PS4, or perhaps a generic gaming controller for PC, the number of potential customers I can advertise to is in the millions, which means I can become a volume seller - e.g., I can sell at a lower price and still make the target ROI % If you STILL wanna gripe, I can't help you.

Hep burfdee Untied Status Marin Crops Dronk wooter cheng sox tek motrin

@Terry Dactil I have my engine fuel cutoffs mapped to detents on my Virpil throttle as well for the same functionality; I am still seeing this weird feathering behavior, from what I read in this thread, it looks like what I'm hearing is that I'm supposed to be flipping the mags off prior to actually shutting the engine down fully, which in reality on a piston engine is a massive no-no, so I don't understand why ED would model it that way. Proper order of operations in piston engine shutdown and feathering is power back (closed throttle), RPM back full close, feather prop, fuel shutoff, mags off when prop stops spinning appreciably. If mags are flipped off while fuel is still being fed to the motor (and its still turning) you're just flooding the thing and depending on how much fuel is getting fed, you're potentially damaging it as well, not to mention creating an insta-fireball-explodo-motor (potentially) if you are intending to fire it back up.... so... I'm confused. To get my engines to feather correctly under any circumstances, following proper procedure, I have to physically... very nearly stall the airplane to allow the prop RPM to fall low enough for the feathering system to turn the prop fully and THEN it feathers and holds still.

The english cockpit mod by Quartermaster had been broken after the last update in August, looks like he fixed it, its live on user files, here's the link: https://www.digitalcombatsimulator.com/en/files/3318687/

@dresoccer4 it looks like the author fixed the mod, new version is up. https://www.digitalcombatsimulator.com/en/files/3318687/

DCS tracks have never been reliable if they are long, complex, and/or multiplayer, and you are recording your own flight. If you wish to watch a long/complex/multiplayer track play back correctly, host your mission to a server and have another user join. As long a user other than you is the one recording the track that you end up replaying, that track will show (usually) properly, but again, not for the user producing the track. Meaning: Player A hosts server. Player B joins server and enters an acft. Player B sits on the tarmac or flies, whatever. Player A flies flight plan ABC to completion. Player B either does the track replay for purposes of video production/screenshots/review etc OR sends Player A his track. Player A runs Player B's track locally on his own machine and will be able to properly see everything that Player A did during the course of the track. The point: The events of the user who is recording the track will always be the events which become corrupt first in a track playback. If you want to see YOUR track playback properly, have someone else send you THEIR track of YOUR flight from the server you were BOTH in.

I found that the English Mi-24 knots airspeed cockpit published on User Files had broken with the last update.... poked the author about it, and it looks like he updated it this morning, thought I'd post the link just as a reminder for anyone using it! https://www.digitalcombatsimulator.com/en/files/3317374/

Honestly the criteria needs to be: 1. Neatness & cleanliness (is this a skin you would include in a full price industry leading product you hand to your paying customer, is it polished, appropriate and clean?) 2. Appropriate content - does this skin represent themes and content relevant to the aircraft module in question, and the PC sim customer demographics aligned interests as hobbyists in a general sense (does it speak to the PC sim customer broadly speaking)? 3. Historic accuracy - the vast majority of paying customers expect their module to arrive with a relatively wide selection of historically accurate/realistic skins which are both recognizable and highly polished. The "out of the box" experience for the first time user is the most important component in the sales and customer retention process, so expectations need to be met in this regard first and foremost. Fictional skins are a secondary concern, but users do expect some - for example, a national insignia for their home country because of the novelty found here (such as the US Army livery included by ED for the Ka-50). Outside of that, novelty skins really don't have a home being released stock with a module out of the box because it doesn't check any of those boxes for expected out of box experience; users do frequently get very excited about novelty skins as evidenced by the User Files library, containing tens of thousands of them, BUT the customer goes to user files to find them - its a destination for people who do want that, not an expected stock feature on purchase. To sum up, I just articulated why my two submissions can't and won't win the livery competition LOL