Lucifah

It would be naive not to at least get a nod from Dassault. A small development team does not want to take on an aircraft manufacturer on the legal battlefield :noexpression: Unlike others in this thread, I do not believe that the simple renaming of the aircraft (Mirage vs M) is going to make them exempt from legal risks. The name is just the most obvious thing, but any manufacturer of anything considerably complex would have patents for every other bolt and knob that's worth protecting. The closer you venture into accurate replica (or sim) territory, the more likely you are at risk of infringing intellectual property. And the more accurate your replica (or sim), the lesser the chance to argue that you're not depicting the real thing -- the changed name won't shield you then. Also, Ecuador has been operating Dassault planes, so they will have a legal presence there, too, which makes the fact that Razbam is from there and Dassault is French pretty moot. It boils down to indie developer team vs. resources of a global aircraft manufacturer... So yeah, let's hope they have their backside covered :)

Is there a reason why you want to install a much older version of the Mustang? 1.5.x is a different engine, so your 1.2.x installer is not going to work. Unless you find a 1.2.11 version of DCS World somewhere (yours was 1.2.10, but Mustang was 1.2.11), you'll probably not succeed with that. EDIT: Unless there's a compelling reason to mess with particular and old versions, I'd just install 1.5.3, as you have, and then use the module manager to install whatever you have a license for.

You guys are nuts! Seriously though, if you can pull that off, I'll buy it! (And if you need alpha testers, count me in. :) ) Good luck!

I just built a new PC two months ago, and I never buy any hardware right when it hits the market. Too pricy, too many driver glitches to fix, just too many downsides altogether. Ask again in a year when the 1080 TI has been on the market for a couple of months. ;-)

If you do plan on making civilian aircraft, please focus on "hybrids" (models with military and civilian use) and make sure the military version gets most love. Honestly though, what are you going to do with civilian aircraft apart from aerobatics? The maps are small, with only a handful of airfields and just a bunch of navaids. This is going to get old very quick. If you are going down that route, maybe don't do a civilian aircraft, but instead lay the ground work for it first: bigger maps, better terrain meshes, airfields, VORs and NDBs, and the ATCs would need some love too. :music_whistling:

Ok, this is going to become a religous discussion as some people easily take offence when you criticise "their" favourite sim... ;) I'll make a start and say P3D. You can get a developer license (monthly subscription, which will be cheaper than re-purchasing the whole thing every year). The terms explicitly state that the license targets *all* developers, even those who just start out. That could match literally anybody! So that's $10 per month rather than $200 every year or so. Technically the product is the same as the developer subscription grants you a professional licence for rent, so to speak. Anyhow, just wanted to get that out of the way, because the terms have been reworded not too long ago, but most people still have the old convoluted terms, which left a lot of questions, in the back of their heads. Now for quality, I use P3D over XPlane mostly because: - A2A, RealAir and Aerosoft have fantastic airplanes for P3D (I only do general aviation; not interested in airliners myself). By fantastic I mean Carenado-level looks, but with proper systems and (as far as I can tell) flight modelling on top of it - Flight1's GTN750 avionics are a must have for me personally - several good weather and traffic plugins to choose from - a little bit better than X-Plane's basically non-existent ATC - very decent scenery available (OrbX for example), without spending hours to download/generate tiles at several GB for a few square miles each (ortho2XP, as used by the unfortunately no longer available SimHaven sceneries). It's great for those who have time to tweak X-Plane, but I prefer to pay instead, since I'd rather spend my time flying rather than tweaking. Graphics can be pretty fantastic on both though, with varying effort. And the latest P3D (v3) looks awesome and performs much better than any predecessor. The only reasons I sometimes use X-Plane are that it feels a little bit more lively in terms of flight dynamics for the majority of aircraft, with exception of aircraft that have been designed with custom flight models (like the designers mentioned above), and it has better flight model support for choppers. That said, whether any of the planes and choppers I fly in P3D or X-Plane are actually realistic is hard to tell. In theory X-Plane provides better flight modelling tools and physics, but whether or not the designer actually tweak their airplanes to make the most of it, hardly anybody would know (except real pilots who have flown specific models for real). Anyway, that's just my opinion, not an accurate or complete comparison. :)

I'd like to add myself to the list of people asking for a Huey-like (and Mi-8 and Ka-50 in FD mode) trim method, which is by far the best method for non-FFB sticks. Also, it would make trim handling consistent with other choppers, which can only be good for DCS as a whole.

:megalol: That sounds sooo familiar!

Manuals: Please provide proper checklists for procedures. Tutorial missions are great, but they should only complement -not replace- essential sections of the manual.

You're right! I thought he was a young lad in his late 20s, but heading towards 40 already that old fart! ;)

I'd have a look at the axis tuning settings. For me personally (everybody's mileage varies!) slight curves for roll and pitch work better for the Huey. And also you will have to trim like a champion, even more so with curves assigned. Now for the Gazelle... don't start with that. I think it's way too sensitive at the moment (much like the Huey was during beta). Seems to be all over the place, but have only spent half an hour in it, so I might just be doing something wrong :music_whistling: In any case, landing and hovering is one of the most difficult excercises in a chopper. We have all suffered from a lot of crashes at first... I think. (or maybe just me) Save time with the startup procedure if you crash often. Usually there's a key combination (LWin+Home?) under "Cheats" that gets the engine up in no time. Or just use mission editor and place a chopper on an empty airfield and choose "start from parking hot" from the waypoint section. You can do proper procedures once you are certain that you don't break the chopper straight after hover check clearance :D

Bought the bundle, now waiting for the Nevaaaaaaaada download to finish... :cry: Quick now before the wife and baby are back home! :music_whistling: Usually I'm calm and collected, but new choppers always get me excited like a little boy. :joystick: Thanks to ED and Polychop. Splendid timing before the long weekend! :thumbup:

:thumbup:

Soon? Another two weeks? :megalol:

Now I'm glad that I held off on purchasing Nevada... Will get the bundle deal! :joystick:

That doesn't mean much. :) Hawkins hasn't won against O'Sullivan in what... 14 years (or in all 11 tournament matches they've played during that time)? Yet Ronnie lost this time (more than just the game). This tournament is full of surprises already... Bingham, Robertson, Murphy out in first round; Trump and O'Sullivan in second. My money for the trophy is on Selby. But McManus deserves it too -- he's the oldest guy but has never won it, or even reached the final. Ding and Fu have plenty of time left in their careers to win the trophy (and probably will eventually); McManus probably not.

Don't write McManus off just yet... 9:7 after this session. I've only watched with half an eye while working, but it was outstanding. Huge breaks on both sides in this session... 4 centuries in 8 frames... 138 for Ding in first frame; 136, 125 and 107 for McManus. My guess is that he might take the lead tonight.

Good summary and conclusion, Yurgon! :thumbup:

That together with throttle&stick mandates that you buy the Huey right now! :) You'll be trimming your arse off, and you'll almost feel aerodynamic forces. On the other hand, the Mi-8 isn't much different, and has a bit more complex systems (and a very very basic auto-pilot, which can be useful at times). Complex is maybe not the right word... lots of knobs, switches and rotaries, but still very basic tech. ;-)

That was in reply to what I said before? Of course the radio works with battery on, but not with the sequence suggested in the video, where he first starts the engine and then the battery, if I'm not mistaken. It struck me as odd. He wouldn't be able to call ATC for start-up clearance that way (not that he bothered anyway), and for any other aircraft he wouldn't be able to start the engine either, unless I'm missing something. :) He didn't have ground power, either. In other words, that's not the correct startup procedure, so likely not what the OP was looking for. In fact the very first thing in the in Engine Start procedure according to manual is BATT Switch On.

As Teej is getting a bit busy in the real world at the moment, I'll try to answer that... The standard codes, which appear to work across the board (unless modules replace them with their own functionality), can be found as comments in your DCS World installation folder -> Scripts\Export.lua And custom functions' codes would be in Mods\aircraft\[aircraft_name]\Cockpit\Scripts\command_defs.lua You'll have to look at what value is assigned to start_command there, and then count up by one for each appearance of counter(), simply put.

Oh alright then. :)

Also, with this startup sequence you wouldn't really be able to contact ATC to request start-up before actually starting up, would you? Would you get the aircraft into the air from cold with this video? Yes. Is it the right procedure? Maybe not, unless I'm missing something and the M2000C has radio power before switching on engine and battery. :noexpression:

Something strange happening in this thread. A thread reply (got the email notification) doesn't show here, and I apparently cannot send you a private message either. It's not showing there after sending. :huh: The powers that be [tm] apparently don't want this discussed. Very odd. If a moderator is involved here, please could you clarify if anything we discussed here was not okay to be discussed? :helpsmilie:

Alright, here it goes... default.lua: -- Systems -- air brake {combos = {{key = 'B', reformers = {'LAlt','LShift'}}}, down = iCommandPlaneAirBrake, value_down = 1, name = _('Speed Brake Switch - Up'), category = {_('Flight Control'), _('Throttle Grip')}}, {combos = {{key = 'B', reformers = {'LAlt','LCtrl'}}}, down = iCommandPlaneAirBrake, value_down = -1, name = _('Speed Brake Switch - Down'), category = {_('Flight Control'), _('Throttle Grip')}}, {combos = {{key = 'B', reformers = {'LShift'}}}, down = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, cockpit_device_id = devices.HYDRO_INTERFACE, value_down = -1, name = _('Speed Brake Switch - OUT'), category = {_('Flight Control'), _('Throttle Grip')}}, {combos = {{key = 'B'}}, down = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, cockpit_device_id = devices.HYDRO_INTERFACE, value_down = 0, name = _('Speed Brake Switch - HOLD'), category = {_('Flight Control'), _('Throttle Grip')}}, {combos = {{key = 'B', reformers = {'LCtrl'}}}, down = hydro_commands.F86_CockpitDeviceCommand_AirBrakesHandle, cockpit_device_id = devices.HYDRO_INTERFACE, value_down = 1, name = _('Speed Brake Switch - IN'), category = {_('Flight Control'), _('Throttle Grip')}}, I need OUT and IN. Hold is the middle position on the rocker switch, which does nothing useful. Up/Down don't do anything at all. And the devices.lua: local count = 0 local function counter() count = count + 1 return count end -------DEVICE ID------- devices = {} -- moved forward for correct initialization of another devices -- do not changed folowing sequence for sim devices["ELEC_INTERFACE"] = counter() -- 1 devices["HYDRO_INTERFACE"] = counter() devices["FUEL_INTERFACE"] = counter() devices["ENGINE_INTERFACE"] = counter() devices["WEAPON_SYSTEM"] = counter() -- 5 devices["AIR_SPEED_INDICATOR"] = counter() devices["BARO_ALTIMETER"] = counter() devices["VARIOMETER"] = counter() devices["MACH_INDICATOR"] = counter() devices["CLOCK"] = counter() -- 10 devices["TURN_SLIP_INDICATOR"] = counter() devices["ACCELEROMETER"] = counter() devices["CONTROL_INTERFACE"] = counter() devices["OXYGEN_INTERFACE"] = counter() devices["FIRE_DETECTION_INTERFACE"] = counter() -- 15 devices["AIR_INTERFACE"] = counter() devices["LIGHT_INTERFACE"] = counter() devices["NAV_LIGHTS_INTERFACE"] = counter() devices["STANDBY_COMPASS"] = counter() devices["GYROMAG_COMPASS"] = counter() -- 20 devices["AN_APG_30"] = counter() devices["A4_GUNSIGHT"] = counter() devices["FM_PROXY"] = counter() devices["ATTITUDE_INDICATOR"] = counter() devices["COCKPIT_MECHANICS"] = counter() -- 25 devices["AN_ARC_27_COMMAND_SET"] = counter() devices["AN_ARN_6_RADIO_COMPASS"] = counter() devices["MACROS"] = counter() devices["AN_APX6_IFF"] = counter() devices["INTERCOM"] = counter() -- 30 devices["ARCADE"] = counter() devices["KNEEBOARD"] = counter() devices["HEARING_SENS"] = counter() devices["AIRBRAKE_TOGGLE"] = counter() Ignore the last one (AIRBRAKE_TOGGLE). That's from my attempts to make it work. To me it looks like the actual functionality is buried in DLL files, but I don't have time and inclination to debug/disassemble them. I doubt they'd be compiled with debug symbols anyway, so that would get rather very tedious to do and is probably not worth it. But if you can make anything of those bits up there, please do share :smilewink: Cheers!