FreeFall

XqdId2akY1A

Actually, I myself don't use snapviews (or custom snapviews) because I have touch screen + Helios (= all panels easily available). But just wanted to let you know. :)

My suggestion is that you make a backup image of your C-drive on regular basis (once a week, perhaps) onto external usb device or NAS. Your Windows just may die one day without no reason and without warning. Without backups it takes hours (days) to get your system back to what it used to be before the crash. Windows 7 and 8 are equipped with free tools to backup your system. Of course you can use 3rd party software like Acronis True Image etc. One example: I have a laptop (with Windows 7 Home Premium) and one day it just decided to commit suicide. I tried everything but almost all files had just disappeared from drive C:. There was no hardware problem or virus or anything. Windows just completely died. Fortunately, I had a fresh backup of my system partition on external usb drive. It took less than two hours to completely restore my OS partition. No tweaking or adjusting needed. I just watched a movie while the restoration of OS was running. By the way, I had two partitions and only the OS partition was messed up. The other partition was totally healthy. After restoring everything was fine again, without any tweaking with settings, updates and so on.

There is this well known issue: http://forums.eagle.ru/showthread.php?p=1650285#post1650285 Haven't tested it with v1.2.3 though.

By the way, have you used snap views? http://en.wiki.eagle.ru/wiki/Snap_views http://forums.eagle.ru/showthread.php?p=1354992#post1354992

At least with standalone versions of DCS A-10C (v.1.1.1.1 and earlier) I've seen Mavericks missing direct hits a couple of times. Every time the missile went over the target hitting the ground very close to it. However, if it was a truck or some other vehicle with weak armour, it was destroyed eventually by the blast.

Just updated to v1.2.3 and did fly a quick test mission after tweaking .luas and things. My Mavericks didn't miss the target (launched only a few of them), but somehow I got an impression that MAV cam looked a bit darker to me than earlier. Is it just my imagination, or has it been changed lately, especially with DCS:World? I've used v.1.1.1.1 for a long time and installed World version only a few dayz ago. You can of course adjust the brightness of MFCD, but anyway.

Just do things as mentioned in OP. I did, and there was no problem. Maybe the instructions might be a bit more detailed, but at least with my system (thanks to Manuel) I figured it out and everything went OK.

I think that the export folder is there, but there is no export.lua-file. Am I correct?

It should be found here: C:\Program Files\Eagle Dynamics\DCS World\Config\Export

I think he means: Open Helios Profile Editor as Administrator, add interface, choose the sim from the list. Then you must "refresh" the install path. By the way, the DCS World updater replaces your modified CDU, UHF-radio, etc. init.lua-files if you have exported them to multiple screens. You have to restore your modified files manually.

Yes they are. 30 is the left one, and 29 is the right. But as mentioned, nice charts anyway! :thumbup:

A bit off-topic, but if you don't want to have duplicate MFCDs when you export your MFCD contents to separate monitors you can do this: To get the incockpit MFCDs not to render, you can open file ViewportHandling.lua with Notepad++ and edit it (read instructions below). Depending on your A-10C version, you can find ViewportHandling.lua in Standalone versions (v1.1.1.1 and earlier): C:\Program Files\Eagle Dynamics\DCS A-10C\Scripts\Aircrafts\_Common\Cockpit\ DCS World: C:\Program Files\Eagle Dynamics\DCS World\Scripts\Aircrafts\_Common\Cockpit (I supposed that your sim is installed onto drive C: and you used the default install path.) Now comment out line 31 by adding the -- as highlighted in red below, and save. purposes = {--render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW, render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always render_target_always = true end

At least with earlier versions of sim you only got response and the permission to takeoff from tower if you were located in a certain limited area close to runway (but not yet on the actual runway). I normally stop close to the runway and after that ask for permission to takeoff while turning on the strobe lights and doing the final checks with flaps, pitot etc. And when you are landing, you have to be within approx. 5 nm from the airport to get the permission to land. Normally tower takes radio contact when you are about 6 miles away from the runway, but you cannot get the permission just yet, you have to fly on until that 5 nm left and then you get the response.

Haven't tried myself, but I think it is possible. See these instructions: http://www.gadrocsworkshop.com/node/89

Thanks, jander. Seems that at least I'm not alone with this "problem" and it is not only my system which is acting weird.

I have updated some drivers and applications to Windows 8 compatible versions, but in general I haven't had any problems with stability.

After updating my operating system from Windows 7 to Windows 8 I have had a strange phenomenon with TM HOTAS Warthog Throttle: I go to Control Panel, open Game Controllers and go to Throttle - HOTAS Warthog Properties. In Test tab (where you can see the buttons, axis an slider) nothing happens if I move my right throttle handle. If I move my left throttle handle, the Z Rotation bar moves as expected. However, both throttles work absolutely fine in DCS A-10C sim (which is the only simulator I fly). No problem at all. The right throttle just doesn't work in the Windows 8 Game Controllers test window. I have Windows 7 Pro installation on another hard drive of the same computer and there is no such problem if I start Windows 7 and go to Game Controllers. Both throttles work OK. So there is nothing wrong with hardware. In Windows 8 I have calibrated the throttle (Settings tab of Throttle - HOTAS Warthog properties), and reset to default. Funny thing is that during the calibration procedure both throttles work (move the test bar) without problem! I have uninstalled the TM HOTAS drivers and reinstalled them. Drivers are kinda old though. I checked TM website and there are no Win8 drivers. They haven't released any new versions for a long time. If any of you have updated your Windows 7 to Windows 8 and have TM HOTAS Warthog, I wonder if you could check the Windows Game Controllers Test-tab and see if both of your throttles are functioning in the Axes box. I'm just curious. Seems that this is not a hardware problem, but instead some kinda Windows 8/drivers-related one. Of course everybody suggests that you should do a fresh install. But I just installed Windows 8 on top of my old Windows 7. Haven't tried fresh install yet.

That's very true. If you have TrackIR and use trim hat as a trimmer, you should disable "middle positions" like View Up Left slow (JOY_BTN_POV1_UL), View Down Right slow etc. etc. from A-10C Sim View Controls.

I think that there is no "wobbleness" if the LED brightness is set to max. And if Target software is not installed, max. is the default? Am I correct? +1 for Paddle as a modifier as well. You are not very clever imho if you don't use it as a modifier because it's kinda waste of capabilities :). I have named my pinkie modifier as "Pinky (Paddle)" in the options. Like Sarge55, I also Zoom with Mic button. My settings are: Zoom in slow: Pinky (Paddle) + JOY_BTN4 Zoom normal: Pinky (Paddle) + JOY_BTN2 Zoom out slow: Pinky (Paddle) + JOY_BTN6 Those "JOY_-buttons" of course mean throttle mic hat actions.

You have to go to Control Panel -> Pen and Touch. There select Press and Hold, go to Settings and untick Enable press and hold for right-clicking. Now your Loz profile will work OK. :) EDIT: BTW, here you are the official Touch Screen Setup instructions: http://www.gadrocsworkshop.com/node/48

Loz SM v2.1 profile has flaps control. I haven't used that Helios switch though, because I have TM HOTAS Warthog. You could download Loz profile and take a look: http://www.gadrocsworkshop.com/node/9

With my standalone v1.1.1.1, I have a bin-folder here: C:\Program Files\Eagle Dynamics\DCS A-10C\bin I haven't installed DCS World version, so cannot say anything about it.

I think those eject handles in the cockpit cannot be operated with mouse. 3 times Ctrl + E is the only way to eject. I can confirm that:

You just need to define a new SPI. Usually with TMS Fwd Long. Then you can slave your sensors to that SPI by "long V" (= China Hat Fwd Long) Quote from the Flight Manual: You can also command SPI to Steerpoint by pressing TMS Aft Long. Totally understanding the terms SOI and SPI is very important. You need to know which sensor is active and then how to use HOTAS to control it. Just search Flight Manual for "Sensor Point of Interest" and read all the stuff :book:. It takes quite some time to learn all the HOTAS buttons and functions.