Dimebag

Thanks sobek, that's all I needed to hear.

So what you are saying is, abandon all hope? This really is a game breaker.

I think many people would pay dearly for a decent new theatre of war with edge enabled, myself included.

I wonder if there is some .dll somewhere we can swap out which is responsible for ffb. Right now I have to fly with ffb off and spring centreing enabled in the profiler. Can't imagine trying to fly the ka-50 like that. This problem needs attention, as for all g940 owners dcs is now broken. Forget formation flying in DCS with a g940, not possible.

Interesting, I wonder has anyone managed to use this code successfully to get a working gear up down command? It seems to me based on that code that we can set a particular argument value directly, but if I set arg 430 to 1, will the system detect that arg 430 is gear and adjust the drag parameters accordingly? I guess what I am asking is, are the gear and flap still tied to the sfm, or do we now have to code more than a command to get the gear or flaps to act appropriately?

Would really love to see a serious dcs level 3rd party development of the phantom.

Agreed, as it stands all aircraft are unflyable from a realistic standpoint if you wish to use trim. The only way around it is to disable ffb in game, set trim forces to 0 then set spring centreing effect in the g940 specific game settings panel to your chosen amount.

Because you flew it? Speculation is just that, speculation. Until I see with my own eyes the announcement of the next ed dcs module I will keep an open mind.

Same problem here too, the devices themselves are working, as I still get the print to user messages, but the dispatch action commands for gear flaps and airbrake must not be linking with the game. When I use the g key to retract the gear the game doesn't respond either. Hope they fix this soon or we find out how to fix it ourselves.

Same here. What I find interesting is when I use the key command inputs for trim, like r control + , for left trim, it still does it, almost like the key commands themselves are mapped wrong, but in the controls section they are set up the right way.

I have also experienced the buttons on both my stick and throttle not responding for several moments only to start working again in fc3 beta. I use the Logitech g940. Hope this gets resolved soon.

Great to see another macchi in dcs world! Can't wait to see the pit.

Damn, got all excited and was praying to see, fixed axis reversal bug, on the list, but alas it was not to be, how disappointing...

Hi jib, I have a feeling you are not clicking on the right thing in the assign controller window before you hit the assign controller button. If you want an argbased rotation, you should highlight 'Rotation : Euler XYZ' in the window on the far right, then click the assign controller button above - this should then bring up 'argbased rotation' in the list. From there you create your keys and adjust the x y or z rotation properties. That is how I do it, hope it helps.

People just need to grow up and get on with their lives, hopefully someday when you least expect it you will get a nice surprise.

Looks real nice, any chance we can get similar shots but without the wireframe? The wires hide a bit of detail. :)

If you mean does argument 8 move the gear lever, yes it does. But if you mean can I click it and have it move, then no. When I put the mouse curser over the gear lever a text comes up with the name of the helper object.

Well I have been attempting to get my gear lever to be clickable with not much success. I can get modelviewer to recognise the dummy helper associated with the lever, however I think my problem is I don't really know how to code for a simple two state gear lever. The other problem is that the gear lever is already animated before it is even clickable, which has thrown me off. Here is what I have code wise for clickabledata.lua: Argument 8 is the argument which actually controls the gear in game, and also moves the gear lever in the cockpit. I wasn't sure how to code this as there is only really one gear command, rather than two for up and down. Here is the code for devices.lua Here is the code for avionics.lua: I have no doubt my code is wrong, and I am going about it the wrong way, please excuse my complete ignorance in these matters. :doh:Any advice or help you can give is much appreciated. Also thanks to Sevas for the info.

Wow, I really wasn't expecting such in depth help, but thanks none the less Ells, I will have a test of this code tomorrow. This is VERY much appreciated! :)

Hi all, I have followed this thread closely and am currently implementing my own custom aircraft into DCS. I have had some success as far as instruments, however I have been scratching my head when it comes to the clickable side. It's not entirely clear to me how one implements a simple clickable device, such as a switch. I would be greatfull if someone could shed some light on how to code, for example, a gear lever, how you define the lever object as clickable, and implement it into DCS. I am aware you use the clickabledata.lua file, however I'm not sure just how one achieves what I have described. Thanks, Dime.

Thanks for the info, can't wait to see something substantial so we can really start getting behind these projects.

That would make a lot of sense, seeing as how good that f-15 cockpit looks.

Indeed, a DCS 3rd party dev wiki would be extremely helpful for all, however I can't see it happening due to the time and effort that those guys put in, they likely want to keep their secrets close to their chest and let others find out the same way they did. Sad really because this truly is a massive community project and those secrets would be best shared among us all.

Yes, I suggest everyone take a 'chill pill' as you suggest, tensions are running high as you can see. The reason for my statement was that this thread has turned into an f-15 vs flanker s*#t fight match; the are plenty of those elsewhere in the forum, so I am suggesting those people should continue their slinging matches there.

Can people please stay on topic, this discussion has wandered too far from fc3, and it's going nowhere.