[Warthog shift axis possible?]

I'm not 100% sure for the color, I need to double check. It should be mentioned in the scripting manual.

[Warthog shift axis possible?]

True, however if using TARGET who's purpose is to primarily emulate keystrokes, I am not sure why one would use TARGET and then just map the buttons within the game. Although one could certainly have a combination of both, some mapped within the game and some programmed to emulate keystrokes in TARGET.

Most of the time you'd need to actually program something only for some buttons, so leaving the other buttons as regular stick buttons make thing easier.

 

At the very beginning (with LO/FC2/FC3) I was tinkering a lot and trying to put something on every single button with different states and all, so I had big profiles, but now with clickable cockpits you only need several functions on the stick as the rest is reachable with the mouse, so it's not really necessary.

 

It is very rare now that I rely on programming for some functions, I keep my profile very short and put everything in DCS as normal button presses.

I never use shift state, sometimes I use TEMPO or SEQ but it's rare, as I have enough buttons to do everything most of the time.

[only gun 1 functions?]

True, it is much more sensible to read the manual, but being helpful costs nothing, creates good impression of the forum, and will make Sithspawn happy.

 

Help could of course be in the form of a link to the right place to find the information. I remember just how overwhelming the complexity of DCS modules were on day 1.

Lol that really seems creepy when you put it that way :D

 

I also try to refer to the manual except when I'm writing from my phone where every character counts :music_whistling:

[Warthog shift axis possible?]

But doing what you said inside DCS would work with the shift state?? I mean, when binding an axis function if I press the shift key and then the axis I want to use it will be recogniced as "another" new axis?? sorry but I still not having this clear enough.

 

Also, I will like to ask one more off topic thing sorry:

 

1- Are the programable leds (the round ones near the friction knob) only green?? because for some reason I though/remember they where red/yellow/... maybe I just dreamed it?:D

 

Thanks mate, I will enjoy the warthog as much as possible!:thumbup:

Shift state mentioned here will also work for axis (in the axis assign page), the Throttle axis will always be the same, except DCS will use it for different simulator function depending on the state of the shift button.

 

But as I said before, the way you want to use your axis will require your axis to behave differently if in brake mode or zoom mode, somethign DCS can't do, that's why the shift state is not the solution in that particular case (I told you what you want to do calls for headaches :p).

Benefit with doing everything in DCS with shift states is that you can use your HOTAS without even firing up TARGET, so, no scripting required.

 

P.S.: Leds can be tuned in brightness. However I would recommend not trying to fiddle with them, even if the scripting manual tells you how to do it.

I don't know why it is like this, but playing with the leds (ON/OFF intensity) made the profile unstable for me. Some other users had the issue too, but few of them, so *maybe* it will work for you, but it is a possible cause of instability.

[Warthog shift axis possible?]

[...]

f you are going to use TARGET with a profile to assign key commands to buttons , then you should not have button assignments in the game. You assign them using TARGET. TARGET will then translate a button press to equal a specific key press - that you have assigned to it.[...]

That is not exactly correct, the Thrustmaster combined has buttons like the other sticks, you don't need to remap everything.

It just doesn't have enough possible DX buttons (32) to cover all possible buttons of stick + throttle.

All the joystick buttons are mapped

The only buttons that don't have a DX outputs are located on the throttle, those are the ones that will require you to write a remap.

 

For reference, here is the default mapping for the "combined", joystick mappings are the same as the naked stick, the throttle gets the remaining available DX buttons:

 

int JoystickMap[]={
TG1,DX1, 
S2,DX2, 
S3,DX3, 
S4,DX4, 
S1,DX5, 
TG2,DX6, 
H2U,DX7, 
H2R,DX8, 
H2D,DX9, 
H2L,DX10, 
H3U,DX11, 
H3R,DX12, 
H3D,DX13, 
H3L,DX14,
H4U,DX15, 
H4R,DX16, 
H4D,DX17, 
H4L,DX18, 
H4P,DX19, 
H1U,DXHATUP, 
H1R,DXHATRIGHT, 
H1D,DXHATDOWN, 
H1L,DXHATLEFT};

int ThrottleMap[]={
LTB,DX20, 
SC,DX21, 
CSU,DX22, 
CSR,DX23, 
CSD,DX24, 
CSL,DX25, 
MSP,DX26, 
MSU,DX27, 
MSR,DX28, 
MSD,DX29, 
MSL,DX30, 
SPDF,DX31, 
SPDB,DX32};

[Is my system to weak for DCS ?]

The biggest thing for me that affects FPS is whether I am using 1 monitor or 3.

My 7 year old computer, intel core 2 quad, 8gig ram, Nvidia 750ti, gets 65-75FPS average with settings at medium using 1 monitor. But I now use 3 monitors bringing down my FPS to 35-50average with most settings to low/off.

Yes I'm getting a new system...

 

3 cameras or 1 cameras across 3 monitors? this is very different

[Warthog shift axis possible?]

Don't know where 2 post...

Could you advise, if I create *.tmc file should I launch it only via TMScript editor? Or is there any way to covert it in *.fcf?

Thnks

I don't think that is possible

[Warthog shift axis possible?]

A simple and easy way:

 

Set a joy button or key as "modifieir" in Controls.

 

Set the TDC axis for designed function, eg. wheel brakes + this modifier.

 

In game press the button/key, move the axis = wheel brakes. Without button/key whatever you want.

 

This was already suggested few posts above

[only gun 1 functions?]

The MiG has only one gun with 4-seconds worth of ammunition supply, thus it needs one button for charging. The remaining two buttons work on the same gun and are there only to recharge in case of misfire.

 

The reason is because it is gas-operated, the charge is the equivalent of arming a handgun by cycling the slide and cocking the hammer (with an explosive charge hehe).

So in case of misfire or jam you need to arm it again.

Note that firing under high G can also cause the gun to jam.

[How to determine your true speed?]

This. Somewhat counter-intuitively the speed of sound in a gas is almost entirely dependent on the temperature of the gas and not the pressure, though for "non-ideal" gases the pressure does have a small but measurable effect.

 

Good Wikipedia article on the subject:

 

 

https://en.wikipedia.org/wiki/Speed_of_sound#Equations

 

Cool détails

Oh damn there is a typo in my text I meant with no wind, true airspeed = groundspeed :D

 

p. s. yeah one would think it depends on density because mach increases with altitude but it's actually because of temperature.

[How to determine your true speed?]

CAS is IAS corrected for a position/installation error.

[.. ]

thanks :thumbup:

[How to determine your true speed?]

Mach speed only depends on air temperature (and a bit on humidity), it is used obviously to check how close you are from the speed of sound (avoid that loud bang and transsonic effects). But also useful as a reference for speed.

In civil aviation, below a certain altitude, the reference is calibrated airspeed, above it is mach (for cruise speed for example).

 

Yeah true air speed is within the air mass. With no wind, true airspeed = groundspeed.

Calibrated airspeed is indicated airspeed (= "pressure airspeed" if you will) plus an adjustment, I don't remember what.

[How to determine your true speed?]

So I know the indicated airspeed gauge is useless for determining your ground speed when you're at altitude. So I'm wondering what gauge I can use to know how fast I'm passing over the ground?

 

It's not useless, it will help you :)

Aircraft with INS or GPS can display ground speed (in HUD or on CDU or INS control panel display).

If no such equipment is available, you can compute using your gauges.

For this you need the pressure altitude, the temperature and the calibrated airspeed.

Then you can compute true airspeed using an E6B computer for example.

 

P. S. yet this is not how fast you're moving over the ground... For this you need to adjust the true airspeed with wind.

[Warthog shift axis possible?]

Ok, I see it can be a real headache so I will probably let it go :P ...anyway, I think I will go for the warthog and as soon as I get it I will try what you told me and see what happens.

 

If I broke something :P I guess you PiedDroit can help me, you seem really savy about joy programming :thumbup:

 

thanks for your help!:)

Sure I can help.

At some point I did some really convoluted stuff just for the sake of making it work, but in the end I always come back to the basics, as nothing beats simplicity, so I might try to avoid answering the most twisted request :D

[Is my system to weak for DCS ?]

I'll try some of your settings ;)

p.s.:

I'd suggest disabling the Lens Effects. Those are mostly useful for cinematic purpose but they don't appear IRL (without a camera) and they eat some FPS.

Also disabling VSYNC will help a lot.

 

For reference, with almost the same setup except CPU, I'm using this:

[Is my system to weak for DCS ?]

Do we have a benchmark track? I can run it, post results and setting.

[Is my system to weak for DCS ?]

Hi gents,

 

I have the following system:

 

Win7 64Bit

I7 3770K 3,5GHz

16GB Ram

MSI GTX 680 4GB

 

Ingamesetting all to max, V-sync on

 

The problem i have is that i only get 30 fps and on the ground 25fps. When i disable shadows i get about 45fps - 50fps, with all other settings still on max.

 

Also i overclocked my GTX to his max. level and my cpu to 4,7GHz, no change on fps with shadows on. NVIDIA settings are the same as in Cliffs of Dover. I run the latest patch version on DCS.

 

Can someone help me pleas to find the right settings or is my system realy to weak for DCS.

 

regards

 

Little_D

I have the same specs except my CPU is i7-3820, 3.6ghz, no OC

With medium to good settings I got 40-70 fps at 2560x1080 (depending on the map and module).

I'll post more details later

[Deleted Post Feedback]

Does this apply only to posts deleted by mods or the ones deleted by users as well?

 

It seems to apply to posts deleted by users as well.

My post above has been deleted by myself

[Waypoint Radar Ranging Position Update]

Thanks to Maulkin for asking, and to PiedDroit for clarifying!

 

I also was not sure about this problem.

You're welcome :thumbup:

It got very frustrating when not figuring out what the problem was indeed :megalol:

[No love for p- 39 Aerocobra?]

Don't mix genuine interest in military aeronautics and technology with ideology or politics. I bet 99.99% of people flying DCS are of the former category, not blood thirsty civilian-killing naziterrocommunists.

 

I would even fly an Ohka just for fun :D

 

On the design of A-10, it was closer to an IL-2 IMO. But yet it had those massive airbrakes, ready for some dive attack fiesta.

[Help - Canopy ejects upon starting]

Before reinstalling, rename your DCS folder in <user>\Saved Games\

DCS will regenerate a fresh one (that you can get rid of afterwards).

 

Then you can decide if your install is corrupted or not:

 

• If nothing happens this time, it will be most likely in the inputs - next, restore your renamed DCS folder, and rename the inputs folder for the SU-25T.
  
• If you still have the issue, your install has indeed a problem.
  

[Oculus Rift immersion is incredible.]

How do you guys deal with not being able to see your keyboard for things such as selecting radio messages?

I think there are voice commands that you can use.

Otherwise (as I did), I go "the tactile way", which is recognizing the keyboard by it's shape. It's fine for function keys, arrows and keypad.

[Warthog shift axis possible?]

the reason Im interested in this is to be able to zoom or brake slowly (so as an axis and not just with a button where press is 1 and release is 0 so all braking strength or nothing) but of course this is not the only thing to make my decision :thumbup:

 

thanks for your help budy!!:)

Zoom on an axis:

In DCS there are two zoom functions, "zoom in" and "zoom in slow" so you can have two zoom speeds.

The speed of each can be configured in a lua file. Using both on one button can be handled by most programming softwares (with shift state).

[EDIT] The above is not right, only works in externals. When in cockpit you can only zoom progressively or go to min/max zoom. Yet the speed of the zoom is still configurable in the lua.

 

Brake on an axis:

You can still have efficient braking with a single button. Before having pedals I was using a button and braking can be adjusted by tapping or pressing the button.

 

Also don't overestimate the accuracy of the ministick, it's not very precise ;)

 

What I want to highlight is that doing what you want to do calls for a lot of frustrations. There are much easier and convenient ways of doing what you want.

 

You can do that without any programing in DCS. You can add the axis with shift as modifier to the brake or zoom

No, not with the ministick (read the thread first...).

To handle brakes and zoom at the same time, it would need to be configured as MAP_ABSOLUTE for brakes and MAP_RELATIVE fo zoom, and DCS can't do that.

[Heading compass and INS Alignment]

Well, this is one of the reasons I love DCS. You learn new thing everyday. Thank you PiedDroit.

But in scramble situation like in BF even 4 minutes feels long lol.

 

Cheers

Welcome :thumbup:

The fastest way to start the alignment is to ask for ground power, once you have it and master power switch is ON, you can put the INS in ALN mode, validate and carry on your startup (otherwise you'd need the engine running).

 

Normally you would enter the initial lat/lon position in PREP 00 before starting the alignment, but if you only care about basic alignment, you can skip that part too ;)

[Warthog shift axis possible?]

Many thanks for your help!! Looks quite hard to hanfle for someone with zero experience in programing though :P ... anyway, what I wanted to do is just using the X and Y axes in the slew nipple for slew and when the shift button is pressed the slew would work one axis (X for exmple) for braking and Y for zooming track IR...also, I wonder if those "extra" axes would be recognized directly into the dcs menu or not.

 

Thanks again

They should be recognized (DCS doesn't know about TARGET, it only sees the DirectX axis). And you can still manually select the axis anyway, so, no issues there

 

But... if you want to select your stick based on this capability, I find this a bit... Overkill. Why not simply mapping the zoom function on a couple of joystick keys? It would be just as effective, with less headaches.

From my personal experience, there is no need for layers (shift keys), except with FC3 aircraft (no click pit) and even with those you can use the short/long press to have two function on one button without relying on shift keys. I managed to avoid shift keys on every profile I did so far.

If you want to go that way, the TARGET software is really powerful, but not for the faint of heart, prepare yourself ;)

 

Also, there will be also additional tweaking to do if you want to zoom with the ministick.

You'll probably need to configure it as "relative" (instead of "absolute", in the MapAxis call) to have the zoom increase of decrease only when you move the ministick away from center.