Leaderboard

if they make me wait another 2 months while youtube plays around, im gonna be pissed.

Pantsir SPAAGM 1.4.0 released! Changelog Version 1.4.0 Added desert livery Fixed autocannons ranging issue

The contents of this topic is IMHO self inflicted. It is caused by conflicting communication or lack thereof. On one hand it is "soon", "very soon", "sooner than you expect", "the year of the Eagle" etc. usw. on the other hand they refuse to communicate any time frame or date at all while at the same time ramp up the marketing. That the customer who already paid becomes frustrated by this behavior is to me to be expected. All I want is any official time frame or date. That's it. Maybe it is not up to Razbam and ED wants to, finally, update the stable version and wants to include the Strike Eagle right away in the stable version rather than just the Beta. But then just communicate that. I think people are actually able to comprehend stuff like this. All this secrecy and uncertainty is annoying.

My 2 cents. As far as I could piece together from Discord, the F-15E was supposed to be released "early June" (internal EA release date), also made apparent by the start of the pre-release marketing campaign, which was pushed to the 9's ("imminent", "beware the pre-release discount", and sending out EA copies to every YouTuber with more than 10 subs ). Only for - allegedly - ED asking RB to push back the release date to July at the 11th our, with, according to some mods on the Razbam discord, the F-15E module itself not being the issue. Should that be the case, there must have been something from ED's side, which we can only guess (like they might want to get another patch in, which would be good, or they want to give another 3rd party module the limelight without it being drowned out by the Strike Eagle release, or, or, or.....) Apparently, last night some people affiliated with RB "spilled the beans" (presumably out of frustration over this last-minute delay, and completely underestimating the <profanity>storm this would trigger), hence the already rather volatile part of the "community" (I hate that term) was being made aware of the "missed opportunity". Without those "whistle blowers", no one would have been any wiser, albeit some being annoyed that "influencers" get to play with the module publicly, while they have to wait (to which I could only say: start your own popular YouTube channel!). My unsolicited advice to ED would be to recognize that the cat's kinda out of the bag now, and communicate the reason(s) for this last-minute delay to the "community" (again, hate hate hate that term ). Otherwise, conspiracy theories will inevitably pop up (already have), and many will be left in a negative mood. For example, it would be quite reasonable that ED would want to wait for some core engine patch or fix to be ready pre-release, or wait for another module (Sinai) to be ready for EA. Strike Eagle + Sinai would make for a nice "bundle" release. So no shame admitting to that if that were the case. In any case, personally, I can wait for another month; got enough on my plate as it is. BTW, I finally pre-ordered the Strike Eagle last night. Just to be contrarian.

Everything from statements made about imminent release to YouBoobers getting early copies has led to a belief that release was just around the corner. To come out now and tell people July (maybe) is crude and a big slap in the face to their customers, whether it is ED's fault or Razbams. It is in very poor taste and not good business.

Right now, I'm pushing for June-ish. Was trying to get it out in May, but a few things require additional cleansing and tweaking. I am travelling for work right now, so available time to code is minimal.

On 20 May 2023, Brian Shul, probably the most famous SR-71 Blackbird pilot, passed away shortly after giving a speech about his favorite aircraft. https://theaviationgeekclub.com/sr-71-pilot-brian-shul-famous-for-his-ground-speed-check-story-passed-away-while-giving-a-speech-about-the-blackbird/ I'm sure you've all heard his L.A. speed check story countless times, but I for one can never hear it too often. Here's to a fallen hero: RIP Brian, you will be missed. Of course I also thoroughly enjoyed the Blackbird episode on the Fighter Pilot Podcast and highly recommend to anyone to listen to it, if you haven't already: https://www.fighterpilotpodcast.com/episodes/051-sr-71-blackbird/

>blindly pre-orders without knowing the release date >gets mad when because release date isn't soon enough lmao it's entirely your own problem! If you were myopic enough to place a pre-order without knowing a release date, don't complain when a release date is announced.

RAZBAM really needs to brush up on the art of the tease. Typically, you want a teaser to excite and motivate your target audience, not deject and piss them off. Did they really think revealing a July release date in this manner through the official Cold Start video would make anybody gleeful with anticipation? They really weren't joking when they said this was the "year" of the Strike Eagle. However, it would have been more accurate if they said, "you'll be waiting another year for the Strike Eagle".

Agree. The issue (for me at least) has never been about the date, the development timeline, etc; It is about setting expectations. I don't believe it to be a good marketing practice, nor particularly helpful, for a company to say something like "the release is imminent" when it is still six months away. I believe most would find this misleading. As recently as two weeks ago, Eagle Dynamics said on their twitter "the Strike Eagle is coming in hot and soon you'll be able to fly this..." and "we are getting close now"... If one of my employees told me those statements, then said we're a few months off, I'd be pissed. This really isn't a new thing. I'd advocate for pre-orders to only go live with an anticipated early access release date. For those that disagree with me, I appreciate your opinion. I only write this stuff in hopes that maybe Razbam, Heatblur, and particularly ED receive the feedback as constructive and stop saying things like "release is imminent!" when it is still months away. I'm sure they hate seeing all the disgruntled comments on the forums, but I'm not sure they don't feed much of it.

Magnitude3 FB https://www.facebook.com/100057409782744/posts/pfbid02qaEHuiCVfxSi1xU66nUDfF2JVnfinLENPjCt5Y2r5oPSMMUrwy5FYh1rFiv3Denol/ Enviado desde mi CPH2197 mediante Tapatalk

Lots of WIP!! Trial and error. Hmm, I wonder if Chat can create

@StreakerSix Location: [game drive]\DCS World OpenBeta\Mods\aircraft\Uh-1H\FM File: FMOptions.lua Open with Text Editor, 2nd Line: New_engine_model = true change to: New_engine_model = false

Lol the year of the pre order.

Mir persönlich war der Marketing-Hypetrain diesmal insbesondere angesichts der teils konfusen Kommunikation so viel zu viel, dass ich auf jegliche Gedanken an eine Vorbestellung verzichtet habe, obwohl ich schon lange auf eine vollwertige F-15-Umsetzung für DCS warte, weil dieses Modell für mich nicht zuletzt auch zu den ikonischsten Maschinen der 70/80er Jahre Jet-Generation zählt und in jede gute Sim-Sammlung gehört. Früher hätte ich wohl rein aus Neugier ungesehen so früh wie möglich zugeschlagen, um nix am Tag X mit dem EA-Release zu verpassen. Aktuell überlege ich mehr, ob ich wirklich noch ein weiteres hoch komplexes Modul in der Sammlung brauche, für das ich beruflich wie privat bedingt absehbar auch nur annähernd vernünftig Zeit finden werde. Vllt. bin ich auf einfach mittlerweile zu alt für so ein "Influencer-Marketing-Blah" und die jüngeren Generationen brauchen so etwas unbedingt, um angemessen aufgeregt sich auf etwas Neues vorzubereiten und einzustellen. Mich regt so etwas eher umgekehrt auf und kühlt damit reichlich jegliche Vorfreude deutlich ab. Wenn dann noch handwerklich in der Kommunikationsarbeit (mein persönliches berufliches Fachgebiet) am laufenden Band so gemurkst wird, wachsen meine Zweifel an der Gesamtkompetenz der Beteiligten deutlich an. Vernünftige Public Relations und Öffentlichkeitsarbeit (sowie Projekt Management allg.) sind wahrlich kein Hexenwerk und sollten zumindest anhand üblicher Standards auch von professionellen Firmen jeder Art beherrscht werden. Immerhin haben wir es hier nicht mit einem Amateur-Modding-Projekt zu tun - und so manche Modding-Truppe bekommt das jedoch deutlich professioneller hin. tl/dr: Aus meiner Warte haben sich weder ED noch Razbam mit dem gewählten "Anpreisungs-Vorgehen" einen Gefallen getan und zumindest bei mir eher das Gegenteil von Vorfreude erzeugt bzw. die einst vorhandene Vorfreude sogar nachhaltig reduziert.

Yet your user account is just a couple months old

Those Youtube-Influencers are just a modern marketing channel. It is advertising. They are attention multipliers. It makes no sense at all to hate on them or be jaelous. It has nothing to do with you preordering. You are a customer. They are means or tools. One could argue about the timing to start such a marketing campaign and personally I'd put it closer to EA-release. But other than that...... edit: grammatical corrections

We have a release date/month until another delay.

Thank you very much, I really appreciate the kind words! In regards to making them official, it's a double-edged sword. The upside would obviously be getting my hands on official documentation and the increment update nature of DCS. The downside would be less control over my work, not being able to implement the weapons/assets I want, coordinating with a much larger organization (development gets slower), a much slower update cycle etc. So at the moment I'm pretty with how it is, weighing all the pros and cons. Especially since this is a hobby of mine, I already have a full time job. I could definitely be interested in adding these kind of assets, the issue is getting good enough models.

You're right, there is always a big backlash when these developers miss dates. Having said that, that is exactly what is driving this backlash. Saying that the release is "imminent" or "very soon" when it is months away is effectively the same as missing a date. It sets an expectation that is then not met. The alternatives are 1) setting a date and sticking to it or 2) keeping your mouth shut until you actually can see a release date that you can execute (i.e. know as a fact that you can release next month because the product is ready to go today, announce the date, open the "pre-order", and release as communicated). A really good way to do things would be to say "we could release today, and ED agrees, so we'll announce a release date three months from now. We'll spend that 90 days polishing, testing, and adding any "nice to have" features, but ultimately the product is ready to go now, so there can't be any delays."

Version 1.3.1 Major Feature Update -- 20230524 After unleashing the flareZone fireworks onto your missions with the last release, another high-octane eye-candy module hits DML: stopGap. Inspired by @Hardcard's seminal SWAPR script, and egged on by @Adalla, the stopGap module today makes it's DML debut. stopGap significantly dials up the 'wow'-factor of your missions: usually, all player aircraft slots on an airfield remain empty, making it a lonely experience when you start your engines in a big (read: many different player slots) mission. StopGap swoops in, and replaces all those gaps with static versions of the player planes. Your mission looks much better, and - depending on how many planes, and how many different planes you provide to your players) your frame rate can take a tiny (normally) to perceptible (on extreme missions) hit. Since the replacements are all static, they don't impact the mission's performance much. Although the stopGap script has its own page here as a stand-alone module, the DML version - being able to rely on DML's powerful framework - is more powerful and easier to use. Admittedly, stopGap isn't that hard to use (you install it, end of story), so 'more powerful' is just me making pompous announcements. Of course, as always there's a demo for you, with its own discussion in the manual. Oh, and speaking of the shock block: it's now officially "not short". Then: It took me a while, and I've now finally completed upgrading (or as we nerds say 'refactoring') the 'ownedZones' module with a bunch of now abilities. During this upgrade process, I separated unit production from ownership, and gave the production stuff its own module: factoryZones. Taken together, ownedZones and factoryZones have gained the following abilities: zones can now (optionally) be captured by helicopters, planes (very tricky to do unless you are in a Harrier), and naval units. And yes, this means that now water-borne ownedZones (e.g. around oil rigs) are possible. they support quad-based (polygonal) zones (finally!) custom color schemes. You are no longer restricted to boring red/blue/grey. You now have access to the full RGBA color space. factories use a powerful 'inheritance' model for production that makes it much easier to set up which units a factory produces for which faction. a host of additional outputs! for your missions to create signals for other modules as input? 99% backward compatibility of ownedZones and factoryZones to the legacy (pre 2.x) version of ownedZones (you may need to add a 'factory attribute for some zones) There are now two additional demo missions dedicated to conquered zones and factories, and the original demo mission's documentation (using the legacy version of the module) has been amended. The legacy version of ownedZones remains in DML and will be maintained if necessary (bugfixes only). Taking to heart some comments from you guys, I spent a good part of the last two weeks revising the main manual's section on flags. It's not a complete overhaul, but I hope that the new graphics and explanation help to understand this somewhat esoteric, yet fundamental topic. My thanks to you for the feedback - keep it coming! All Changes Documentation Main - flags in DML (rewrite) - liveNumber '#' attribute definition - stopGap documentation (new) - factoryZone documentation (new) - ownedZones documentation (rewrite) - various modules: update (mainly # attribute updates) - no gaps no glory demo documentation (new) - owned zones ME integration demo (update) - my first factory demo documentation (new) - owned zones and factories demo (new) Demos - my first factory (new) - no gap, no glory (new) - once, twice, three times a maybe (update) - owned zones and factories (new) Modules - cfxGroundTroops 1.7.8 strengthen guards before envoking ownedZones methods - cfxMX corrected typo in remarks, no change - cfxOwnedZones 2.0.0 - massive rewrite - colors for zones - capture by sea, air possible - poly zone support - cfxZones 3.1.0 - RGB zone property handling - factoryZone 2.0.0 - split from owned zones - production inheritance - poly zone support - limitedAirframes 1.5.4 - red# and blue# attribute naming updates - mxObjects experimental module, do not use - playerZone 1.0.1 - pnum# attribute name update - stopGaps standalone (new) - stopGaps (new) Phew! Enjoy, -ch

Sehe ich normalerweise genauso. Allerdings - wenn das stimmt, war die Freigabe der ganzen Infleuncer-Videos, die gerade hereinprasseln, zum jetzigen Zeitpunkt etwas ungeschickt. Gelinde gesagt.

User can't join a server because of the mod (modification of the game, not supported by devs) he himself installed. The owner of the server allows pure clients only, which is his right and own decision. User quits but yet still seeks attention on the forum. Please, don't go.

Just become a YouTuber and you get one for free right away! :)

You got the discount. Other than that, there is and never was any "reward" to pre-ordering.

EA 072023 The image posted and Combat Aircraft calendar seem to suggest July

'Weeks not months' my backside, if this is the case.

if thats the release date, im gonna be pissed

Black Hulls, with a very slight hint of red, look better - MUCH better. I will do another set of the Type 26 and the Type 45's with black hulls and post them here in a day or two. - Done - see below. The ship on the left is a red hull, the other 2 are a type 26 and a type 45 with black hulls. You decide ! Here is the updated link with black and red hulls for both the Type 26 and the type 45 - you can have any colour you like - as long as it's black, or red. You can mix and match, simply drop the folders into your liveries folders for each type. All that is different is the hull colour, the rest of the ships are the same for each hull color. https://www.dropbox.com/s/kpk0g9getegkguc/CrazyEddies Type 26 and Type 45 Liveries.zip?dl=0

+1 for trees appear too big in many scenarios. The lower and slower you move, the more off it appears.

I started looking and looking for information about the second world war, there is not much information, except for what is on the Internet (Wikipedia was my main source). I found some pictures, but this does not give a complete picture of the fighting. I also found maps, on this source, of course there are not many of them, but at least like this: https://www.oldmapsonline.org/en/Al_Qahirah#bbox=30.65074010712502,29.340328798767274,32.1770948325,30.51534107021223&q=&date_from=1960&date_to=1980&scale_from=&scale_to= I did not find: - what the airfields looked like (but their location can be found, i mean Egypt side) - shelter objects - Israeli airfields - etc.. any thoughts? please advise

Well no, because everyone understands what the chart shows and then extrapolate from that. No performance chart for an aircraft can show every possible kind of variation or permutation, you have to extrapolate everything inbetween. In DCS we have the luxury to actually be able to test more exactly against them which helps us recreate them.

To be honest, I don't blame Razbam, I blame ED. They are the only ones to blame for this and it's actually quite easy to rectify. First off, I don't care about launch dates. I'd rather the module be in good state before release more than just getting it as soon as possible. This month, next month, next year, whatever. What I don't like is the process for pre-purchase. I'm not against pre-purchase as a whole, I'm just against the way ED does it. I basically never purchase modules until the release date is pretty much assured. The pre-order price is the same the day before launch as 4 months before launch. What I noticed with this module is that there has been a lot more "soon", imminent etc. passed about not to mention tweets alluding to impending release. I broke my own rule and pre-purchased last month because I THOUGHT by the tweets that the launch was actually IMMINENT. Silly me. Here's an idea for Eagle Dynamics. How about you don't launch pre-orders until the module is ACTUALLY ready for launch, meaning beta tested and given the green light to release. A Friday news letter would come out saying: "We are pleased to announce that the much anticipated (insert module} has been in the beta testing phase with us for the last 10 weeks and we are pleased to announce that (insert 3rd party) has been given the permission to launch. As of today we will be offering a pre-purchase discount which will last until (insert date) at which time it will change to an E/A discount. We hope you enjoy the YouTube videos about to be coming your way as we await launch day (insert official date). End of problems. The only thing that should cause a minor delay of a couple of days would be on ED's side if there was a beta patch issue not a module issue. It ends all complaints about changing dates/ no dates/ taking money months in advance etc. Just a thought. I think it's more fair for the customers and especially the ones who are willing to slap down their credit card early.

I didn't found how to do this in game, but I've found how to manipulate the LUA file to obtain a toggling view without going in toggling mode (for anyone that may have the same question one day...). This is the LUA part where it is controlled: {combos = {{key = 'Num0', reformers = {'LWin'}}}, down = iCommandViewSnapView0, up = iCommandViewSnapViewStop, name = _('Custom Snap View 0'), category = _('View Cockpit')}, {combos = {{key = 'Num1', reformers = {'LWin'}}}, down = iCommandViewSnapView1, up = iCommandViewSnapViewStop, name = _('Custom Snap View 1'), category = _('View Cockpit')}, {combos = {{key = 'Num2', reformers = {'LWin'}}}, down = iCommandViewSnapView2, up = iCommandViewSnapViewStop, name = _('Custom Snap View 2'), category = _('View Cockpit')}, {combos = {{key = 'Num3', reformers = {'LWin'}}}, down = iCommandViewSnapView3, up = iCommandViewSnapViewStop, name = _('Custom Snap View 3'), category = _('View Cockpit')}, {combos = {{key = 'Num4', reformers = {'LWin'}}}, down = iCommandViewSnapView4, up = iCommandViewSnapViewStop, name = _('Custom Snap View 4'), category = _('View Cockpit')}, {combos = {{key = 'Num5', reformers = {'LWin'}}}, down = iCommandViewSnapView5, up = iCommandViewSnapViewStop, name = _('Custom Snap View 5'), category = _('View Cockpit')}, {combos = {{key = 'Num6', reformers = {'LWin'}}}, down = iCommandViewSnapView6, up = iCommandViewSnapViewStop, name = _('Custom Snap View 6'), category = _('View Cockpit')}, {combos = {{key = 'Num7', reformers = {'LWin'}}}, down = iCommandViewSnapView7, up = iCommandViewSnapViewStop, name = _('Custom Snap View 7'), category = _('View Cockpit')}, {combos = {{key = 'Num8', reformers = {'LWin'}}}, down = iCommandViewSnapView8, up = iCommandViewSnapViewStop, name = _('Custom Snap View 8'), category = _('View Cockpit')}, {combos = {{key = 'Num9', reformers = {'LWin'}}}, down = iCommandViewSnapView9, up = iCommandViewSnapViewStop, name = _('Custom Snap View 9'), category = _('View Cockpit')}, removing the "up = iCommandViewSnapViewStop" part, will make the snapview to stay.

+1 ... I pre-ordered last week ... got to say that I love your use of "" and agree with most of your post .. I wish that the delay were to allow the La-7 a release ahead of the F-15E

I'm hoping that there's a lot of barking about nothing here and that it's coming earlier than we are guessing, but we'll just have to wait and see what ED says when they announce the date. If we are looking at a July release, I would just like to add to the voices that says maybe we shouldn't make this practice standard. I don't love it, but I can understand giving YouTubers an advance copy for marketing purposes a week out or so to generate hype and get people seeing the product in action. But over a month I think is too much, both as some select few get to learn and play the module for far longer before the rest, and because that hype turns to annoyance having it that far out.

Not at all. I'm happy to see the content. The problem is in the reveal of the date. RAZBAM is clearly aware of the intense anticipation for this module, the long road it has been, the clamoring for release date information and the expectation that upon release of the official cold start video, the wait would not be long. Revealing that the release is still some ways off to a date in July, possibly even toward the end of that month, was callous and not very thoughtful. I think some form of a press release, giving details of the state of the module, acknowledging the long wait and perhaps explaining the reason why release must still be more than two months away, would have been much more prudent, understandable and would have assuaged some of the frustration over such a surprising reveal.

July isn't the issue for me. I think that Razbam should have been more transparent over the release, giving us a date from the start of the pre-order, at least, even if it would be postponed. That would give us an idea on how the development is going and when to expect a release. If they have said that it would release in August back then, I wouldn't be so disappointed as I am now, considering the release is in July...

DAS Buch zur SR-71 schlechthin (zumindest aus Pilotensicht) ist wohl Sled Driver des am vergangenen Montag verstorbenen ehmaligen SR-71 Piloten Major Brian Shul. Leider ist das Buch nur sehr schwer zu kriegen (und natürlich auf Englisch): https://www.amazon.de/Sled-Driver-Flying-Worlds-Fastest/dp/0929823087 Alternativ sind aber auch seine Vorträge sehr zu empfehlen, denn er war ein super Redner der seine Erlebnisse auch sehr unterhaltsam rüberbringen konnte:

Once we are 100% sure of the date we will let you all know, thank you for your patience.

Hi again. Thank you all for your patience. Although the tests we've performed initially offered positive results, we've decided to raise this internally for further analysis. Stay tuned for possible future improvements.

Sehe ich genauso. Die Community ist mittlerweile einfach so... schwierig. Kommt es nicht schnell genug, nur weil man vielleicht einmal zu oft "imminent" oder "year of the X-Wing" gesagt hat -> sind alle upset. Kommt es zu früh mit einem Sack voll bugs -> sind alle upset. (siehe F-16) Perfect, good or moderate timing -> impossible Bad timing -> garantiert! Dazu noch ein Haufen DCS-YTler die andauernd sagen: It' just around the corner! Almost there! Imminent! Probably this month! Und die Leute legen das in den Mund von Razbam.

yes please make a post in the bugs section with a short track example and video / pictures of the bug you see. thank you Sorry to hear you have quit, hope you return when you are ready to, our work is constant so maybe we can meet your expectations one day. all the best to you. -------------------------------- folks please keep this thread for patch notes discussion

I think its pretty obvious that the tree size in DCS is slanting towards the bigger end, probably for performance reasons. There are basically no small trees. And maybe its "just" 50% higher than average fully grown tree, but it seems decidedly so.

Stay tuned WIP Coming soon!

Mine will be released together with the Kola map. (= I haven’t the faintest idea when) But I’m sooo looking forward to FIWOS and The Gamblers! The sample mission is a work of art!

Maintenance didn’t like taking the tanks off for the sole reason that it sucked. You needed four guys on either side and one guy working the standpipes and the latch and you reached under and locked arms and grunted, groaned and cursed while the guy tried for five minutes to get the god damn standpipes to line up.

Knowing the release is in july I will not watch any more youtube videos of the F-15E since I can take it more easily plus I don't like most of the DCS youtube creators. I would love to have the manual though, the manual is important for me while waiting for the release.

The previous brakes didn't need to provide much brake torque, as there was so much rolling resistance it was as if the brakes were being applied at all times. Now that rolling resistance is much lower, we have to crank the max brake torque back up. This issue was discovered just after the submit deadline for the last patch. They'll be able to hold Zone 1 AB in the next patch.