smoothchat

My solution to control all the Latécoère (6) and the “Dornier Do X” (12) engines with a 4 throttle controller. I defined the 4 lever axes in FSUIPC7 and then put the following modified script into the fsuipc7.exe folder. Create and use an MSFS controller config with the throttles removed for the Latecoere and Dornier X. Many thanks to the person who sent me the original code. Note: the script doesn’t work with the Hercules for some reason, I use SPAD.neXt for the Hercules. --===================================== -- File Throttle.lua -- Put this file to the FSUIPC folder that contains the FSUIPC.ini file -- Add the file name to the [AUTO] section of the .ini file like this -- [AUTO] -- 1=lua throttle -- or (make sure numbering is consistent if the AUTO section already has entries) -- [AUTO] -- 1=lua xyz1 -- 2=lua xyz2 -- 3=lua throttle ---------------------------------------------------------- --variable definitions local user_aircraft_type = "" -- holds name of user aircraft in sim local number_of_engines = "" -- how many engines on the current aircraft local calc_code = "" -- string to hold RPN code local combine_throttles = 0 -- 0 = no, 1 = yes local My_Aircraft_Type = 0 -- Number assigned to a recognised aircraft --this is called whenever new aircraft is loaded in the sim function aircraft_changed(offset, uat) user_aircraft_type = ipc.readSTR(0x3D00, 256) number_of_engines = ipc.readUW(0x0AEC) ipc.log("in change_aircraft_name = <"..offset.." "..user_aircraft_type..">") ipc.log("Number of engines = <"..offset.." "..number_of_engines..">") if string.find(user_aircraft_type,"Latecoere") then -- Is this a recognised aircraft My_Aircraft_Type = 1 elseif string.find(user_aircraft_type,"Dornier Do X") then My_Aircraft_Type = 2 else My_Aircraft_Type = 0 os.exit() -- Not a recognised aircraft, so stop the script. end end --this is called when Thrustlever 1 changes function throttle_lever_1(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) " .. -- throttle 1 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:2, Percent) " -- throttle 2 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) " .. -- throttle 1 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:2, Percent) " .. -- throttle 2 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:3, Percent) " -- throttle 3 ipc.execCalcCode(calc_code) end end --this is called when Thrustlever 2 changes function throttle_lever_2(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:3, Percent) " -- throttle 3 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:4, Percent) " .. -- throttle 4 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:5, Percent) " .. -- throttle 5 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:6, Percent) " -- throttle 6 ipc.execCalcCode(calc_code) end end --this is called when Thrustlever 3 changes function throttle_lever_3(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:4, Percent) " -- throttle 4 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:7, Percent) " .. -- throttle 7 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:8, Percent) " .. -- throttle 8 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:9, Percent) " -- throttle 9 ipc.execCalcCode(calc_code) end end --this is called when Thrustlever 4 changes function throttle_lever_4(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:5, Percent) " .. -- throttle 5 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:6, Percent) " -- throttle 6 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:10, Percent) " .. -- throttle 10 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:11, Percent) " .. -- throttle 11 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:12, Percent) " -- throttle 12 ipc.execCalcCode(calc_code) end end --callbacks event.offset (0x3D00, "STR", 64, "aircraft_changed") event.offset (0x25F0, "SW", "throttle_lever_1") event.offset (0x25F2, "SW", "throttle_lever_2") event.offset (0x25F4, "SW", "throttle_lever_3") event.offset (0x25F6, "SW", "throttle_lever_4") --=====================================

I have the opposite issue. I want to keep the older version of AviaServer (and prevent it from updating). It took me weeks to get my home cockpit working with all my hardware. I will be keeping the older version of the 737 for quite some time. Is there a way to prevent the auto update of AviaServer from occuring?

I persevered with the desire to have no errors when error logging is enabled in P3Dv3. My remaining error was ... Key values exist outside of a section: File:E:\Games\Prepar3Dv3\SimObjects\Airplanes\PMDG 777-200LR\panel\panel.cfg Key: as well as other spurious errors about duplicate key names. It turms out that the PMDG 777-200LR\panel\panel.cfg file has embedded unicode. I just loaded the panel.cfg file into notepad, cut and pasted the text into another empty notepad window and saved it as panel.cfg (ignoring the unicode warnings). No More Errors.

Hmm, I am using a Logitech USB headset. I have set the P3D Primary Playback device to my main speakers (Voice Playback and Capture to the default communications) In Fs2crew I have set the audio device to the Headset. Using the HS button makes no difference. Changing the audio device in the FS2Crew Secondary panel makes no difference (even after resetting the audio) Luckily it all works as it should by default, so I can live with it. It would have been an issue if it was the other way around ;-)

Thanks Brian, Yes. Much of the audio goes thru the headset (Voice etc, with engine sound and P3D environment going to the main speakers), but unchecking HS seems to make no difference. I would think that de-selecting HS would have ALL sound go to the speakers eg. so a friend can hear whats going on. I must be mistaken. I'm running P3Dv3 on Win7 x64.

Hello everyone. I don't seem to notice any difference when I enable or disable the HS button (NGX Reboot 1.1). I am wondering which sounds this switch is supposed to redirect to either my headset or the primary output device? All FS2Crew sounds seem to still go to my headset. (With the P3D background and engines sounds going to my priimary speakers as set in the p3d 'primary playback device' sound settings) Any info would satisfy my curiosity. Thanks.

Hi. I love Linda, however, I have discovered that .... When using the PMDG 737, if I undock my PFD or ND , Linda gives me a "range check error". Also the "FSX Sync" stops displaying the current aircraft (it defaults to -- Aircrafts -- ). Linda 2.6.3 P3D 2.5 Win7 x64 PMDG 737NGX While this isn't critical, I thought I would post my findings anyway, to help diagnose the general Range Error issue mentioned elsewhere. Also, Linda doesn't 'reset' when I unload P3D and reload P3D. I have to kill Linda and restart it. Is there a way to avoid this?

For some strange reason, I cannot set the MCP altitude to 35100 using a voice command. I have tried "Set altitude 3 5 1 hundred" but I get ignored. (despite the words being correctly interpreted and displayed by the recognition software) "Set altitude 3 5 zero hundred" gives me 35000 and works fine as does "Set Altitude 3 5 thousand" Am I to use the "Set Flight Level" command instead ? as this appears to work.

Hi guys. I'm having a lot of fun with Linda (configuration heaven). Congratulations on a fantastic program. One quick newbie question if I may tho, I am wanting to utilize the radio panel dials for different functions (like panel light brightess) when in shifted mode. To allow this, in unshifted mode, I want to have Linda read the Saitek radio panel and drive the values directly in the sim, but on my system, the values update about 2 times a second as I rotate the dial. I simply assigned the xxx inc and dec attributes against the relevant "button" entries in Linda, and disabled the corresponding action in SPAD. Rotating the dial works, but only updates and changes twice a second. It also appears to be buffered, as a quick turn results in the value increasing for a second or two after I stop. Am I doing something wrong? Interesting........: If I enable the Tracer in Linda, the update speed increases. Even after leaving the tracer section, the speed increase remains. Linda 2.6.3 Win7 64bit Prepar3d 2.4 4790k

I purchased from the VRInsight online shop.

Hi, I applied some small enhancements to my recently purchased VRInsight 737 overhead. When I bought it from VRInsight, I asked them to include some extra knobs (to fill the missing plates) which I attached with some blu-tack.. I also printed out some guages (30mm and 20mm), and found some cheap plastic compasses on ebay, which I cracked open to use as bezels for the dummy gauges. I think that having some dummy bits in the "blank" areas makes a big difference to the asthetics and makes the unit look more complete. Anyone else with this overhead, please post a reply. Mount the overhead on the wall using a vesa wall mount, lay some black cloth sheeting across the top and down to the monitors and you get a cheap cockpit shell. An iPad provides a separate instruments display, and a $50 Pendo hosts a virtual CDU which interfaces to the PMDG NGX.

In your main Prepar3D folder, typically something like c:\program files\prepar3d\shadersHLSL\PostProcess\ PS. I decided to stick with the avgLuminance *= 0.85f; option. I was getting some clipping on the white clouds.

Sorry if this has been covered before (if so please point me to it) but I have found a way to increase the brightness with HDR enabled. In the shadersHLSL/PostProcess folder is a file named ' HDR.hlsl ' Make a backup of this file elsewhere, then load it into notepad or similar editor. At line 166 you will find ' //avgLuminance *= 0.85f; ' which is commented out by the two slashes. remove the two slashes ie: ' avgLuminance *= 0.85f; ' and save. If you want to experiment with this value, increasing it makes the image darker, decreasing makes it lighter. I haven't determined whether it messes with the overall HDR experience, but the programmer put this line in and it seems to work. Note: In my case, just saving and running P3D worked the first time, but later runs of P3D resulted in a black (blank) screen. The solution was to ensure that the associated compiled shaders in the ' C:\Users\Yourname\AppData\Local\Lockheed Martin\Prepar3D v2\Shaders ' were deleted. As I understand it, the HDR code looks at the average brightness of the display and boosts it adding bloom to simulate the effects of light and dark. The stock code seems optimised for a standard display. Those of us with triple screens have much larger display area that often includes parts of the side window views. This extra brightness has the HDR overcompensating and resulting in a darker than desired screen. Changing the code at line 166 seems to tell the code that the average brightness is less, therefore add more brightness. ------------------ Another option which leaves the rest of the code alone, is to increase the return value of the ' Composite ' function. Insert ' final *= 1.2f; ' just before the last line of code eg: bloom = bloom * BloomMagnitude; // Add in the bloom float3 final = color + bloom + brighten + dither; final *= 1.2f; return float4( final, 1.0f ); } So far I prefer the above option. Note: setting a value too high causes bright parts to clip. I welcome everyone's comments.

I too am having difficulties with New York and P3D v2.3 Half the buildings appear with the night textures (in the daytime) and performance is much slower than FSX. Copy the folder over to FSX and the textures are fine