nessuno0505

There's also the english texture cockpit bug of the l-39, being there since the last three open betas and never addressed despite bug reports, then passed todady on release version. If this Is the state of things, they want us to use the open beta (I'd be for stable if It was supported, since I do not buy EA modules); release version Is Just a Legacy, so that if you have a blocking bug they can say "go to release, ob Is not for you". Neither release Is for anyone, being this state of things!

È che sto finendo lo spazio sull'ssd e tenere aggiornate entrambe le versioni, con le mie missioni salvate e le configurazioni tasti su entrambe, saltando di qua e di là, comincia a scocciarmi. Vorrei tenere una versione sola ma non so decidermi su quale, perché ci sono cose che mi disturbano su entrambe.

Riflettendoci, il vero problema di dcs è che la stabile non è supportata. Tutto il supporto e il bug fix si fa sulla beta, quando una beta è giudicata abbastanza stabile passa in release, e lì resta fino al ciclo successivo! Se qualche bug passa di là e lo fai notare, la migliore risposta che puoi avere è "already fixed in open beta". Ma allora se la versione principale è la stabile perché non la supporti, fai un hotfix e porti di là quello che hai già sistemato in beta? Invece no, sulla released non c'è nessun supporto, tutti i lavori sono sulla open beta. È questo il motivo per cui, a fronte di maggiori bugs, stanno tutti in open beta, anche chi non gliene importa nulla dei moduli nuovi in early access: almeno la open beta ha un supporto, se insisti può essere che il tuo bug tu lo veda corretto in qualche settimana; quello che passa in stabile invece è "per la vita", e così te lo tieni fino al giro successivo. Sulla stabile non c'è alcun tipo di supporto, per cui anche se sarei molto felice di usarla come unica versione, so già che al primo bug come quello dell'l-39 (vedrai che ci passa in stabile) ti tocca tenerlo per mesi. Una volta c'era la sezione sul forum per segnalare i bug in stabile, adesso è stata addirittura tolta del tutto! Messa così mi spiace dirlo ma la stabile è una legacy, forse la soluzione più bug free possibile è usare moduli released sulla open beta, sperando che i continui aggiornamenti non vadano ad intoppare qualcosa come peraltro spesso succede.

I do so, but the stable and the fully released modules are often full of bugs and we have to wait months for a fix. I'd be glad to stay on release and buy only finished modules if the release version was supported. It Is not. The only supported version Is the OB, when they are quite satisfied they "freezes" the OB version and call It stable; but if a bug pass through you have only a "fixed in OB" answer and have to wait. No hot fixes and such. That's why the whole community Is on OB. Please ED support the release version too, give us hot fixes when needed and do not support OB only. Thanks.

I have both but I'm thinking to keep only stable; there are too many bugs in OB and they don't get addressed quickly, sometimes they even pass on stable. Fortunately some of them have community home made solutions, but the frequent updates of the open beta force me to recheck and redo fixes every week. The 3 months cycle of the stable Is, well, more stable, since you have to deal with bugs and fix only once until the next update and not every week. However I do not fly online. I think that the vast majority of servers being on open beta Is a weird thing and the main problem in dcs community. People can't wait and wants news as soon as possible, but the main reason of the open beta should be tests and to help the developers. Unfortunately this Is not the case, even if ED itself suggests to do so. Things being this way, maybe just one public version (hopefully with slower updates than OB) could be a solution.

Tanto domani passerà su stabile e tu non hai idea di quanto mi facciano girare le gonadi queste cose...

I know it's off-topic, but could you please fix the l-39 missing english cockpit textures before bringing it to stable? It's an easy solution, do not let game-breaking bugs pass in the stable... ehm... release version, come on!

E' sia sul C che sullo ZA, ma solo nel cockpit inglese. C'è un fix della community, basta aggiungere la parola "false" in due files di testo. Certo è assurdo che un bug del genere, che non ti consente di volare, è ampiamente documentato e ha già un fix, non sia implementato nativamente dopo ben 3 patch della open beta. La ED non si smentisce mai, queste sciocchezze davvero snervanti continuano ad uscire in continuazione. Io sto fermamente pensando di passare definitivamente in stabile, almeno ho gli upgrade ogni 3 mesi e se devo fixare manualmente qualcosa lo faccio una volta e poi sto a posto, non devo ripetere la cosa ogni settimana! Dovrò aspettare per usare l'a-10c II, ma tanto ha talmente tanti bugs reported che non lo sto usando lo stesso, a questo punto tanto vale stare in stabile.

Ok there's a fix, but it's a shame it's not already fixed since it's a very easy fix, it's enough to do what the community has already done. They do not have enough time to add five letters in a text file?

It's a shame.

Thanks all for the kind answers, and yes I know about import taxes since I already bought collective lever by K-51, also from Russia. I'll take a look at Andre's shop.

Sorry but I have some problems in understanding the differences: 1) the jet pads: basic, flightsim or simracing editions: all have 8 motors, is the differences only in shape, measures and motors position? Since I use an Ikea armchair in my simpit, maybe the basic edition is enough, I'll check dimensions to be sure. Am I correct? Is the control unit included in the jet pad or has it to be bought separately? 2) the software: I need simshaker for aviators (freeware right?) to play dcs and x-plane 11, the main reason I'd use the hardware; but for il-2 great battles I need simshaker wings too (payware) and for euro truck simulator / project cars 2 I need simshaker wheels (payware) (I use a different seat for driving games and I play them rarely, I should have to remove the jet pad from my flying simpit to put It in the driving seat, not so comfortable to do every time so maybe I can live without simshaker wheels). Another question: "6 pad shakers support Is a paid option": what does this mean? The jet pad has 8 motors! Are pad shakers something different and in addition to the jet pad? Maybe if I had to buy only standard simshaker wings/wheel editions I could buy both even if I rarely drive. My need is to add a bit of haptic feedback to my VR experience, thanks for help.

I'm interested in buying one, is this available? Should I order from Andre's shop or gametrix page? What software do I need? If I intend to use both with dcs, il-2 and car sims, do I have to purchase three softwares? Thanks. P.S. Just a question on gamepad integration too: does It work with wireless gamepads? Thanks again.

As Snoopy said, in the real airplane there's a mfcd osb with that function, currently not implemented in the simulation. It has been asked to add It, let's hope ED decides to.

If we'll have the three options, as it seems to be, it's the best thing for everyone.

If it's correct as is it's ok, I do not want fictional functions; if there's a mfcd osb to boresight the tgp in the real airplane, let's hope ED implement this as soon as possible.

The devs should be informed about this since there's a wishlist in which they say they'll add the option to be one eye only as - according to someone posting pics - so should be: https://forums.eagle.ru/showthread.php?t=287543

It's already reported afaik

Maybe you should open another bug report under the "bugs" section; if the devs marked this as [already can], they won't look here any more.

Do not rush people! The open beta - with the a-10c II introduction and some other tweaks - still has bugs to be fixed; it is better to have a slower stable but with as few bugs as possible. There's an option (something like update@openbeta / update@stable command - I do not remember well, check the forum) to pass from stable to openbeta and viceversa, without the need to keep both installations side by side, if SDD free space is an issue.

Open beta hot fix yestedrday but bug still there. You are right, I go report it in the right section. I really appreciate ED work, but these - in some way stupid - things still happening despite the flowing of time are maybe the things that keeps ruining an otherwise perfect experience (and I mean DCS in general).

See the attached thread for logs, pictures, diagnosis and users' manual solution; please just add the fix to the next official open beta update, thanks. You cannot loose yourself in such a cheesy bug! P.S. the bug is cheesy, but the frustration in finding it - and it is game breaking - coming here on the forum, searching and studying for a manual solution, is huge. Fortunately we can find one, but it's not always so easy for any forsaken bug. https://forums.eagle.ru/showthread.php?t=286610

A-10c II Is an outstanding module and I have bought It immediately, even if I usually di not buy early access stuff; nevertheless if everyone upgrades to a-10c II the fate of the original a-10c Is inevitably sealed.

The answer at the first question I suppose to be yes, now. There were problems in doing so with the initial release, that should have been fixed with the last hotfix (see changelog). I do not know about the second question. By the way, I wonder: if someone does not have the original a-10c and buys a-10c II, does he get both modules? And if so, can he choose to install just One of the two?

At the moment a-10c II Is only for open beta; in any case, you'll have another module (a-10c II) side by side your current a-10c.