All I'm wondering is if it's going to externally be animated

All I'm wondering is if it's going to externally be animated

lol

I can only hope that from Roberts reference to engine shutdown during taxi-in, that they've got the aircraft taxiing nicely on one engine.Best regards,Robin.

In the past, there have been shots at the ground contact model being the reason for taxiing issues, so unless they found a way to work around it, it's more of an FS limitation than lack of effort on the developers' part. I'll hope, but I'm not going to put much emotion in said hope.

There is one work-around and that is to put the thrust vector of all FS engines down the center-line of the aircraft then use effects to simulate the engine positioning but the issue is that the FS engines still contrail.Best regards,Robin.

I'm sure there's other "hacks" to correct this.

I got a tough one here: I use an axis for the motion of the stab trim (a racing wheel that works fine with all FSX models) but I have a weird problem when I use the axis.The product: PMDG 737-800 NGXThe problem:I start with the trim at the center position. Then I turn the wheel, say full left. At first the trim goes forward (nose down), which is fine but as my wheel reaches about 75% left, the trim suddenly starts going in the opposite direction (nose up) until I hit 100% left on my wheel. Then I move the wheel to the right and the trim continues going nose up until I hit the center position of my racing wheel, then as i keep turning the wheel to the right, the trim now starts going nose down even though I haven't moved my wheel to the left, and so on. So no matter what i do, the trim doesn't seem to work in a linear fashion when it's driven by an axis.But there's more to it. If I move the wheel, say full left and I start moving it right and left in small continuous strokes (between 100% left and 75% left) the trim goes nose down in a nice linear way as long as i keep the motion. Move the wheel to full right and move it in small strokes (100% right -> 75% right) and the trim nicely moves nose up all the way to max up. That looks like a hell of a bug to me!Thinking it might be a compatibility issue I changed to several other physical axis but the problem remained the same. I'd appreciate any hints on that one (besides having to use annoying key commands to work the trim :/ )

Get a two-way switch for it. I use one of the up/down switches on my Saitek yoke system (more comparable to the trim commands on a 747 than a 37) and it works just fine.

lol

[severely off topic] Hey Ethan where did you disappear to?

[severely off topic] Hey Ethan where did you disappear to?

I'm here. =)Really REALLY busy with work.

I got a tough one here: I use an axis for the motion of the stab trim (a racing wheel that works fine with all FSX models) but I have a weird problem when I use the axis.The product: PMDG 737-800 NGXThe problem:I start with the trim at the center position. Then I turn the wheel, say full left. At first the trim goes forward (nose down), which is fine but as my wheel reaches about 75% left, the trim suddenly starts going in the opposite direction (nose up) until I hit 100% left on my wheel. Then I move the wheel to the right and the trim continues going nose up until I hit the center position of my racing wheel, then as i keep turning the wheel to the right, the trim now starts going nose down even though I haven't moved my wheel to the left, and so on. So no matter what i do, the trim doesn't seem to work in a linear fashion when it's driven by an axis.But there's more to it. If I move the wheel, say full left and I start moving it right and left in small continuous strokes (between 100% left and 75% left) the trim goes nose down in a nice linear way as long as i keep the motion. Move the wheel to full right and move it in small strokes (100% right -> 75% right) and the trim nicely moves nose up all the way to max up. That looks like a hell of a bug to me!Thinking it might be a compatibility issue I changed to several other physical axis but the problem remained the same. I'd appreciate any hints on that one (besides having to use annoying key commands to work the trim :/ )

If you are going to set your trim with an axis control, you should use FSUIPC. You can set up elevator, aileron and rudder trim wheel axis control with it. It can set accurate axis control for trim. Then I also set the left spring loaded switch on my Saitek Yoke for Elev Trim Up and Elev Trim Down with the check on repeat while holding the button. That gives me the electric trim action similar to the yoke on the real aircraft. Bob

I got a tough one here: I use an axis for the motion of the stab trim (a racing wheel that works fine with all FSX models) but I have a weird problem when I use the axis.The product: PMDG 737-800 NGXThe problem:I start with the trim at the center position. Then I turn the wheel, say full left. At first the trim goes forward (nose down), which is fine but as my wheel reaches about 75% left, the trim suddenly starts going in the opposite direction (nose up) until I hit 100% left on my wheel. Then I move the wheel to the right and the trim continues going nose up until I hit the center position of my racing wheel, then as i keep turning the wheel to the right, the trim now starts going nose down even though I haven't moved my wheel to the left, and so on. So no matter what i do, the trim doesn't seem to work in a linear fashion when it's driven by an axis.But there's more to it. If I move the wheel, say full left and I start moving it right and left in small continuous strokes (between 100% left and 75% left) the trim goes nose down in a nice linear way as long as i keep the motion. Move the wheel to full right and move it in small strokes (100% right -> 75% right) and the trim nicely moves nose up all the way to max up. That looks like a hell of a bug to me!Thinking it might be a compatibility issue I changed to several other physical axis but the problem remained the same. I'd appreciate any hints on that one (besides having to use annoying key commands to work the trim :/ )

It's not a bug, it's simply that it's not meant to be mapped to an axis like that (I take it you are using the FSUIPC ElevTrim Axis). It works increasing / decreasing when you use the clickspots and to make it work with an axis you'll need to either wait for the SDK and hope for some kind of (unrealistic?) axis behaviour support, or code the axis in Lua.I can do that for you in a few minutes if you want, but can you please confirm you have a registered copy of FSUIPC?

Hey! i don't have FSUIPC installed so i believe that may be a reason for the crazy behavior. I'm giving that a try for sure, thanks for the advice

Hey! i don't have FSUIPC installed so i believe that may be a reason for the crazy behavior. I'm giving that a try for sure, thanks for the advice

If you have FSUIPC registered:

MIN_AXIS = 16384MAX_AXIS = -16384MIN_TRIM = 0MAX_TRIM = 16.9PRECISION = 0.04function trimSet(param)--ipc.log("trimSet" .. " " .. param)factor = (MAX_AXIS - MIN_AXIS) / (MAX_TRIM - MIN_TRIM)offset = MIN_TRIM - (MIN_AXIS / factor)trimTarget = (param / factor) + offsetipc.set("trimTarget", trimTarget)tt = format_num(tonumber(trimTarget), 2, "")ipc.writeSTR(0x3380, "Trim: " .. tt);ipc.writeSW(0x32FA, 5);endfunction trim(time)factor = (MAX_AXIS - MIN_AXIS) / (MAX_TRIM - MIN_TRIM)offset = MIN_TRIM - (MIN_AXIS / factor)current = ipc.readLvar("L:ElevTrimTT")target = ipc.get("trimTarget")--ipc.log("trim " .. time .. " " .. target - current)if target - current > PRECISION then  ipc.control(70310, 8192) elseif current - target > PRECISION then  ipc.control(70310, 16384)endcurrent = ipc.readLvar("L:ElevTrimTT")end-- from sam_lie-- Compatible with Lua 5.0 and 5.1.-- Disclaimer : use at own risk especially for hedge fund reports :-)---============================================================-- add comma to separate thousands--function comma_value(amount)  local formatted = amount  while true do 	formatted, k = string.gsub(formatted, "^(-?%d+)(%d%d%d)", '%1,%2')	if (k==0) then  	break	end  end  return formattedend---============================================================-- rounds a number to the nearest decimal places--function round(val, decimal)  if (decimal) then	return math.floor( (val * 10^decimal) + 0.5) / (10^decimal)  else	return math.floor(val+0.5)  endend--===================================================================-- given a numeric value formats output with comma to separate thousands-- and rounded to given decimal places----function format_num(amount, decimal, prefix, neg_prefix)  local str_amount,  formatted, famount, remain  decimal = decimal or 2  -- default 2 decimal places  neg_prefix = neg_prefix or "-" -- default negative sign  famount = math.abs(round(amount,decimal))  famount = math.floor(famount)  remain = round(math.abs(amount) - famount, decimal)    	-- comma to separate the thousands  formatted = comma_value(famount)    	-- attach the decimal portion  if (decimal > 0) then	remain = string.sub(tostring(remain),3)	formatted = formatted .. "." .. remain ..            	string.rep("0", decimal - string.len(remain))  end    	-- attach prefix string e.g '$'  formatted = (prefix or "") .. formatted    	-- if value is negative then format accordingly  if (amount<0) then	if (neg_prefix=="()") then  	formatted = "("..formatted ..")"	else  	formatted = neg_prefix .. formatted	end  end  return formattedendevent.param("trimSet")event.timer(200, "trim")

1.- Copy that to a text file called trimNGX.lua for example and save it in the Modules folder2.- Add the Auto entry in your FSUIPC4.ini [Auto.Boeing 737-823NGX American Airlines Winglets]1=Lua NGXInit 3.- Asign your axis to the control "LuaValue trimNGX" You may need to adjust the max and min values for your axis. Let me know if it works as it is or not

Hi dazz! I saved the .lua file as you suggested and i added the auto entry at the final line in my FSUIPC4.iniSince my model is not american airlines i changed it to my aircraft title as it appears in the aircraft.cfg file [Auto.Boeing 737-8Q8NGX Air Jamaica Winglets]1=Lua NGXInit i double checked all steps before posting this.now my problem is i dont get how to assign my axis to the control "LuaValue trimNGX" i cant see it in the FSUIPC axis assignments nor can i in the FSX menu. i think i'm missing something here Thanks in advance