boredtechie

Hi, Welcome to SxS a new kind of DLL hell. A little background information on SxS http://en.wikipedia.org/wiki/Side-by-side_assembly Some people have reported some success with sfc (system file checker) though I've never used it myself. I typically try to work out what's wrong using ProcessMonitor from SysInternals which is now part of Microsof. Process monitor records all of the File IO actions a process is performing amongst other things. Typically you'll see the last few lines of the log shows the process is looking for a certain file in a number of different locations. It's normally this file that's either completely missing or is the wrong version. bt

Hi, Vista and Win7 may both try to protect system files from users inadvertently changing something they probably shouldn't. You can get around this by right clicking on your editor program (probably notepad) and clicking run as administrator. The version of notepad that comes up will be running with higher privileges than normal and will allow you to modify the files. Select File > Open and browse to the files listed in the original post. bt

Hi, It will need to be the RCTRL + KEYPAD0 to toggle the SnapView functionality on and off. Initially when you enable the SnapView functionality it will go to SnapView 5 (KEYPAD5) and stay there until you press another keypad key. The last view stays visible until another one is selected or the SnapView functionality is toggled off again. All key presses are momentary and do not need to be held to maintain the selected SnapView leaving you free and unhindered to interact with the chosen view. bt

Hi, You guys may find this useful too http://forums.eagle.ru/showthread.php?t=62820. bt

Hi, I've been struggling a little with the default snap views even with TIR5 it's just not comfortable for more than a glance at certain instruments. So I set about adjusting the snap views and thought I'd share both the views I'm now using and what I've learnt with regards to adjusting them. Disclaimer All data and information provided in this post is for informational purposes only. I make no representations as to accuracy, completeness, currentness, suitability, or validity of any information in this post and will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its display or use. All information is provided on an as-is basis. 1. Backup the files you're going to change .\Eagle Dynamics\DCS A-10C Beta\Config\View\View.lua .\Eagle Dynamics\DCS A-10C Beta\Config\View\SnapViews.lua No, seriously backup! 2. Enable your own custom snap views .\Eagle Dynamics\DCS A-10C Beta\Config\View\View.lua UseDefaultSnapViews = false 3. Change KEYPAD1 Snap View (Radios) .\Eagle Dynamics\DCS A-10C Beta\Config\View\SnapViews.lua Snap[11][2] = {} Snap[11][2]["y_trans"] = 0.15 Snap[11][2]["x_trans"] = 0.15 Snap[11][2]["z_trans"] = -0.5 Snap[11][2]["vAngle"] = -90 Snap[11][2]["rollAngle"] = 0 Snap[11][2]["viewAngle"] = 45 Snap[11][2]["hAngle"] = 0 RCTRL + 0, KEYPAD1 in game should now give you the radio stack. 3. Change KEYPAD2 Snap View (CDU) .\Eagle Dynamics\DCS A-10C Beta\Config\View\SnapViews.lua Snap[11][3] = {} Snap[11][3]["y_trans"] = 0.15 Snap[11][3]["x_trans"] = 0.32 Snap[11][3]["z_trans"] = 0.75 Snap[11][3]["vAngle"] = -90 Snap[11][3]["rollAngle"] = 0 Snap[11][3]["viewAngle"] = 30 Snap[11][3]["hAngle"] = 0 RCTRL + 0, KEYPAD2 in game should now give you the CDU. 4. Change KEYPAD3 Snap View (Lights) .\Eagle Dynamics\DCS A-10C Beta\Config\View\SnapViews.lua Snap[11][4] = {} Snap[11][4]["y_trans"] = 0.15 Snap[11][4]["x_trans"] = 0.15 Snap[11][4]["z_trans"] = 0.5 Snap[11][4]["vAngle"] = -90 Snap[11][4]["rollAngle"] = 0 Snap[11][4]["viewAngle"] = 45 Snap[11][4]["hAngle"] = 0 RCTRL + 0, KEYPAD3 in game should now give you the light controls 5. Change KEYPAD4 Snap View (Left MFD) .\Eagle Dynamics\DCS A-10C Beta\Config\View\SnapViews.lua Snap[11][5] = {} Snap[11][5]["y_trans"] = -0.27820714509734 Snap[11][5]["x_trans"] = 0.32762247014528 Snap[11][5]["z_trans"] = -0.24479886800933 Snap[11][5]["vAngle"] = -10.651849345676 Snap[11][5]["rollAngle"] = 0 Snap[11][5]["viewAngle"] = 35 Snap[11][5]["hAngle"] = 0 RCTRL + 0, KEYPAD4 in game should now give you the left MFD. 5. Change KEYPAD4 Snap View (Left MFD) .\Eagle Dynamics\DCS A-10C Beta\Config\View\SnapViews.lua Snap[11][7] = {} Snap[11][7]["y_trans"] = -0.27820714509734 Snap[11][7]["x_trans"] = 0.32762247014528 Snap[11][7]["z_trans"] = 0.24479886800933 Snap[11][7]["vAngle"] = -10.651849345676 Snap[11][7]["rollAngle"] = 0 Snap[11][7]["viewAngle"] = 35 Snap[11][7]["hAngle"] = 0 RCTRL + 0, KEYPAD6 in game should now give you the right MFD. 7. Tweak to your liking Snap[L][M]["N"]=O L is the plane and 11 is the id for the A10 M is the KEYPAD value + 1, so for example KEYPAD1 would be Snap[11][2], KEYPAD2 Snap[11][3] etc. N is the value you're changing where:- y_trans up(+) and down (-) z_trans right(+) and left (-) x_trans back(+) and forward(-) vAngle pan view rollAngle look left (-) and look right (+) viewAngle = field of view / zoom hAngle pan view By the way it's RCTRL + KEYPAD0 again to turn off snap view and return to your normal view. Anyway hope you find the above useful. bt

Hi, Where possible include a track... ah hell I'm starting to sound like ED :D Is it possible your TGP was looking at something else entirely slaved to STPT or something like that. I've had similar moments of WTF and found my TGP was looking at the next steerpoint because it was slaved and the flight plan was on auto. Quick checks now are is the TGP diamond on the HUD/TAD where I expect it to be and looking out the window at the TGP itself. If you're in a real rush and can see what you're after in the HUD just boresight the TGP and don't worry about where it was looking. bt

Here's another you can try if you like. EDIT: Just seen TrackIR 4 in your signature where as this profile and Wag's are for TrackIR 5, I'm not sure if that makes a difference or not in honesty. bt A10.zip

Hi Machinegun this would help with restrictive firewalls and possibly throttling depending on the ISP's policies. However I would expect it to make the latency worse rather than better due to the extra hops and encryption involved. bt

As others have said I would stick with ADSL as the latency of sattellite and the effects of weather are not fun. Could you describe your problem more specifically for example:- * I have high speeds but intermittent service * I have disconnects and an unstable profile * I have low speeds at all times * I have low speeds at peak times I've been through similar issues as yourself with broadband and know how frustrating it can be. Personally I was having random disconnects where by I would have weeks of solid connectivity and then days of terrible connectivity which resulted in my profile plummeting towards dial up speeds. I was able to resolve my issue in the end with the following steps in order of perceived effect:- 1) Disconnecting all internal cabling and connecting straight to the master socket. Often the properties internal cabling can cause problems due to bad terminations other and faulty equipment. 2) Replaced the freebie microfilters with a decent one in my case an ADSL Nation xf-1e. 3) Replaced the freebie RJ11 cable with a high quality shielded one (REIN interference was also suspected in my case). 4) Replaced my modem with a high end model Draytek 2820 originally and more recently 120 (using a linux server for routing/firewall etc). I've also heard people stating that different chipsets in different modems have more luck than others in certain areas depending on the equipment used at your exchange. This seems to be a trial and error thing so Argos and their 14 day return policy might help here (check for the exclusion key to make sure the modem you're looking at isn't excluded). If you do go down this route take care of the device and only unpack what you need to also be kind and perform a factory reset before returning it so the next person to receive it has an experience in line with the manual e.g. IP as documented and quick setup wizard to greet them. This link also has some very useful information http://adsl24.co.uk/faq/. ADSL24 give no nonsense when it comes to throttling and they've also been very helpful with issues that were nothing to do with them. Another tool you might be interested in is pathping(windows) or mtr(linux) these will show you how long it takes for a packet to reach each hop in it's journey to the remote host. Often you'll find it's a particular spot along the route that's causing a problem. For example I had a belkin router that was dropping between 25-50% of all traffic when bridging between it's switch and it's ADSL modem this caused havoc in multiplayer games. bt

Having seen the "Save Cockpit Angles" control binding in the Options > Control screen I did a quick google to find out how to use it. I came across the following thread:- http://forums.eagle.ru/showthread.php?t=52749 I realise it is for another title entirely but thought I'd mention the following issue on the off chance you're expecting it to work. Essentially if I follow the steps in the linked thread:- 1) Set "UseDefaultSnapViews = false" 2) NUM0 + Num9 3) Reposition the view port 4) RALT + Num0 then everything seems correct for that flight however subsequent flights are loaded with a solid blue screen the only things that's visible is the mouse cursor. The issue can be corrected by setting "UseDefaultSnapViews = true" again. If you require any further information don't hesitate to ask. I've not provided a track as I'm presuming in this instance it won't actually help. 1- Operating System : Windows 7 Home Premium x64 2- CPU : i5 750 3- RAM : 8GB 4- Graphics Card : Nvidia GTX 260 5- Multi-monitor use : Single Monitor Dell 2407WFP 1920x1200 bt