pdmarsh

I can confirm that Flightpanels and DCS-BIOS work in DCS 2.0. I haven't noticed any special demands on hardware in 2.0. Paul

I don't know if this is the source of vicx's imagery, but you can download JPEG2000 orthoimages from Earth Explorer. Look at the selections on the left in the attached screenshot. Paul

Excellent news!!! Great find. I never would have thought of that. Paul

It seem pretty clear that for some reason DCS World and DCS-BIOS are not communicating. I'm grasping at straws, but let's try this. Go into Multiplayer mode and click on "New Server" and then on "Advanced." Make sure that all of the exports are enabled--there are three. Click "OK" and close DCS altogether. Restart and retest. This really shouldn't matter for single player, but it might kick something lose. I very much doubt this next thing is the problem, but I have three versions of DCS running on my PC. Make sure DCS-BIOS and Export.lua are in the version you are testing with. Again, grasping at straws. Paul

I am a bit confused by Logitech's support page. They don't specifically call out drivers for the Saitek panels, but they do show drivers for the Saitek Flight Instrument Panels (FIPs). I would download the test software from the link below and run that. If nothing else, you can test the Radio and Multi Panels to see if they are working. This test software might install drivers as well, but I don't know. Download Page http://support.logitech.com/en_us/product/flight-sim-cockpit-radio-panel/downloads Paul

@Brk195 -- Let's make sure DCS-BIOS is in the right folder. Here is the proper folder structure: Saved Games/DCS/Scripts/DCS-BIOS (see screen shot below) Also, make sure the Export.lua file is in the "Saved Games/DCS/Scripts" folder with this line added: dofile(lfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) If all of this is correct and things still don't work, I would reinstall the Saitek drivers and try again. I know that's the standard response, but it is still worth a try. At this point, I am running out of ideas on things to check. Actually, it's worth noting one other thing. DCS-BIOS will not work in multi-player sessions unless data export is enabled by the host. If you are not in single-player mode, that could be the problem, although I have a feeling you are in single-player mode. Paul

OK, it sounds like the DCS-BIOS link between Flightpanels and DCS is not working. I'm assuming that you have the flap switch programmed as a keyboard emulator, i.e. with "G" for gear. If so, let's try to program it with the DCS-BIOS command instead and see if it works in-game. Again, right click on the field and select "Edit DCS-BIOS Control." You can use the dialog box that comes up to search for the command and program the lever. If this does not work in-game, then it will pretty much confirm it's a DCS-BIOS communication issue. Let us know how it goes. Also, if no DCS-BIOS commands are available, then DCS-BIOS is most likely not installed correctly, although it doesn't sound like that's the problem. Paul

Sadly, no. It is just a generic profile using Flightpanels as a keyboard emulator. Even if more modules were added to the DCS-BIOS inventory, Flightpanels would not get updated at this point. However, I don't believe there has been much updating of DCS-BIOS itself. Even though Logitech says that they intend to write drivers for DCS, I doubt they will go beyond keyboard emulation as well. Unless DCS and their third-party developers can standardize on command structure, it's just too much work to develop control input programs for every module. I think that's why DCS-BIOS has stalled. What's needed is something along the lines of Fly-With-Lua that is very useful in programming Saitek (Logitech) panels for X-Plane aircraft. Paul

Hi Brk195, In the interest of covering the basics, have you created and saved profiles for the specific aircraft you want to control, e.g. A-10C and/or MiG-21? Also, are you sure the profile is loading into Flight panels when you open the program? If and A-10C profile was in Flightpanels when it was last closed, that same profile should load automatically. However, this does not always happen. My newer profiles that don't use DCS-BIOS, the Viggen for example, have to be loaded manually every time. You can tell if Flightpanels is communicating with DCS by looking at the gear symbol toward the top of Flightpanels. You should be in the cockpit in DCS before checking. If the gear is spinning, the programs are communicating. Also, within Flightpanels you can see if DCS-BIOS commands are available by configuring a switch or button. I'm not at a PC where I can get more details, but right click on a button or switch field and see what programming options are available. Paul

In time, I believe Saitek, now Logitech, will support DCS. However, I don't believe they do as yet. I just checked their downloads for the radio and multi panels and DCS is not shown as supported. X-Plane is, which is relatively new. To be honest, the third party software I have been using for X-Plane is still better than what Logitech offers. I hope that in time Logitech will offer software with the same flexibility that the third party software offers. Regarding the problem Brk195 is having, the first thing I would check is the DCS-BIOS installation. Thanks, Paul

Rather than duplicate it here, below is a link to a post I made on the TacView site regarding the new ability to place texture files. It might provide some useful information. Thanks, Paul http://dogsofwarvu.com/forum/index.php/topic,5019.msg23481.html#msg23481

Some of My Wishes 1. The ability to draw polygonal or freehand trigger zones. 2. The ability to give trigger zones an altitude and to set triggers when either above or below the zone when inside the zone's defined area. 3. Already on the list, I think, but a 3D map/object editor or, at minimum, a 3D quick view while creating missions. Thanks, Paul

The new mission sounds awesome! We will look forward to it. We are working our way through all of the missions in Krasnodar Ground Attack. We tend to fly the same mission over and over until we have it down, then move on to another selection. It's a great way to design a mission.

@Apache600 -- We're getting a lot of mileage out of this mission and we're not done yet. Thanks again. Paul

Is there, or will there be, a standalone encyclopedia (pdf) that just shows WWII Asset Pack objects? Right now, even when this group is selected in Mission Editor, these objects are mixed in with all of the others in the ME encyclopedia. Thanks, Paul

Mission: Krasnodar Variable Ground Attack Module: AJS-37 Viggen Weapon: RB-15 Targets: Kuznetsov and Albatros Sortie 1: One missile hit Kuznetsov but did not sink it; other missile hit and sank Albatros. Sortie 2: Both missiles passed through Kuznetsov, which was firing on them. Missiles were destroyed after passing through ship. See image RB-15-01.jpg attached. Sortie 3: Both missiles passed through Kuznetsov, which was not firing on them. See image RB-15-02.jpg attached. All three sorties were same aircraft, i.e. not respawned, but rearmed. A flyer in another Viggen sank Kuznetsov with two RB-15s after my sortie 3 above. His flight was a second sortie after being rearmed. I only mention this as there was (is?) an issue with weapons not working after a rearm in the Viggen. DCS log file attached. I have no idea if this is a DCS issue or a Viggen/RB-15 issue. dcs-log.txt

@Apache600 -- I'm afraid that I gave you some bad information. The "lower than" altitudes for the heli rooftop missions work fine for the Huey, but not all work for the Mi-8. Apparently, aircraft altitude is based on center-of-gravity or something like that. I have now tested all three difficulty missions with both aircraft multiple times. The changes that should be made are these: Easy: 82 meters -- OK as is. Medium: 95 meters -- increase to 96 meters Hard: 119 meters -- increase to 120 meters You could go even higher to be safe, but then the trigger might fire a bit too early. I am sorry for this. I thought I had enough margin in the original numbers. Paul

This specific problem, landing at an alternate airport and nav going dark after takeoff, was resolved by entering the alternate airport code as the starting field. Thanks again.

Thanks. I have been switching to BER right after landing, and then back into NAV before taking off. I guess that is what confuses the nav system when at a different airport. Paul

I do have the nav system set to BER, but I didn't think to enter the code of the new airport. I did try re-entering the 9099 code. However, even without changing the airport code I would not expect the nav system to simply shut off. I'm guessing that as you take off, the nav system is attempting to align relative to the airport it thinks you are at, but gets a bad reading and shuts down. Is that the case? I'll try entering the new airport code and see if that resolves the issue. Thanks for pointing this out. Paul

Just backing this up. I experienced the same problem at Krasnodar Center. Paul

Another flyer and I have experienced the exact same issue at Krasnodar Center. TILS consistently brings you in at 90° to the runway heading. The green TILS indicator is on as you approach the field perpendicular to the runway and goes out as soon as you cross the runway. It appears that the coding for this field is off by 90°. Paul

In addition to having similar issues with the NAV system, I have another that could be related. When I land at a different airport from where the mission originated, rearm and take off, the NAV system goes dark immediately after takeoff. No HUD symbology--have to abort mission. The yellow Nav system warning light comes on. This problem also happens randomly, but frequently. Hope this helps. Thanks, Paul

Great idea! I hope they act on this.

@m4ti140 -- I'm glad it worked out for you. Saitek knows they have some issues with their drivers. Now that they are part of Logitech, this might get corrected. Paul