BrassEm

They obviously didn't thunk that one through properly. Good for a laugh though, funny how they sped the video up. Should have made it quicker, undo the belt harness and really fly!!!!

That is a good question. None that I've seen other than Saitek giving a hole mounting diagram for the whole base. Obviously not really suitable for what you want I would think. From the connectors on the base of the stick handle it looks like the stick handle is sending serial data to the base. What you can possible do is hard wire the stick to the base with longer wires, one to one, to give you the extention. How far you can extend via the added wires would need to be experimented with. I know the logic works on 3.3vdc, and would have to assume the transmission is not buffered. So you might get a foot or two before the stick goes haywire. (For myself I will be modifying the stick for my own central seat layout, but I will be fitting a new control processor for the stick hardware. Also figuring out how to make it interchangeable with other devices too like a yoke.) If I find any direct extention details I willl post it here.

Stock reinstall of the drivers.exe from MadCatz -> NO! All I ever got was the (Bulk) drivers and that is all!!! So... Extracted the appropriate files from the driver.exe then in a DOS PROMPT (as admin) pnputil -a SaiG2215.inf (The missing one) to install the driver and register it in registry. Then updated the HID drivers in DEVICES till I hit the updated SaiG2215.sys (There is no indication which one it is, just got to go through them till you hit it.) and it will then restore the "Saitek Pro Flight X-55 Stick" entry. (I had to do that for all the drivers on the X-55 to get it to work out of the box brand new! :mad::mad::mad:, that is also why I listed them here. ) Don't get me wrong, it is a great HOTAS, when it works.

Installation double check After weeks of intermittent throttle problems I got it sorted and I am posting to give a heads up. The X-55 was working fine for months, then the stick buttons would stop working intermittently in DCS. Control panel Devices and Printers all good. HUD would work, jump in game and would not work, HUD test okay, jump in game no. HUD test okay, jump in game okay. Restart mission and not work in game, HUD test okay, would only work with HUD test up. All the time the throttle was working fine, every time. But the stick was flakey. Utter frustration!!!!!! Control Panel DEVICES AND PRINTERS reported both the Stick and Throttle okay. Drilling down the X-55 installation you should see the following in DEVICE MANAGER; Human Interface Devices Saitek Pro Flight X-55 Rhino Stick (<-- Mine went AWOL!) Saitek Pro Flight X-55 Rhino Stick (Bulk) Saitek Pro Flight X-55 Rhino Stick (HID) Saitek Pro Flight X-55 Rhino Throttle Saitek Pro Flight X-55 Rhino Throttle (Bulk) Saitek Pro Flight X-55 Rhino Throttle (HID) Saitek Magic Bus Programmable Hotkeys Programmable Root Enumerator Programmable Support for Keyboard Programmable Support for Mouse DRIVER FILE DETAILS UNDER DEVICE MANAGER; HID Drivers Saitek Pro Flight X-55 Stick C:\windows\system32\drivers\SaiG2215.sys (<-- Mine went AWOL) C:\windows\system32\drivers\WdfCoInstaller01009.dll? Saitek Pro Flight X-55 Stick (Bulk) C:\windows\system32\drivers\Said2215.sys C:\windows\system32\drivers\WdfCoInstaller01009.dll Saitek Pro Flight X-55 Stick (HID) C:\windows\system32\drivers\SaiK2215.sys C:\windows\system32\drivers\WdfCoInstaller01009.dll Saitek Pro FLight X-55 Rhino Throttle C:\windows\system32\drivers\SaiGa215.sys C:\windows\system32\drivers\WdfCoInstaller01009.dll Saitek Pro Flight X-55 Rhino Throttle (Bulk) C:\windows\system32\drivers\Saida215.sys C:\windows\system32\drivers\WdfCoInstaller01009.dll Saitek Pro Flight X-55 Rhino Throttle (HID) C:\windows\system32\drivers\SaiKa215.sys C:\windows\system32\drivers\WdfCoInstaller01009.dll Saitek Magic Bus Programmable Hotkeys windows\system32\drivers\SaiMini.sys Programmable Root Enumerator windows\system32\drivers\SaiBus.sys Programmable Support for Keyboard windows\system32\drivers\SiaMini.sys Programmable Support for Mouse C:\windows\system32\drivers\SiaMini.sys Nothing wrong with the hardware or software, just a driver went missing. Just something to double check if you are having some issues over and above the USB power problem. .

Thanks Bourrinopathe. These are probably just as expensive with shipping... Vrinsightshop.com. (There is a 10 pack of white.) I.D is approx 5.3mm. They fits snuggly over the X-55 switches. At full throttle, H4 is close to TGL3 but not a show stopper. I fill these caps and drill to fit over the smaller standard C&K switches. I was going to build an arduino based Overhead/Pedestal but Helios got the better of me.

Thank you! Its under Messaging and Notifications. When sending private messages the forum can make a copy of the message in your Sent Items folder. [ ] Save a copy of sent messages in my Sent Items folder by default

Thanks for the kind words! From looking at it, it is only driven by the microcontroller as a simple toggle switch, on/off. The HUD driver only sees it as a switch also. So at this stage that's all we've got. The microcontroller that they use on the X-55 is extremely powerfull. If they release a SDK, that would open a whole raft of possibilities. But then you need the driver software to suit as well. The mouse nipple appears to be treated as a special case by the controller. So the tactile switch did not show up as a raw button in DCS. :( The HUD has to be used in a configuration for the nipple to function.

X-55 Mouse Nipple Modification - PART TWO X-55 MOUSE NIPPLE MODIFICATION - PART TWO Created by BrassEm 2015. START OF PART TWO Wire up the resistors to join to the existing wires as per the schematic. IMPORTANT NOTE; because the resistors are so small and it is very hard to distinguish between the values. The 560 ohm resistors were painted/marked to distinguish them. Wire up the 4 way tactile switch as per the schematic. Solder together and heatshrink/insulate. Tack the switch into position with a small amount of hot glue. Make sure of the up orientation. Pointing just to the left of the microswitch should give an average up across the throttle movement range. Try out the switch to make sure it is perpendicular to the board, the stalk is in the middle of the hole quadratures, and the up is where you want. When happy tack the switch down further to secure it. (You may want to change its position late so don't go overboard with the hot glue.) Reassemble in reverse order of disassembly. Double check the switches to make sure they are working. NOTE: When closing the two shells together ensure that the main cable running from the the throttle is not pinched. This can be very difficult to achieve. After it's all screwed back together, plug in and test. Do not forget to set the mouse feed rates low in the HUD before it is tested. The mouse nipple is now working reliably and consistantly as a 4 way tactile switch. .

X-55 MOUSE NIPPLE MODIFICATION - PART ONE Created by BrassEm 2015. DISCLAIMER The following information is my personal interpretations in review of the issues. You are advised to use your own discretion to the correctness and suitability for your own use. Use of the following information and its outcome is solely the responsibility of the user. While the process worked for me, results may differ. This information is intended as complete. Any fragmentation is outside the scope of its intent. Be aware that any modification inside a manufacturers warranty period will void said warranty and possibly void a repair by the manufacturer outside of warranty. (Bottom line is if your not sure, don't do it.) INTRODUCTION This mod was developed by my frustration with the mouse nipple operation. Direction control was intermittent and I had no DOWN direction unless I really leaned on the stick - when it would work and if I got the right direction. This is a great HOTAS and not wanting to have down time shipping the throttle back under Warranty Return, I purchased another HOTAS to use while I shipped the other. I connected the new unit and still had the very same issues! Driver Issue??? Very possible... Investigating the mouse nipple mechanism I found that it was a carbon membrane contact type switch. I had cured another well known controller that used the same type of mouse controller by replacing it with a tactile switch, time to cure my X-55. This one was tricky as the contacts had resistance both high and low and were not all commoned like other switches. A digital multimeter sorted the issue out. This mod is not heavy duty. Tactile feedback is good and very little force is needed to toggle the direction switch. While not a true mouse where pressure increases velocity, the driver can set the direction velocity so you would need to find a velocity that works for you. As a tactile direction switch it works reliably with little force. The following details were carried out on my secondary HOTAS after proving the original modded throttle worked. To complete a mod like this you would need to have a reasonable degree of technical and dexterous competence. And have a thorough understanding of the process before proceding. If all components are on hand it would take about five to six hours uninterrupted to complete a mod like this. PARTS LIST TPA511GLFS 5 way switch x1. 5.6K Ohm 1/8 Watt Resistor x4. 560 Ohm 1/8 Watt Resistor x2. Arduino breadboard jumper leads - various. (Flexible multi strand wire.) 1.5mm Heatshrink. Plastic rod for switch stalk. Long plastic golf tee's are perfect. TOOL LIST Soldering setup. Small tip soldering iron, solder, wick, Wet paper towel to clean tip. Small philips head screwdriver that has at least 30mm small shank to get into the plastic recesses of the screws. Medium philips head screwdriver about No.2 for the two screws holding the handle in place. Very small philips head screwdriver to undo the Mouse Nipple assembly. Hot glue gun (Small nozzle) to tack the switch and wires into place. Blutac (sticky putty) to hold stuff in place while soldering etc. Small side cutters to trim wires and heat shrink. Sharp blade to trim wires. Tweezers Torch or very good lighting. Magnifying Glass and/or damned good eyesight. Drill or Dremel to drill the 2.0mm diameter hole in you switch stalk 2.0mm Diam drill bit for switch stalk. Pin and superglue to tack on the stalk to the switch if the 2.0mm diam hole is sloppy. (Or try again.) Patience. PURCHASING 5 WAY Switch Manufacturer: C & K COMPONENTS Order Code: 2320116 Manufacturer Part No TPA511GLFS http://au.element14.com/c-k-components/tpa511glfs/switch-5-way-0-05a-gullwing/dp/2320116?CMP=i-55c5-00001621 ARDUINO JUMPER CABLES (65 PACK) DF-FIT0010 $8.79 AUD http://littlebirdelectronics.com.au/products/arduino-jumper-cables-mm MULTICOMP MF12 560R RESISTOR, 0.125W 1% 560R $0.10 AUD http://au.element14.com/multicomp/mf12-560r/resistor-0-125w-1-560r/dp/9343350?CMP=i-55c5-00001621 MULTICOMP MF12 5K6 RESISTOR, 0.125W 1% 5K6 $0.21 AUD http://au.element14.com/multicomp/mf12-5k6/resistor-0-125w-1-5k6/dp/9343369?CMP=i-55c5-00001621 1.5MM BLACK HEATSHRINK TUBING EL-WH5530 $1.60 AUD http://littlebirdelectronics.com.au/products/1-5mm-black-heatshrink-tubing Micro Drill Bit Set 0.7 - 2.2mm CAT.NO: TD2407 $14.95 AUD http://www.jaycar.com.au/Tools-%26-Soldering/Hand-Tools/Drill-%26-Socket-Sets/Micro-Drill-Bit-Set-0-7---2-2mm/p/TD2407 MODIFICATION DETAILS Test the unmodded unit to confirm operation. For ease of handling slide the throttle handle lock in to lock the two handles together. Move throttle friction knob to mid position. Where there is least friction on the throttle handle. Undo 15 screws to remove the bottom part of the case. Release right throttle cable from its holding clip to allow more movement. Undo the two larger screws that hold the throttle handle to the slide mechanism. Release the throttle hand lock to free the right throttle handle. The throttle handle should now be free to be removed from the slide mechanism. Manoeuvre the throttle so that you have good access to the screws and assembly. Resting it on a foam block helps to keep strain off the cables. Remove all the screws if possible. Use the blue tack on the tip of the screwdrive to draw them out if needed. Else the tweezers. Gently crack the two halves of the handle all around. After cracking splay the handle open like a clam. Move the 2x4way switch board over to the left and out the way. Notice that it is located by the notch. NOTE THE POSITION AND CABLE LAYOUT OF THE INTERFACING BOARD. Undo the two screws holding the interfacing board and move the board out of the way. NOTE THE CAVITY UNDER THE INTERFACING BOARD, THAT IS WHERE THE RESISTORS ARE GOING TO BE PLACED. Manoevre the shells around to get access to the screws holding down the mouse nipple board (mn board). Care should be taken when removing the mn board. There is a spring on the red E button cap that holds it in position. Also the plunger for the E microswitch is square on. Note this as it will need to go back the same way. Remove the two screws and remove the mn board. Making sure to not loose the spring on the E botton cap. IMPORTANT!!!! DO NOT CUT THE BLUE AND WHITE WIRES!!! THEY ARE FOR THE RED E BUTTON!!!!. Trim and tin the four wires. Remove the 4 screws and remove the black holding bracket. Turn the board over and remove the two very small screws to remove the mn assembly. Carefully prise the four rubber prongs from the pcb to remove the button membrane. Prep the switch stalk and test on the switch. I used a 1.8mm drill bit by hand and it shanked out to a nice fit without glue. END OF PART ONE.

Thanks for sharing! I am just at the start of breadboarding now. (Link to worklog soon.)

IMPORTANT MESSAGE: I apologise for the loss of the images linked. Without warning Photobucket are now asking for $399.00 USD to restore the picture links. Please bear with me while I make other arrangements to host the pictures. US NAVY HELSEACOMBATRON FIFTEEN HSC-15 'Red Lions' UH-1H Skins for DCS World. Created by BrassEm 2015. Additional Textures by Home Fries. These skins are an interpretation of the modern paint scheme of the MH-60S as operated by the US Navy Squadron HSC-15 Red Lions. HSC-15_Red_Lions.zip Airframes; 611 Serial 168531 612 Serial 168532 614 Serial 168536 616 Serial 168538 617 Serial 168539 BLANK NAVY The structure of the ZIP is; 6 Directories containing the required files. HSC-15 Red Lions 611 HSC-15 Red Lions 612 HSC-15 Red Lions 614 HSC-15 Red Lions 616 HSC-15 Red Lions 617 HSC-15 Red Lions Blank To install unzip the download file and copy these directories to your DCS BAZAR directory. (I.E. For non-steam.) C:\Program Files\Eagle Dynamics\DCS World\Bazar\Liveries\uh-1h MAKE SURE YOU DO NOT HAVE THE ZIP FILE IN THIS DIRECTORY OR ELSE YOU WONT SEE ANY LIVERIES! NOTES; Reference websites; https://www.facebook.com/HS15RedLions http://www.seaforces.org/usnair/HSC/Helicopter-Sea-Combat-Squadron-15.htm https://www.dvidshub.net/ http://everyspec.com/ http://encycolorpedia.com/ Based on MIL-STD-2161B(AS) APPENDIX B Figures D-2, D-14. FED-35237 FED-36320 FED-36495 The FED colours appear too light compared to published photos. Also depending on light conditions the grey tends to reflect the surrounding blue more. No disrespect is intended for not applying the appropriate crew labeling, including the golden wrench. It is just to keep the paint schemes more generic. The shoulder patch is improvised due to texture limitations. Airframes are based on what reference was available for interpretation at the time of making these files. While it would be brilliant to have a full MH-60S in game, the Huey is very welcome and fun to fly. Special thanks to Home Fries for allowing others to utilise his excellent textures. These were obtained from the DCS website http://www.digitalcombatsimulator.com/en/files/646161/ Texture files used directly; pilot_uh1_01_Des_USMC.dds uh_1_blade_nomark.dds uh1_weapon_grey.dds (renamed to the default filename.) Texture files modified to suit this scheme. pilot_uh1_02_Des_USMC.dds - No disrespect intended. pilot_uh1_patch_1_usmc_des.dds At this time I cannot modify the Gunners Arm patches or the weapon colours. When it is possible I will undate the files. ALSO; Many thanks to Eagle Dynamics, and everyone involved with supporting this brilliant combat sim.

My startup is TrackIR, HUD, TeamSpeak, Helios, DC World (usually). I Will have to make note of sequences and effects. A full reboot gets the startup working again.

If you ever get this problem sorted would you let the forum know please Deeplodokus. (I never touch the ingame assignments if I can help it, and prefer to use the controller to issue the correct command to the game command defaults. Once the profile is loaded into the controller I shut down the programming app.)

That would be a great help with these other references.

The switch is not straight forward as there is resistance between BOTH on/off as measured with a FLUKE. And are not commoned like most 4 way switches. I will be posting a mod for the X-55 in a new thread which works for me. It works reliably as a directional switch but not as the proportional mouse of course. (Should take a week or two to get the photos on the steps involved. Applying the mod to a new unit from scratch.) MADCATZ only scratched the surface on the capabilities of the chip they used for this controller. :doh:

You might want to check out DCS-BIOS to start delving into accessing UDP traffic. http://forums.eagle.ru/showthread.php?t=136570. And THIS! -> http://forums.eagle.ru/showthread.php?t=122577

I saw the technique applied to F-18 simulators a long time ago in the late 1980's using pneumatics. Not until I saw your posts did I realise its full impact, only being aware of full motion simulators. Being very limited for space this is very very do-able, especially with the current state of electronics. Thank you for sharing this information and letting others gain this experience.

...

I didn't photolog this mod - wasn't sure whether it would work - and it does. But I have all the details. If you can solder some wires together then it is very straight forward. Disassembly and reassembly can be a bit tricky though and there are some things to watch out for. At least the damn thing works reliably now as a 4 way switch! Stand by while I revisit this and I will post a thread in this section. Give us a couple of weeks to re-order the parts and do the build log. I don't regret buying it but disappointed at the build quality like you mention.

I have found that; Silicone grease is definitely required for all slides on the joystick tension mechanism and the red spring. (Teflon grease is better). Takes some getting use to it on the detent and no proportional tension. Throttle tension still tight even at lowest friction setting. (This needs to be revisited). Programming a profile is tedious between modes. Setting up a switch is fine but no two stage. Profile printouts primitive. Mouse stick on the throttle is useless. Inconsistent U/L/R and no Down, even after adjusting trigger thresholds. This was on two different units. Ended up moding it myself by replacing the carbon switch with a 4 way tactile switch (Voiding warranty to get it to work as it should have out the box). Other than that in my opinion it is okay.

Thank you! I can appreciate the effort involved (Photoshop?). I hope that you will progress this work further. It makes it so much better to fly this great aircraft. So many labels though!

Excellent! Two happy MiG-21 Pilots :thumbup:

G'day BigBadVuk, I did a "repair" on DCS World. (Located under Eagle Dynamics on the Windows Start button. It still would not boot. I downloaded the latest MiG21BIS install file on this website. Then installed the module with "Administrator" privileges. (This writes the files back over a "fresh" repaired DCS World.) When it boots up, don't forget to enable the MiG-21 module to get the missions enabled. Let us know how you get on. Cheers, .

[RESOLVED] G'day, Downloaded and installed the new 1.2.15 version of the install files for the MiG-21BIS. This appears to have resolved the problem file references and DCS World Booted! :) It appears as though the uninstall module routine for the MiG-21BIS left some references that the repair didn't pick up on. I am not going to uninstall the module again for testing purposes now that I got it back. Cheers, .

G'day, Installed 1.2.15 on Saturday for VFA-113 Stingers Combined Arms online mission. Unchecked the MiG-21BIS module prior to install due to STARFORCE change. Installed and Combined Arms worked no problems. Restart next day, tick the MiG-21BIS module. Flew the SU-33, SU-27, MiG-15BIS no problems but got this when I started up the MiG-21BIS in Mission Editor. Maybe I should have uninstalled the MiG-21BIS first before the update? Okay so uninstalled the Mig21 via the module manager in DCS and I will re-install it next boot up. Restart DCS but nothing happens??? NADA. ZILTCH. :( Ran Repair several time without change. Run DCS and don't even get to the very first screen... Log file reports error; 00000.956 UNKNOWN main: GUI Error: [string "./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua"]:1: attempt to index global 'LockOn_Options' (a nil value) Do not know how I will fare as I have all the current modules installed. (Except for the uninstalled 21 and do not own C-101) This is not a steam install either. === Log opened UTC 2015-03-03 05:15:03 00000.000 INFO EDCORE: createSerialQueue IOQueue 00000.002 INFO VFS: Using 'Saved Games': "C:\Users\Dave\Saved Games" 00000.063 UNKNOWN main: locale: en EN 00000.211 UNKNOWN main: me_db_api creation started 00000.889 UNKNOWN main: MOD loading: ./CoreMods/aircraft/C-101/entry.lua 00000.891 UNKNOWN main: MOD loading: ./CoreMods/aircraft/C-101/C-101.lua 00000.892 UNKNOWN main: MOD loading: ./CoreMods/aircraft/C-101/Views.lua 00000.893 UNKNOWN main: MOD loading: ./CoreMods/aircraft/F-86/entry.lua 00000.895 UNKNOWN main: MOD loading: ./CoreMods/aircraft/F-86/F-86.lua 00000.896 UNKNOWN main: MOD loading: ./CoreMods/aircraft/F-86/Views.lua 00000.898 UNKNOWN main: MOD loading: ./CoreMods/aircraft/MiG-15bis/entry.lua 00000.908 UNKNOWN main: MOD loading: ./CoreMods/aircraft/MiG-15bis/MiG-15bis.lua 00000.909 UNKNOWN main: MOD loading: ./CoreMods/aircraft/MiG-21BIS/entry.lua 00000.911 UNKNOWN main: MOD loading: ./CoreMods/aircraft/MiG-21BIS/Entry/Aw 00000.913 UNKNOWN main: MOD loading: ./CoreMods/aircraft/MiG-21BIS/Entry/Am 00000.915 UNKNOWN main: MOD loading: ./CoreMods/aircraft/MQ-9 Reaper/entry.lua 00000.916 UNKNOWN main: MOD loading: ./CoreMods/WWII Units/entry.lua 00000.919 UNKNOWN main: MOD loading: ./CoreMods/WWII Units/Weapons.lua 00000.921 UNKNOWN main: MOD loading: ./CoreMods/WWII Units/FW-190D9.lua 00000.922 UNKNOWN main: MOD loading: ./CoreMods/WWII Units/Views.lua 00000.925 UNKNOWN main: MOD loading: ./CoreMods/WWII Units/Bf-109K-4.lua 00000.925 UNKNOWN main: MOD loading: ./CoreMods/WWII Units/Views.lua 00000.926 UNKNOWN main: MOD loading: ./mods/tech/CombinedArms/entry.lua 00000.927 UNKNOWN main: MOD loading: ./mods/aircraft/A-10C/entry.lua 00000.929 UNKNOWN main: MOD loading: ./mods/aircraft/Bf-109K-4/entry.lua 00000.930 UNKNOWN main: MOD loading: ./mods/aircraft/Bf-109K-4/Views.lua 00000.931 UNKNOWN main: MOD loading: ./mods/aircraft/F-86/entry.lua 00000.932 UNKNOWN main: MOD loading: ./mods/aircraft/F-86/FM/config.lua 00000.934 UNKNOWN main: MOD loading: ./mods/aircraft/Flaming Cliffs/entry.lua 00000.935 UNKNOWN main: MOD loading: ./mods/aircraft/Flaming Cliffs/FM/F15/config.lua 00000.937 UNKNOWN main: MOD loading: ./mods/aircraft/FW-190D9/entry.lua 00000.938 UNKNOWN main: MOD loading: ./mods/aircraft/FW-190D9/Views.lua 00000.939 UNKNOWN main: MOD loading: ./mods/aircraft/Ka-50/entry.lua 00000.948 UNKNOWN main: MOD loading: ./mods/aircraft/Mi-8MTV2/entry.lua 00000.950 UNKNOWN main: MOD loading: ./mods/aircraft/Mi-8MTV2/Views.lua 00000.952 UNKNOWN main: MOD loading: ./mods/aircraft/MiG-15bis/entry.lua 00000.953 UNKNOWN main: MOD loading: ./mods/aircraft/MiG-15bis/FM/config.lua 00000.954 UNKNOWN main: MOD loading: ./mods/aircraft/MiG-15bis/Views.lua 00000.956 UNKNOWN main: MOD loading: ./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua 00000.956 UNKNOWN main: GUI Error: [string "./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua"]:1: attempt to index global 'LockOn_Options' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua"]:1: in main chunk (tail call): ? [string "Scripts/Database/db_mods.lua"]:853: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:1012: in main chunk [C]: in function 'dofile' [string "./Scripts/Database/db_main.lua"]:211: in main chunk [C]: in function 'dofile' [string ".\MissionEditor\modules\me_db_api.lua"]:277: in function 'create' [string ".\MissionEditor\MissionEditor.lua"]:202: in function 'loadDatabase' [string ".\MissionEditor\MissionEditor.lua"]:342: in main chunk stack traceback: [C]: ? [string "./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua"]:1: in main chunk (tail call): ? [string "Scripts/Database/db_mods.lua"]:853: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:1012: in main chunk [C]: in function 'dofile' [string "./Scripts/Database/db_main.lua"]:211: in main chunk [C]: in function 'dofile' [string ".\MissionEditor\modules\me_db_api.lua"]:277: in function 'create' [string ".\MissionEditor\MissionEditor.lua"]:202: in function 'loadDatabase' [string ".\MissionEditor\MissionEditor.lua"]:342: in main chunk 00000.956 ALERT LUACOMMON: Error: GUI Error: [string "./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua"]:1: attempt to index global 'LockOn_Options' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./mods/aircraft/MiG-21BIS/Cockpit/KNEEBOARD/indicator/CONTENT_orig/sample_page_with_text.lua"]:1: in main chunk (tail call): ? [string "Scripts/Database/db_mods.lua"]:853: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:847: in function 'scan_path' [string "Scripts/Database/db_mods.lua"]:1012: in main chunk [C]: in function 'dofile' [string "./Scripts/Database/db_main.lua"]:211: in main chunk [C]: in function 'dofile' [string ".\MissionEditor\modules\me_db_api.lua"]:277: in function 'create' [string ".\MissionEditor\MissionEditor.lua"]:202: in function 'loadDatabase' [string ".\MissionEditor\MissionEditor.lua"]:342: in main chunk === Log closed. Help please. .