borisvp

Hi, Perhaps someone can shine some light on this. I have a script group dl'ed for the FBW A320. The script for the EXT PWR Korry switch (which I want to use as an example) looks like this and works just fine - I just don't understand how: (L:A32NX_EXT_PWR_AVAIL:1,·Number)·(L:A32NX_OVHD_ELEC_EXT_PWR_PB_IS_ON,·Number)·!·and·(L:A32NX_OVHD_INTLT_ANN,·Number)·0·==·(L:A32NX_ELEC_DC_2_BUS_IS_POWERED,·Bool)·and·or·1·and·1·and·(L:A32NX_OVHD_INTLT_ANN,·Number)·2·==·if{·0.1·}·els{·1·}·* (>L:ExtPwrSeq1) (L:A32NX_EXT_PWR_AVAIL:1,·Number)·(L:A32NX_OVHD_ELEC_EXT_PWR_PB_IS_ON,·Number)·and·(L:A32NX_OVHD_INTLT_ANN,·Number)·0·==·(L:A32NX_ELEC_DC_2_BUS_IS_POWERED,·Bool)·and·or·(L:A32NX_ELEC_AC_1_BUS_IS_POWERED,·Bool)·and·1·and·(L:A32NX_OVHD_INTLT_ANN,·Number)·2·==·if{·0.1·}·els{·1·}·*· (>L:ExtPwrSeq2) (L:A32NX_OVHD_INTLT_ANN,·Number) is the position of the test switch: TEST = 0 / BRT = 1 / DIM = 2. The rest should be self explaining. (L:ExtPwrSeq1) and (L:ExtPwrSeq2) are variables which describe the status of the annunciator, depending on GND PWR and EXT PWR status. (1) controls the AVAIL light, (2) the ON light. 0 + 0 = OFF 1 + 0 = AVAIL 0 + 1 = ON With GND PWR available (1), EXT PWR off (0), Test switch BRT (0), DC bus not powered (0), the upper half of the script up to the "if" would look like this: 1 0 not and 0 0 == 0 and or 1 and 1 and 0 2 == The result is 0 which triggers the els action and sets (L:ExtPwrSeq1) to 1 (AVAIL light is on). What I don't understand in the order this script is being processed. According to what I found RPN takes two operands and uses the operator on these two. Except for the negation (not), which is performed directly on the preceding operand. Which brings me to this: 1 1 and 0 0 == 0 and or 1 and 1 and 0 2 == And next: 1 0 0 == 0 and or 1 and 1 and 0 2 == Here I'm lost. Three operands and a == operator. And then "and or" right behind each other. What am I missing? Boris

Hi, As ist says in the title - I try to read the LVars from the BKSQ TBM850, but it keeps failing. My version is 4.10b51, and lorbysi-content-hooks is present in Community. I'm trying to find the variable for a specific button. Boris

Hi, Did I miss something or is ist really so that the throttle axes do not work past the idle detent of the lever? Value is 0 at the detent, and seems not to be adjustable. If so, how would I assign a reverse axis function? My sim is MSFS, and I have not installed any specific software for the Bravo yet. Regards Boris

Hi all, I know, vasFMC is not supported anymore, but perhaps somebody knows my problem and has a workaround for me :smile: I am running vasFMC standalone with Thomas Ruth's A340 (same happens with the default A321, however) with the following settings: hardware throttle set to AXES_THROTTLE_SET via FSUIPC 4.95 A/THR mode in vasFMC to VASFMC Airbus A/THR in vasFMC to ON When loading the aircraft, the engines are running with the start switches OFF (for whatever reason). Now the throttle works fine: The lever commands N1, the FADEC does the rest. IDLE, LVR mode, all detents. Note the cyan arc following the N1 bug. As soon as one start switch is set to ON (and this necessarily happens, because I must stop the engines to program the FMGC) this does not work anymore. I still see the N1 bug in the ECAM, but simultaneously there is a constant IDLE input which keeps the engines in idle and prevents taxiing. The detents still work. The cyan arc is gone now, and IDLE is blinking. Any help is appreciated. Regards Boris

Hallo Robert, das passierte von der Installation weg mit allen angezeigten Profilen, auch wenn ich es noch nie geöffnet habe. Immer zuerst der Fehler, dann geht's. Nochmal drüberinstallieren? Gruß Boris

Dear Peter, I am just configuring version 2.7 for FSX, and when I click on the "edit profile" button I get an unhandled exception error. After ignoring this message and clicking the second time, the dialog opens and seems to work fine. If this has no other effect than that I must cklick twice when editing a profile, I'm fine. I just want to make sure that nothing goes wrong with the FSX setup here. This is the text of the error message (I only have it in German...): "Der Wert 0 ist für Value ungültig. Value sollte zwischen 'Minimum' und 'Maximum' liegen. Parametername: Value" ************** Ausnahmetext ************** System.ArgumentOutOfRangeException: Der Wert 0 ist für Value ungültig. Value sollte zwischen 'Minimum' und 'Maximum' liegen. Parametername: Value bei System.Windows.Forms.TrackBar.set_Value(Int32 value) bei SIMstarter.simConfig_F.set_TrackBar(String value_String) bei SIMstarter.simConfig_F.easyConfigFSX_setLabel(List`1 config_List) bei SIMstarter.simConfig_F.load_easyConfig() bei SIMstarter.simConfig_F.currentProfile_ComboBox_SelectedIndexChanged(Object sender, EventArgs e) bei System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e) bei System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value) bei SIMstarter.main_F.profileSettings_Button_Click(Object sender, EventArgs e) bei System.Windows.Forms.Control.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ButtonBase.WndProc(Message& m) bei System.Windows.Forms.Button.WndProc(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Geladene Assemblys ************** mscorlib Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll. ---------------------------------------- SIMstarter Assembly-Version: 2.7.4.0. Win32-Version: 2.7.4.00. CodeBase: file:///C:/Program%20Files%20(x86)/SIMstarter/SIMstarter.exe. ---------------------------------------- Microsoft.VisualBasic Assembly-Version: 10.0.0.0. Win32-Version: 14.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll. ---------------------------------------- System Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- System.Core Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll. ---------------------------------------- System.Windows.Forms Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll. ---------------------------------------- System.Drawing Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1068.2 built by: NETFXREL3STAGE. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll. ---------------------------------------- System.Runtime.Remoting Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll. ---------------------------------------- System.ServiceProcess Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll. ---------------------------------------- System.Configuration Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll. ---------------------------------------- System.Xml Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1067.0 built by: NETFXREL3STAGE. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll. ---------------------------------------- Accessibility Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll. ---------------------------------------- Ionic.Zip Assembly-Version: 1.9.1.8. Win32-Version: 1.9.1.8. CodeBase: file:///C:/Program%20Files%20(x86)/SIMstarter/Ionic.Zip.DLL. ---------------------------------------- mscorlib.resources Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll. ---------------------------------------- ************** JIT-Debuggen ************** Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der Konfigurationsdatei der Anwendung oder des Computers (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden. Die Anwendung muss mit aktiviertem Debuggen kompiliert werden. Zum Beispiel: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> I also tried with an empty "Flight Simulator X Files" folder, but there was no change. Regards Boris

Huh? An I7-2600 @ 4.7 and no HDR? What kind of machine do we need to run HDR?Boris

Hi, I dug deep and found this old thread, so why make a new one :( Since nothing has happend regarding the development of a native FSX King Air in the meantime, the Aeroworx aircraft remains the only alternative. Basically it works in my FSX, and I can live with the prop texture autogen remover, but there is one nasty thing: Whenever I click on a main panel gauge in the VC, the right power lever moves to full power (same in the 2D cockpit, but that is not an option anyway).Does anyone know a workaround for this problem? ThanksBoris

Hi,in my FS the standard ground roll (bnroll.wav) is permanently playing, even when the plane has stopped and the power is off. Happens with every plane that has bnroll.wav as rolling sound, does not happen with planes with a different ground roll sound.Filemon says: fs9.exe READ bnroll.wavWhat might that be?RegardsBoris

Well, what is high end? It is said about LOD radius, that it only has influence on the texture representation. Anyway, I tried 6.5 - no change. 8.5 - seems a little better, but still too abrupt. Above 10 it starts looking OK (which micht be imagination and wishful thinking, though), but gives me OOM after 10mins.RegardsBoris

I tried. Bare landscape, and still popping. Sorry, but FSX looks too good with autogen on dense - as long as you don't move.Isn't there a way to increase the autogen draw distance? Or to build the fader function directly into the autogen? Hmm, probably not, or someone would already have done it. Well, then I'll hope for a change - and wait. FS9 is fine, too :( RegardsBoris

If I had knowledge about programming I might say "what a stupid move from Aces" - of course I haven't :( But I'd rather live with less autogen showing smoothly than way too much than current hardware can handle suddenly flashing in the way it is now - and this even with the lowest setting. Well, FSX has lots of improvements over FS9 (better mesh representation, no simplified world model, much better textures even by default, less blurring - but that, dear FSX, is a KO criteria.Anyway, here's my hardware - maybe there can be reached at least some improvement to make the thing usable for me.MSI P45 Platinum (latest BIOS and chipset drivers)E86002x2GB OCX 1066 Reaper K2MSI GTX260 / TH2G analog with 3x17" / 1x15"MSI 8600 / 2x 17"VGA driver version 178.24XP SP2 on 2xSeagate 500GB/7200 RAID0FS on 2x WD Raptor 74GB RAID0Corsair 620W power supplyThanks for your help :( Boris

Hello,as the search for "autogen" and "popup" reveals more that 1000 results, I may be excused to ask an already answered question again :( I'd like FSX a lot, if it weren't for the autogen which keeps popping up in close distance. This is really annoying. I already learnt that this has something to do with the so called alpha shader, which the late Aces guys removed with SP 2.But SP2 was back in 2007, and I want to ask if there is a fix available by now? ThanksBoris

Hi Ron,I don't have a USB headset, but I do have a set of small USB speakers. I connected those, and bingo. It talks :) So it obviously has something to do with the sound chip (I have a Realtek High Definition Audio). I will go get another sound card.Best RegardsBoris

Hi David,unfortunately it doesn't. But - could it have to do with using the system internal sound system? Which is what I do; I don't have an extra sound card. I just don't want to buy one and then find out that it doesn't solve the problem...RegardsBoris