Jump to content

shagrat

ED Translators
  • Posts

    13344
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by shagrat

  1. That's how bugs make it into releases... And yes, they need to compile at least one new build and test/QA it with the beta testers if the bugs are fixed and no new critical bugs are introduced. So splitting this into two releases only adds more workload.
  2. That doesn't work, as it means compiling a build minus with the campaigns and the current (!) DCS version that needs to be tested, to ensure the Campaigns at least work somehow decent enough... and that's assuming the Missions don't use any new script/trigger feature that requires the new build... The eternal circle of development hell.
  3. That exactly was my suggestion. It's not even too many "irons", it's the self imposed pressure of release dates, way before a release is ready to be released. That doesn't mean there won't be any bugs in the patch, but it will stop the drama...
  4. Not if there is no announcement that there is a plan. It will work for future patches. Simply announce a date AFTER you have a tested and release ready patch. ED could even delay the patch for weeks if necessary and as soon as they have a patch ready announce the "planned" release of that exact build in a week from then. The development isn't impacted as that is done in seperate branches anyway. Thus no delays, patch will always drop on the planned release date a week after it is done.
  5. I don't mind waiting, what I mind is getting a promise every day that tomorrow I get my present. I would prefer to walk into the living room and "surprise" my present is standing right their...
  6. Yes, but I rather prefer an announcement of a working patch after the patch is ready instead of an advance announcement, that basically is the "hope" to manage to have a working patch in the near future, with a date that's unreliable anyway. What's the problem with a surprise announcement: "Today is patch day. Patch is live." ?
  7. I'd like to add, that Kandahar (KAF) was home to a constant detachment of US and UK aircraft, during the depicted timeframe (2008-2011). Well, actually since December 2001, both FOB Rhino (later renamed Camp Dwyer) and Kandahar Airport (KAF) were established and under coalition control, so landbased operations for aircraft in Helmand is a reality for anything, shortly after December 2001(!), let alone 8-10 years later.
  8. Oh, so you really missed the 3 tweaks that already happened? How come?
  9. Huh? My job pays my wages. I am a normal customer, when it comes to buying DCS modules. And what triggered that reminder, was the "at release" comment, which hinted at the usual perception, that early access, equals release and thus claims to a certain feature set, necessarily implemented. As i said, my educated guess is, they will have trim at early access, but not the sophisticated real life features. Force Feedback support would be a nice to have, but I remember a time, where non of the modules had even basic FFB support and only in the recent years were new FFB sticks available, usually home made "3D print prototype" turned small business. It took some effort for ED to get their hands on old working MS FFB-sticks etc. to even be able to develop/test FFB implementation. I hope they do have basic FFB support on early access, though. Worst case I need to use the Hardware "Force Trim Release" Emulation.
  10. Man unterschätzt, allgemein wie wichtig generell das Scenario und die Mitstreiter sind in so einer Mission. Der Spielspaß kommt ja nicht ausschließlich vom "Dinge in die Luft jagen". Das meiner Meinung nach große Problem der Huey in DCS, ist die meist sehr feindselige Umgebung, die gerade im Multiplayer häufig, schlechte Jet-Piloten animiert, auf wehrlose Helikopter jagd zu machen, die mangels funktionierender CAP ein angenehmeres Ziel sind, als gegnerische Abfangjäger, oder mit absurd überzogenen SAM-Stellungen geschützte Bodenziele anzugreifen. Da hilft nur selber machen, in kleiner intimer Runde.
  11. Btw. I am confident "basic trim" is meant as opposed to "Advanced trim system of the real helicopter, that has hovering assist modes and other highly advanced stuff, like the Apache's hold modes, that took a couple updates during the early access phase to be implemented". Just speculating, here.
  12. No need to rant. You can always NOT buy, like in every store in the world... That's how a store works. Offering something... and if you don't like the offer, you need to decide if you buy it, or pass, until you find something that suits you. Do you go around shops in your town and complain about all the stuff they offer, that you don't like to buy? Edit: and the release(!) is still years away. The early access phase is next, and that's what they deliver for early access. So of course it is incomplete! That's why it's called "early access".
  13. Offering to safe some money through pre-order or early access purchase?
  14. Jedes Jahr mit der BO ist ein gutes Jahr!
  15. Nee, ist genau dasselbe. Versteckte Statics sind auf der F10-Karte usw. unsichtbar. Nur George und Petrovich "sehen" sie trotzdem. Eigentlich sollte der FARP mit diesen Settings in game komplett unsichtbar sein, sowohl F10-Karte, als auch auf MFDs...
  16. Try not(!) applying a curve to the axis. Try a small deadzone and linear curves with lower Saturation if you need to slow the movement. This was the solution to a very similar problem with the AV-8B slew, IIRC. Maybe it is the same.
  17. You could, but that's still only on your end and will cause issues with any online service, cloud applications etc.
  18. No intention to scare, trying to educate...
  19. First you should read the EULA before giving (wrong) legal advise. I also recommend to add an "I am not a lawyer, this should not be taken as legal advise" disclaimer, in case you are based in a country where negligence may be a civil law tort that could get you in trouble. I am not a lawyer, so this isn't legal advise. Fair enough. But I think it would have been best for all involved if this has been kept between the involved parties. But that's just me.
  20. They couldn't, because in the industry the first thing even before drafting the first contract document, is usually signing a mutual NDA.
  21. You sure have analyzed the source code and identified the "time bomb", so you can definitely rule out a simple issue with the signing certificate for the .dll?! Or any other possibility? ...or are you making assumptions to present them as fact? This is part of why this is blowing up and rumors overshadow any reasonable information.
  22. I recommend to combine the 5-way CMS hat with the disconnect lever, or Pinky button, as modifier. Gives you 10 commands with 6 buttons. - CMS press: AI on/off - CMS fwd/aft: speed - CMS left/right: heading with lever/pinky held as modifier: - CMS press: Hover - CMS fwd/aft: Altitude - CMS left/right: drift I put AI HUD on the equivalent of the Master Mode button (right side of the stick) with modifier.
  23. I highly recommend you don't buy it. It isn't what you are looking for. The focus isn't on the rivets, and appearance of textures from 20-30cm away, which seems to be of utmost importance, to you. I personally prefer the focus on actual flying and working with the systems and especially the environment while I look outside. The cockpit is pretty decent. It looks very close to the real thing. Only issue that bugs me currently, is the L2MUMS doesn't export to a separate screen, only the MFDs content. The L2MUMS page doesn't. Lot if fun, flying a module that's combat ready (complete system wise).
  24. Do you really think they didn't update the textures, never introduced normal maps and improved the 3D Model in 5-6 years of development, while the DCS graphics engine was overhauled two times and forced all existing modules to adjust? Really? It actually looks very close to what I see in that picture...
×
×
  • Create New...