JayPee

I did as you wrote and I get FreeTrack to function IG but like you said as well, it doesn't show up in the controls section. No luck with FTN tho.

Some of the controls of the V-22 remain a mystery to me. Hopefully someone here can shed some light on it, or better, provide some reference material since Google is failing me big time. At 90 deg. nacelle, the Thrust Control Lever controls collective pitch to control altitude through downward thrust, just like an ordinary helicopter, where engine RPM remains the same (+/- governor corrections). What happens at 0 deg. nacelle, or airplane mode? Does the TCL still alter blade pitch to control for thrust, or does it keep blade pitch constant and adjust engine RPM the way a turbo prop functions?* * I know a turbo prop also has variable blade pitch but the primary channel to adjust thrust is the engime RPM. Regarding yaw, at 90 deg. nacelle the pedals cause differential nacelle angle, IIRC from 83 deg. to 97 deg. At 0 deg. nacelle the pedals control the tail rudder control surfaces to yaw like a plane. Articles on the FCS of the Osprey state that controls gradually phase out based on nacelle angle. What does that mean? That e.g. with nacelles at 60 deg., a full left pedal gives a 33% rudder control surface swing and 66% differential nacelle angle? (My logic: 60 deg. nacelle angle is 2/3rd helicopter mode, 1/3rd plane mode) Also, what is the procedure to gain forward (or backward) airspeed while in helicopter mode? Slightly tilting the nacelles forward (or backward) using the wheel on the TCL, again max. 83 deg. to 97 deg. IIRC? Or does the pilot give forward (or backward) stick input to have the whole airframe pitch nose down (or nose up)? Thanks -Jp

Aight. I'll be checking it later on this day!

When you're 3 years old, you're happy you can drink your glass of soda without spoiling. When you're 28 years old, you're happy you survive 14 beers and 4 whisky cokes. Right now, I'm 3 years old. :smilewink:

Thanks for all the answer guys. You've been of good help!

SPI If I turn the laser on prior to setting an SPI, will the laser override the use of elevation data, and create the SPI at the point where my LOS collides with an object, instead of on the ground? TGP I seem to struggle a bit with picking orbit positions. Most of the time the TGP is looking at my fuselage, wing, or ordnance with only small time windows in which I can see my target area. What are the best altitudes, slant ranges, and banking angles pilots use? If you're carrying your TGP on the right side, is it generally better to bank right or left? I'd say right but I'm not sure. I've seen pictures of Hogs carrying the TGP on stations 3 and 9, is the station related to this subject? If so, why does DCS limit the TGP to 2 and 10? Last but not least, the manual shows a picture of an RL green monochrome TGP display, not a grey one? bombing This might be over simplistic thinking, but when modernised precision ordnance is available, why still use dumb bombs? In fact, why still use self lased LGBs when we've got JDAMS? I'd argue dumb bombs are cheaper and therefore preferred when accuracy is not a big issue but then I doubt if money is a factor when it comes to effectiveness. CMS This is the last section, I promise..! I know the SEMI and AUTO setting use these four programmes: A: low intensity of chaff for gen. 1 RADAR SAMs B: high intensity of chaff for gen. 2 RADAR SAMs C: high intensity of flares for IR SAMs D: normal instensity of chaff and flares for "unknown/misc." If I change the first four programmes, will the SEMI/AUTO setting look for a suitable programme past D? What is considered "unknown/misc."? I was thinking of customizing these programmes, but only if SEMI/AUTO looks past programme D: A: 1, 0, 0.5, 10 for gen. 1 RADAR B: 2, 0, 0.25, 10 for gen. 2 RADAR C: 0, 1, 0.25, 10 for IR D: 2, 1, 0.25, 10 for unknown, assuming the worst: gen 2. RADAR and IR both in the area. E: 0, 1, 1, 10, preemptive for IR during ingress/egress/strafing; plume or incoming tone --> immediately to A, B, C, or D, depending on what I know. Any contribution to my learning is greatly appreciated!

I'm about to make a new 3 point LED cap to use the pointtracker in FTN 1.7. However, with FTN set to TrackIR interface, it does not show up in a vanilla 1.2.5 which, according to claims made by some of its users, it should do without having to mod DCSW for use with non-NaturalPoint files. Also, FTN does not start the dummy trackir.exe, I seem to have to do this manually in order for it to show up in task manager. Help is welcome! Already posted it over at FTN's sourceforge but that's a rather inactive forum it seems.

Which is more or less what was concluded in that other topic. ;)

Milli, I know that an autoexec.cfg does that but I was hoping JSGME could do that for me. For the autoexec.cfg you need to know the exact spelling of a command and its table to generate the proper syntax. Fictional example: from what I've read, for something like BUILDING_DISTANCE in graphics.lua it is possible to be called HOUSES.RANGE when you enter it in the autoexec.cfg. On top of that, you need to know the Lua table name in which the commands are located because you have to add them as a prefix. Long story short: I have yet to find a way to translate lines from the .lua files to the proper syntax required in the autoexec.cfg.

For those interested, conclusion drawn in a similar topic: The trim reset cheat is likely to be a general game function of World to aid control with limited hardware. The actual Trim T/O button happens to have the same effect and is part of the real A10. So should you need to reset trim, you should use the Trim T/O as that is the only option an actual pilot has. Take note that both do the same: gradually resetting the control surfaces to centre position when holding the function down.

Perhaps other users of msalama's files can shed some light here? Would be awesome. I'm in the process of tweaking but I'd like to know technical details on which file/line does what prior to blindly adding the whole fun package. I'm especially interested in msalama's tweaks to improve FPS without noticeably nerfing eye candy as I find low level flying already a bit MS Flight Simulatorish. Currently: 55 fps external, lights on 30 fps in-pit, lights on 20/25 fps in-pit, TGP on and/or flares deployed (this one needs attention) ... and flashing rooftops and flashing vehicle textures thru TGP On: i7 3610QM GT640M, 2GB, DDR3 840 basic series With: all HIGH water LOW civ OFF blur ON hdr NORMAL fsaa 4x tssaa OFF trees 1500 bushes 0 birds 100% Graphics.lua: draw distances reduced lodMult 1.5 lodAdd 100 No other tweaks yet.

Cookies for the guide! I already knew JSGME but this is a nice tutorial to save endless topics of why mods don't apply, which is usually due to messed up file paths. Anyway, assume the following, you attempt to edit your graphics.lua so you make a snapshot of the file as per 1.2.5 vanilla and you start messing in your own modded copy for which you use JSGME to apply. However, when an update changes the layout/structure of the graphics.lua file, yours -based on an older version- is rendered obsolete. What can be done about this using JGSME? Does it offer a find&replace text strings feature to not overwrite entire files but only certain lines within a single file?

Roger!

I totally get it! Where'd you get those drawings from?

I got Prifinity to work but it seems messing with affinities/priorities only reduces my FPS so I'm back to 4 cores * hyperthreading = 8 virtual cores.

OK. This is what I thought but I didn't want to bias the discussion. So under normal circumstances, trimming an A-10 does not move the tabs, instead it moves the whole surface. However, when in MAN REV, trimming moves the tabs which in turn move the whole surface due to aerodynamic forces. As a reply to Bonsai, when idling on the rwy my entire ailerons clearly move while the trim tabs don't when trimming for roll. I will check whether it is different in MAN REV.

I always presumed that changing the pitch of the trim tab causes aerodynamic forces to push the main surface out of its neutral position and thereby reducing required pressure on the controls. The paragraph on manual reversion confirms this mechanism as it states that trim tabs are used to push the main surfaces in the required direction by making use of aerodynamic forces when in MAN REV mode. However, if aerodynamic forces are the factor driving the main surfaces when adjustment of trim tabs is applied, how is it possible for trim to move the main surfaces when I'm idling on the ground and no aerodynamic forces are present? And why don't the trim tabs move in relation to the control surfaces? Trimming now looks more like a type of auto pilot continuously giving input to the main surface and not to the trim tab.

Now I'm at peace.:book:

Trim T/O does indeed not do anything fancy. When held, the plane slowly goes back to doing it's own thing, no radical changes. Still, what is the difference between Trim T/O and trim reset? And why do we need the trim reset function if Trim T/O does the same thing?

Thanks MadCat, that would justify an actual trim reset function being absent in the real a/c. However, this still leaves me wonder what the difference between trim reset is, and why it is implemented anyway when Trim T/O does the same?

Sorry for the bump. So what is the practical difference between the fictional game's function of resetting trim and the actual A-10 Trim T/O button? They both set al surfaces to their initial position, what else?

I noticed what you found as well, that when holding down the trim reset button the surfaces gradually move back into position. However, I also noticed that after having quite some trim applied, holding down the Trim T/O button also takes a while before the confirmation light is lit. This would indicate that both functions slowly return the surfaces to their default position instead of one instantly and that there is no real difference between them? Anyway, thinking about this is kinda leading to a 2nd question, as the real A-10C does not have a trim reset function but only the Trim T/O button, do pilots use this Trim T/O funtion in flight to re-centre all surfaces?

Is the non-real trim reset function the same as holding the Trim T/O button until all surfaces are reset?

For those unfortunate enough to not have any fancy gear but a simple stick instead. Take a look at my sig and try the HOKAS chart for yourself. It is only a chart since it is based on simple keyboard inputs which you can easily map using the in-game control options.

I'm using a plain and simple Microsoft stick with no drivers and no software available anymore, just an 8-way hat recognised by DirectInput and map-able (is that a word?) in-game.