-
Posts
13366 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Events
Everything posted by shagrat
-
6 Buttons, 5 + 1 modifier. Up/down, turn left/right and Hover. Modified: Accelerate/decelarate, drift left/right and anything else I'll put on the five top row of the MFD frame buttons. ...the benefit is: No need to constantly remember in which mode you are currently and clicking through 4(!) modes to get to the one you need, or more if you clicked too often.
-
It's feature complete for Release. It won't be bug free, and it may get additional features, later. That's called updates. By your "very creative interpretation", the DCS A-10C and Ka-50, along with every other module would always be in Early Access, as they are still getting new features, better textures/3D- models and bugfixes. Name any module, that wasn't updated after release? Even FC3 got multiple additions...
-
From what I understood even they took over the complete project. I am sure they did redo the 3D-model to adjust for the new DCS features, but that's basically the same for all DCS modules, including the Polychop OH-58D... The Heatblur F-4E Phantom II is now in Early Access, so it still has a discount. The Polychop OH-58D will not be released as Early Access, so the whole comparison is apples and oranges...
-
They took the whole project from ED/Belsimtek...
-
Not sure, but could it be you forget to de-slave, by pressing the slave button, again? Press and release Slave button > TADS is now slaved to the HMD (Sight) and follows where you look. If you look at the correct place: Press and release the Slave button, again > TADS stays on the point. Now, select TADS as Sight with Sight-Select-Switch right (TADS), to control the TADS.
-
Because it isn't in pre-order or early access... Feature complete ready to enjoy product = full price. Wait for the time the KW participates in its first sale, if you want a discount. Actually it was announced by Belsimtek in July 2017 (close to 7 years ago). Then ED and Belsimtek merged and the F-4E was "on hold". Then ED let Heatblur take over the project.
-
You were referring to "the IT market", not DCS or even Flight Simulations. The Information Technology market for software is dominated by SaaS and long term Enterprise Agreements. What you now talk about is the "Computer gaming market", specifically. ...and then there is a small subset of Flight Simulation games, further divided in civilian and combat/military flight simulation. Then there are a handful of products, of which round about one(!) does all era including modern and WWII combat aircraft. THAT is the "IT market" you meant. I agree, everyone should be old enough to make his own decisions. I am sure it will.
-
Nobody is forced to buy anything. I am just wondering why people start whining, if they don't get discounts, or other incentives? A typical "marketing reaction" would be to adjust the standard price, accordingly and add a "discount" to get more initial sales...
-
So you are extrapolating your own behavior and a statistical element consisting of "your friends in DCS" to the overall sales?! ...like "a marketing and sales specialist and project manager"? May I ask what you do for a living? The important detail is, "sales" do not pay bills, revenue does. BTW the professional IT market is characterized by a service concept, where customers license a product to use it and pay a monthly, yearly or long term fee. The longer the contract, the lower the yearly fee. This allows for a long term cashflow. Basically you can add the number of licenses already contracted per year for the next 2-3 years, substract the estimated service costs and revenue, to calculate the available development budget.
-
Neither is true. The F-4E was in development by Belsimtek, then "on hold", then Heatblur took over and so on. EDIT The announcement by Belsimtek for the F-4E was in July 2014, so roughly 7 years ago. The release date was scrapped, after announcing and at the very day it should release after announcing it, again, delayed, again. Those delays triggered a short prolongation of the discount period, because customers asked HB for refunds.
-
Well, it does, depending on your mission preference. Fly now, together with others, in a nearly complete module. Or go through the Early Access years with the CH-47F, learning and utilizing features piecemeal as they get integrated. That's not a negative, did this with the Apache and it has its merits, as well. As an apology for the delays and release confusion... yep.
-
For me this is instant buy. I am actually thrilled they have it close to finished for release. I really like the sneaky Scout/Recon and asymmetric warfare/COIN mission types.
-
Sollte da nicht eine Mission Card auf dem Kneeboard sein? (RSHFT+K) EDIT Gerade nachgeschaut. Da ist in der Tat nichts im Kneeboard. Bleibt also nur F2-Ansicht, oder im "Schnelle Mission Generator" die "Fortgeschritten" Ansicht, "Generieren" und dann "Im Mission Editor und dort die F-4E im Loadout anpassen.
-
The obvious answer is: both. The OH-58D KW will be close to finished, likely feature complete. The CH-47F Chinook will be Early Access. While ED adds features and finishes the Chinook, you can learn the KW. If you need to decide for either one, only, focus on your preferred mission set. More the Recon/Scout type? Take the KW. More the CSAR/MEDEVAC, SpecOps Insertion/Extraction and support roles type? Wait for the Chinook.
-
No Early Access phase, so no discount...
-
Can you define "proper simulator"? I never thought of the "procedural training simulator of the A-10C HOTAS" build to specs for the ANG as a "Game"... really confused, now. Also, I am sure there are very different "real simulators" in use by the military, for different purposes in training, with very different focus and none of them comes close to "real life", but does its specific task, pretty well.
-
That's how it begins... and suddenly you find yourself redesigning you living space around a DIY "home cockpit".
-
You are aware that is NOT a belt, but a flexible feeder system?! ...and actually the munition transport inside(!) the feeder is animated (at least it was in one of the recent videos). But honestly that's the least of my personal priorities. Though I like the details, I am more interested in the Flight Model (that seems to be top notch according to Casmo, a real life KW pilot) and the cockpit I actually look at 99% of the time and then the avionics and internal systems. If my focus would be on creating cinematic DCS video, my priorities may be different, but for simulating flying and fighting in the KW, I definitely prefer top notch FM and systems.
-
I personally love the concept! The George AI modes are problematic in a stress situation, because you need to monitor which mode you are in and maybe switch the mode (from hover to combat) if you want to evade an ATGM. For commanding the copilot I need accelerate/decelarate, turn left/right and the hover command on a 5-way hat switch. Add a modifier for up/down and drift left/right and that should be enough to have basic control in a combat situation. Anything else may go to keyboard or voice attack... I would like the option to click the "HUD-Interface", though, as an additional option.
-
Not "also", but "only" because of the weight... there's no recoil from the missile.
-
Why? There is no recoil. It is a missile, not a bullet. Similar to "recoiless rifle", RPG launchers or your average ATGM, the missile accelerates propelled by the rocket motor, not compression of gas against a breach... it simply slides of the rail. That's not saying it looks a bit too stable, but that decision by the devs has already been explained, and I definitely favor their train of thoughts, as I find George way to complicated to operate from a CP/G position.
-
Yeah, but OrbX decided to do the Kola Map, not Balkans...
-
Jupp, es wird ja kontinuierlich weiterentwickelt, also ist eine Woche später schon wieder der Core etwas weiter. Dann kommen wohl alle Module drauf, es wird kompiliert bis eine Version die (hoffentlich automatisierten tests) besteht und dann geht's in die closed beta testing Runde wo hoffentlich noch kritische bugs auffallen... dann fixen, neues build kompilieren und weiter. Man könnte höchstens, eine funktionierende Version verzögern und erst einen Monat später releasen und sich so Spielraum verschaffen, für Marketing und einen verbindlichen Termin. Aber was diese Community tut, wenn sie weiß, das ihr geliebtes Modul "schon fertig ist" und sie es erst in 1-2 Monaten in die Finger bekommen... mag man sich gar nicht ausdenken. Aber das würde das Problem mit dem Termin tatsächlich lösen.
-
Wer sagt denn, das der breaking bug in der Phantom ist? ...und welche PC Systeme betroffen sind?