Bahger

Excellent! Thanks. It's a drag to spend ten minutes learning what you already know, only to have the mission cut out before you learn what you don't. They are excellent training missions.

I swear by CH products, too, but because I do a lot of sim racing, I have a G27 wheel and pedal set installed. I'm happy to report that DCS recognizes these pedals, and, as long as "Report Combined Pedals" is checked in the Logitech Profiler, they work very well in all DCS flight sim products.

I'm wondering if this useful function made it across into DCSW for both A-10C and FC3. I have no idea if it was ever implented in the FC series but I found it useful in A-10C. My HOTAS mapping for it no longer works. Has it been eliminated or maybe the key combo changed? Many thanks.

In both the unguided bombing and navigation training missions, the voiceover just cuts out and the mission guidance ends. I know the triggers can be fussy and require flying within fairly exact parameters but this is just a refresher course for me and I always fly the airplace pretty precisely as instructed. Has anyone else experienced this? Might there be problems with training missions in DCSW? All input appreciated, thanks.

Does Tacview work as well with FC3 as with A-10C?

This worked for me. Thanks d.b

Well, I deleted my config files and re-set the controllers but I can't stand to delete all those missions, so I put them in their own file within the sim's mission tree.

I have a CH HOTAS which always worked like a dream with A-10C pre-DCSW; I had an elaborate multi-function map that I activated via the CH Control Manager software. In DCSW the controller interface seems to see the CH devices and even reconises throttle input, for example, but in the airplanes (A-10C, FC3 F-15E)...nothing. Can anyone advise? EDIT: NVM, fixed it...I think.

Mods, I know you'll move this thread but I'm posting it here as this is where people go first and both customers and devs need to be aware of the issue. I also realise that it's quite well-known; I'm just contributing my own experiences, which are not very good so far, while running DCSW/FC3: - When in 3-D flight mode, DCSW is not always "on top" of other Windows applications, i.e, the sidebar and other desktop objects show through, flickering, and interfere with both controls and graphics. - Other posts about this do not resolve whether switching from Windows Aero display mode fixes these problems. For some it appears to, for others it does not. - Similarly, I do not know if playing the sim in a windowed mode (how?) helps. Some say it does, more say it does not. - It is impossible to exit 3-D mode via the "Exit" command in the menu. This is vexing. The only way I can get out into the 2-D program and then exit to desktop is via an unpredictable combination of ALT-TAB and/or CNTL-ALT-DEL. I don't yet know if these issues apply to non-Beta modules I have installed in DCSW, i.e. A-10. Either way, this is a really serious performance glitch. If it applies to A-10, it's a large step in the wrong direction, performance-wise. If it only aplies to FC3, ok, it's Beta but I think we should be informed re. whether a fix is on the way. This is a serious issue.

Hey Sarge, thanks for your helpful advice. I'm very glad you liked my missions...hopefully there will be more where they came from. I did copy over my control configuration just because it's a PITA to do it from scratch with my complex controller setup (CH stick and throttle, G27 pedals). If it does not work I'll delete the file and start from scratch but I suspect the axis controls at least will carry over. Hmm, after getting DCSW up and running and verifying that both the A-10C module and my newly aquired FC3 Beta were installed and working in DCSW, I simply uninstalled DCS A-10C (once I had copied over all my user data, such as missions, etc.) What did I need to do to deactivate? Your advice re. the possibility of missions not playing out properly because of large changes post-DCSW is well taken. Because the sim allows a folder tree system for missions, I think I will create a folder called "Old" for my pre-DCSW missions so that I can separate them from any missions I create in the new install. It took me all afternoon to get FC3 to install -- it's a long story -- but it will be worth it because I will now be able to create missions that can be flown in either an A-10C or an FC3 F-15E. Cool, huh? Thanks again for your interest and helpful response.

I did it... I think. Went into regedit and followed C0ff's instructions very carefully. However, because I rolled back the DCSW install and cannot get it to update, I will need to uninstall DCSW and reinstall yet again in order to get the most updated version that will accept FC3. Here goes. EDIT: Yes! First time I've messed with regedit and lived to tell the tale. Now all I have to do is install the F-15 training missions and set up a CH profile for the eagle. Thanks for your help, guys and I hope this thread will be useful for others who have this problem, i.e. a LOMAC install that does not create registry entries, thereby preventing FC3 from installing. GGtharos: I owe you a beer. Kunz too.

Ah! That registry solution looks promising. I'm afraid I do not have the technical know-how to follow c0ff's directions though, sorry. I always back up my registry but I do not know how to make these changes. Re autoupdater, it's stuck at the reverted version, which I accomplished via a batch file supplied on these boards. I'm not sure how to reverse this, as it does not update automatically, nor when I run the update executable inside the install folder. Thanks again, I know I'll get all this sorted somehow.

Thanks, GGTharos, you've always been great and I appreciate you dropping by. I've been looking forward to flying the enhanced Eagle in DCSW and to designing many missions in which both the A-10C and the F-15E are flyable. That's why I spent the $40 on FC3 and the $10 on LOCKON. It'll be worth every penny once we get it worked out; thanks again.

How does the autoupdate work? I've reverted to an earlier version of DCSW, hoping to solve my problem -- it didn't -- and now I run dcs_updater.exe but it does not appear to be updating DCSW. I know this is not ED's fault -- because of LOMAC being a Ubisoft IP -- but I have not had to do a useless dance like this with any PC software in a long while. I'll need to get my money back for FC3 if ED cannot help me.

You may be right. Any solutions or workarounds? I'm currently reverting DCSW back to a previous version although I do not have much faith in that strategy as my problem occurs before DCSW even gets involved...

Hobo, I can run LOMAC but registration fails when the ancient registration utility tells me I'm not connected to the Internet (although obviously I am...) Win Vista 64x. I just uninstalled and reinstalled LOMAC/DCSW in the opposite order and FC3 still won't reciognise LOMAC. I'm not happy.

I know that. But FC3 won't see it. I'm now uninstalling and installing LOMAC and DCSW in the opposite order, i.e. LOMAC first.

When I try to run the registration program it ultimately tell me I'm not connected to the Internet. Grr. I might be able to find my old LOMAC disk; would that help?

Updated DCSW to 1.2.2.7570, still no luck with getting the FC3 installer to see Lockon. This is galling. I've spent hours trying to get this to work and have even re-bought a product I have no intention to use in order to do so. Can anyone help me?

I installed DCSW then LOMAC (bought as a download specifically for this purpose, i.e. to get FC3 installed in DCSW). Was I supposed to install DCSW and Lockon in the opposite order (i.e. Lockon first)? When I try to run the FC3 installer I get an error message saying I need to have Lockon 1.0 "installed and activated"; it is, I can even start it up and play it. This is frustrating. Help appreciated.

I'm making the transition. I'd like to transfer all my own missions made in the DCS A-10 ME plus any other useful user data like control configurations, etc. The source folder is /Saved Games/DCS Warthog The Target folder is /Saved Games/DCS I'm going to uninstall DCS A-10 after I transfer all this data from one folder to the corresponding folder. Can anyone advise re. which data I really need to send across and whether it will then be safe to do a Windows uninstall on DCS A-10? I need the HD space and do not want redundant installs. Thanks!

Hmm, ok, so that bit of trigger scripting -- pretty simple, as you say -- is, as I understand it, unavoidable if you want the player to be able to choose between two client flights and you want the flight mission not chosen to function under AI. The only alternative (SP only) is to avoid the "Client" designation entirely and make two versions of the same mission but with "player" flight adjusted. The former option is obviously more elegant.

Thanks, Grimes. How about SP mission making? Is it possible to make an SP mission, as described above, and to give the player -- or the mission designer, when testing it -- the option to choose whether to fly an F-15C or an A-10C? I'm assuming that, because the "client" system" does not apply to SP mission design, this would work as long as the player has all the right modules and the mission designer has designated these flights as "Player". I still can't figure out the all-important question of what happens to the other flight once the player makes his choice; it's obviously important that the AI can fly the mission for a flyable a/c or a/c group, if the player selects an alternative. In other words, it's been a while and I can't remember whether SP mission design in this sim allows more than one aircraft/flight to be designated as "Player". An alternative would of course be to copy the finished mission, rename it and simply change the "Player" flyable a/c from the Hog to the Eagle and then redesignate the other flight as AI-controlled. This alone, for me would justify the purchase of LOMAC/FC3 for use within DCS World. I think it would be really interesting to be able to fly two completely separate but interlocking missions within one scenario, in SP or MP. But in MP, as you say, the "Client" setup makes triggers necessary to get the AI to step in when client a/c are not flown by players.

I'm installing DCS World for the first time and integrating the A-10C module. I'm also about to integrate the FC3 Beta (having re-purchased and reinstalled LOMAC just to get it to work). I have a lot of experience in this sim family's mission editor. I do not know what the limits of the new modular system are, though, or its impact on mission design, so I may need to calibrate my expectations. In this regard, could someone please confirm or deny the following: With A-10C and the FC3 Beta installed within DCS World, if I go into the ME and make a scenario involving both the Hog (the C, not the LOMAC/FC A variant) and the F-15C from FC3, will that mission be flyable by the player (assuming he has all the necessary modules) in either aircraft, with the aircraft not selected flown by AI? This would be great, if true. I'd like to make scenarios containing CAS missions for the A-10C and CAP for the F-15C, with the player able to choose which role he wants to fly. Ultimately, I anticipate playing with DCS Combined Arms in the hope that the player might then acquire a third option which could be the ability to push a ground assault forward and take an objective while the AI flies the A-10C CAS mission, or to work as FAC for that CAS mission. Are these assumptions realistic, fantastical or WIP?

Thanks so much, GGTharos. I have just learned that the FC3 module comes out in February. Presumably this integrates LOMAC/FC fully with DCS World. Would it make sense to wait for this? EDIT: Oh, I see FC3 is available in beta. OK, now I'm in business.