PhoenixBvo

OK, I have a TM Warthog, so slightly different, but: I use a TARGET profile with it. It includes keyboard based commands as well as DirectX buttons. I still use the same profile AND I just copied the controller's lua file (the one with the name followed by the long unique hardware ID) and it all works exactly as advertised. No instabilities encountered here.

yeah, NEVER touch the default.lua files. There should be another one in the directory called something like mouse.lua (or Maus.lua in my case :)). Edit that one and you should have more luck. Also your syntax looks funky, are you sure that is correct? Mine looks quite different...

It's not unsolvable, you'll have to edit the appropriate .lua file. Sorry, I'm at work, no way to check exactly where, but you can add DX buttons and other controls to functions which in the GUI do not have those devices available. It's a bit weird, but it works well enough when you get comfortable with the lua editing. I discovered this when I was creating a profile for the TM warthog with TARGET enabled. This combines the two controllers (stick + throttle) into one virtual device which is seen by DCS as a new controller. It has its DX buttons distributed differently and switching the TARGET profile on/off led to odd behavior in the DCS GUI where it would allow certain functions to be assigned a DX-button in one case but not the other. After comparing both control mapping config (lua) files, I saw that the corresponding functions had control devices missing in one of the two versions. By adding the needed control device (mouse in your case) + correct button you'll get the functionality you want. Hope this helps:smilewink:

Guys, just get a VPN connection like VyprVPN. That way your ISP can't look into your packages and therefore it will not throttle you anymore.

I wonder if you could set up a profile for the X45 to switch throttle axis left/right with the flip of a button. The thrustmaster TARGET software has that capability. It would be useful with the Cougar.

Yes, That would be the easy way of course :)

Or you could make a custom profile for the TM Warthog. The shutdown position is a button in the TM Target GUI which you can map to a keyboard key. Make this mapping depend on another switch position and you could get the behaviour you're looking for. Problem though is the Target software combines both controllers and reassigns the switches to other DirectX keys leaving a lot without DirectX key assignment at all, reason being that Windows doesn't support that number of switches on one controller. So, you'll have to assign a lot of keyboard commands to the Warthog and remap the functions in DCS as well. It's at least an evening work, but I did it and it pays off because you get the ability to put in some custom commands such as TrackIR and Teamspeak.

Great work bavella! I use your checklist all the time. I made a quick text only version based on yours for quick reference (in the mean time I know the switch positions, but still like to make sure I don't forget any steps). Have a look to see if you like it. Cheers!:thumbup: DCS_Rampstart.pdf

I disagree, in Acrobat just set view to entire pages and scroll through with the mouse wheel, works like a charm. Thanks TRoe!

I guess what you mean EtherealN, is that adding more particle effects would make the sim too heavy on the GPU? But having the same smoke particles disperse more over time should be possible without much graphics performance impact I'd think.

That's a really cool system... I wish I had the time to fly frequently online. I usually get a few hours in through the week, but I doubt I could fit a regular online rendevous with a squadron in my schedule.:cry:

Great tutorial! Thanks Paul. +1 BTW, will personalised skins be automatically visible online, is it a server setting or is it just for one self?

You mean here? Yes, you are right. Respect for remembering!:thumbup: I thought about it since then (especially the technical side) and the currently proposed form (only rotations corrected) is much easier to implement. No 3D rendering of the cursor since there are only angles involved.

This concept has matured over a long period of flying various sims including DCS. Although TrackIR makes a flight simulation very immersive, it's combination with the clickable cockpit is not that natural, yet... Let me explain: in these simulations the user has the task of operating some switch or knob in the 3D-cockpit. To accomplish this, the viewport in the cockpit frame of reference being controlled by the head position has to be coordinated with the mouse pointer location on the screen. Although training together with a good TrackIR profile and IR-noise free environment will allow quite efficient operation, it remains fairly unnatural. In practice, any viewport (head) movement will cause the mouse cursor to drift off the desired cockpit location and has to be actively compensated by the mouse. Consider the human body: the mouse cursor simulates the human hand. The hand is attached to the arm which, in most humans, is not directly attached to the head. The neck primarily provides us with three rotational degrees of freedom with respect to the torso. This means any head rotations do not influence the hand position. This as opposed to translations which are effected by moving the upper torso which also moves the arms/hands. Considering the above anatomical facts, it would be more natural if the simulation had a mode which would compensate any cursor movement (with respect to the cockpit) due to rotation of the viewport. Movement due to translations would be unaffected. This should make it much easier and more natural to operate cockpit switches, increasing immersion. To this idea, NaturalPoint replied: (original thread here) Basically putting it in your hands ED. You have the right position to implement this: It only takes some simple geometric equations including the rotations of the viewport and the mouse cursor position. Of course this feature would be optional and linked to an on/off toggle function to be assigned in the keyboard control menu. I appreciate the hard work going into DCS and it would be wonderful if this idea could contribute to the success of the product. Thanks, Mark

The extra digit gives a number representing the runway heading accurate to one degree, 06 and 35 are rounded down to tens of degrees...

Seriously, The damage model allows you to touch the ground and get away without anything other than some scratched paint;)

Who said I was going to extend the landing gear? :D

BTW: I will wager I can touch-and-go at any speed within the flight envelope without blowing a tyre. Anyone don't believe me?

The VVI has quite a delay and can only be used to verify steady descent rates. While flaring look at your total velocity vector symbol in the HUD and place that just a tad below the horizon line (anything below the horizon means descent).

I don't know that view mode (cockpit seems to be turned off). How do you get that? Is it only available in arcade mode?

I would be VERY surprised if that worked. I mean happy surprised of course but... We were told this problem is not easily solved and requires a major 3D engine overhaul, so I think it's just there for future compatibility. Sorry for being pessimistic. I can't test it right now, maybe someone can confirm/disclaim by flight test?

Yeah, but the formation lights don't have a flash mode. I think the dim part has to be disregarded/deleted...

You can create any mission scenario in the ME. E.g. set yourself up with some JDAMs and LGBs and put a group of targets in front of you for a basic TGP procedure practice. 5 min. work. But I guess you want those missions to appear in the training menu? I don't know about that, might be possible with some lua editig but I don't see the merit in that. Just put your own training missions in a seperate folder called mytraining or something like that and go to the mission item in the main menu and select your training mission. Works fine :)

Uhm, where exactly? No link...

Copy that. Not as simple as it looks at first. A pity that network protocols are developed independently where possibilities for benefits from cooperation seem to exist. SADL was developed based on the Army's Tactical Internet and EPLRS which was developed independently from Link 16. But CAS a/c bridge both worlds. It would have been very helpful if the JTRS package had included a gateway to Link 16. I want to know when the top cover, or better, AWACS spots bogies. Sure they can tell me, IF my radios are set to receive the proper freqs, but that's what the data link concept tries to solve, unify data exchange to provide a clear situational awareness picture to the pilot.