ishtmail

I assume Wags (and Nate) does not write something on a public forum which wouldn't already be agreed upon within ED. So, if Wags writes that prepurchasers will get Nevada for free, I assume this is an official ED opinion on this matter. It would be quite problematic for ED's public relations, maybe even devastating for ED's reputation, if an official team member would give public promises which ED does not intend to keep.

Maybe. But this complicates things: DCS World remembers controller settings for each aircraft individually, so basically, once you have your controls set for different aircraft, you don't have to think about it: just select the aircraft and fly. If you set your controls in Target, you have to do it for each aircraft separately. And then you have to run the proper profile, depending on the plane you want to fly. And if you switch to a different airplane, you have to go to Target and load the proper profile again. And you have to do this EACH time you run DCS World, and EACH time you switch a plane. Since DCS does this automatically, it just seems like a hassle to use an additional external program for something DCS already does well enough.

Memphis, you keep rambling that Nevada was NOT a pre-purchase feature. Nate, a member of ED testing team, clearly stated the opposite. You keep saying that prepurchasers are NOT entitled to a free Nevada map. Nate said that prepurchasers WILL get a free Nevada map. And Nate posted this yesterday. THAT.

I would hope that they already ARE doing their work and thoroughly ignoring these bickerings. And anyway, Nate already explained the situation (and on the previous page, nonetheless): So, Memphis, ED will release Nevada for pre-purchasers for free, and payable for the rest of us.

For me, this flashing occurs when loading the flight. Usually, if I see desktop flashes, this means the mouse doesn't work in DCS either, and I am forced to switch windows (alt+tab), and then click on the DCS World running program to maximise it again. After that, the mouse works AND no more desktop flashes. It would appear that DCS World application, when it loads, does not go 'to the front' of the desktop completely. It does maximise so that you only see the program (and not the taskbar, for instance), but sometimes if I move the mouse down to the bottom part of the screen, the cursor changes shape to the vertical 2-arrow cursor, as if I pointet the cursor over the edge of the Taskbar and the mouse would let me resize it. Basically, DCS World does not go to the front of the desktop, to be the application 'on top', even though you see it on top.

This I would also like to see very much. It's been quite a process to assign a sensible profile for P51D, to my Warthog joystick - lots of going in game and exiting to make controls changes were necessary, and it would considerably speed up the process of optimizing your controls, if you could change them while in game...

jjohnson241: use the solution described on the previous page. Download the .lua file, unzip it in the proper folder, problem solved. Ofcourse, I expect ED will fix this so we don't have to do stuff like this in the future. But for now, a solution is available.

ophiuchus: Your installation had these options available. Our istallation didn't. We didn't even see the P51D tab in the 'special' section. The problem was the missing optionsData.lua file, which you had in your folder, while we didn't. You kindly posted your file and solved all our problems :)

Yes, this fixes it. Thanks! Tutorial: Download the Optionsdata.zip that ophiuchus attached above. Unzip the file into your DCS World/Mods/Aircraft/P51D/Options folder. Done, the P51D tab is back and you can set those options as you see fit.

Instead of using the Autoupdate option (which pops up when you launch DCS World), use the updater (shortcut found in your Start menu under Eagle Dynamics/DCS World/Update DCS World). I also had problems with a very slow updating process via the auto-updater, which I eventually cancelled. Running the updater separately was much faster and worked with no problems whatsoever.

I made a clean install about 2 weeks ago (version 1.2.1), and yesterday updated (with the updater program) from 1.2.1 to 1.2.2 and all the options (including auto rudder) are there and available to turn on or off. And I should note that the Auto rudder option is ON by default (for example, when you make a clean install), so if you want to play full realism, you'll want to turn it off first. EDIT: I went and checked to see what's going on, so here's the jiff: I updated to 1.2.2, and the auto-rudder option WAS there. I know, because I checked AND set that option properly. I then purchased and installed FC3, AFTER I updated DCS World to 1.2.2. And now, these options seem to be indeed gone. Is it possible that FC3 somehow affected this?

What about separate wheel brakes for left and right wheel, respectively, applied to axes on controllers (for instance toe brakes on Saitek Pro Flight Combat pedals)? Probably not high on the priority list, but I've grown accustomed to toe brakes in A10C and I miss the feature when flying (or rather, taxiing) F15.

It depends on the DCS World version you're running. Version 1.2.1 has an auto updater, which also updates all modules with ease and no hassle whatsoever. I don't think all early versions had this feature.

Sorry, it took me a while to find where the dcs.log file is being held. In the attachment is dcs.log (made as per instructions - multiplayer) and dcs.log.old (from last night - singleplayer; maybe there's other irrelevant data in there). Logs.zip

Ah, I didn't know Nevada was a planned feature for A10C during preorders. I should read up on the DCS history, I suppose. That case, yes, it's logical that A10C preorders get Nevada for free. I am in any case prepared to pay for this addon, as I'm sure it'll be fantastic.

Confirmed that this happens in Single player as well. I don't (currently) play online, and have noticed long load times every time I launch a single player mission (any airplane, any mission - training, instant action...).

Why then not all users that purchased ANY DCS sim in pre-purchase? Like P51D, Black Shark 2, Combined Arms or FC3? Why would only A10C prepurchasers be exclusive? But then again, pre-purchasing a game already grants you early access to beta versions, allowing you to enjoy the sim AND contribute with comments, to make the sim even better when it's officially released. So why would the Nevada map be made free for pre-purchasers only? Either make it free for anyone that bought a DCS module, or make it payable for all.

Yes, this method worked for me as well. The Updater from the DCS World shortcut stalled when downloading, so I cancelled it. I then ran the Updater from the Start menu DCS shortcuts folder, and everything updated smoothly.

Yes, it's the splash screen part that takes longer. It takes several minutes for my desktop to convert to Basic mode (it turns off Aero), which is something one would expect should happen immediately upon loading the splash screen. What MadTommy described might be the cause: the splash screen (for some reason) affects GPU clock speeds, which slows down the loading process.

HMA: thanks for that link! It worked, it appears. I now just have to be careful not to calibrate in Windows :)

Allright, let me explain my theory a bit: In Windows, when calibrating the Saitek Pro Flight Combat pedals, the toe brakes are represented as X and Y axes. Windows understands these toe brakes like a traditional Joystick. During Windows calibration, Windows asks the user to first leave the stick centered. Then it wants you to push the axes to their extremes. Last it again asks you to center the stick. Now, toe brakes DON'T have a center position. They only go from one extreme point (completely released) to the other (completely pressed). Normally, when calibrating the toe brakes, I would leave the toe brakes released when the utility asks me to 'center the stick'. This would mean that Windows would register the 'center point' of the stick (in this case left and right toe brake) at the extreme point of an axis, rather than at its center. Windows would still register the movement of the axes correctly, resulting in the Windows utility to properly display the pedals position. Moving to DCS: I'll make an assumption, that DCS software takes Windows calibration as something relevant. Let's say, it sees that Saitek pedals' toe brakes are visible to DCS like a traditional joystick (where a stick can be centered), instead of like pedals. Let's say that DCS software, in addition to the 'extreme points' of calibration, also reads the CENTER point of Windows calibration. Since the center point of the toe brakes has been calibrated to be at an axis' extreme, and since DCS 'expects' the center point to be at an axis CENTER instead, the mixup occurs. This COULD be the root of all evil, so to speak. The real solution would be Saitek: they should release Windows drivers which would put the toe brakes to SLIDERS, instead of traditional joystick axes. Sliders don't have center points, only extremes. When I originally purchased my Saitek pedals, there were no dedicated drivers, and the pedals were read by Windows like any USB joystick. Now, it would appear that Saitek released both drivers AND software for these pedals. http://www.saitek.com/uk/down/drivers.php At home, I'll try and install the new drivers, see if they make a difference.

@Wallace: I think I understand, what you did there: you set a dead zone in the middle of the axis, making the axis not respond until it is almost fully pressed. This might work, but it kind of eliminates the purpose of analog wheel brakes. In your case, you fully press the brakes and the plane responds by fully braking, but you have nothing in between: you can only fully press them or not at all... If I understood you wrong, let me know. EDIT: I see now I understood wrong. You were talking about the same thing as Heggis in FreeFall's link: you set the X-saturation to very low. FreeFall: thanks for the link... I'll try what Heggis did in the last post of that thread (saturation to 70). EDIT2: It didn't work. I set the X saturation to 70 (as suggested by Heggis), and got the same result. Then I set it to 25 (almost vertical, like Wallace suggested), but that didn't work either. EDIT3: I have an idea, but I'll have to try it later today as I'm heading for work now... I'll keep you updated if my theory turns out correct.

I'll just go and put my question in here: I got a Saitek Pro Flight Combat rudder pedals, which have wheel brakes on top of the standard rudder axis. I have them set up properly (both X and Y axes are inverted, so wheel breaks engage when I press the breaks, and disengage when I release them). In all DCS sims (A10C, P51D), the wheel brakes act funny. Once pressed, the wheel breaks engage fully. But when I release them, they only release to about half in the sims. This means they remain half-pressed in the sims, even though in reality they are fully released. I can best see this behavior if I press RCTRL+Enter, which opens the Controls axes display thing - there, I can easily see how the brakes remain half pressed (and ofcourse, the airplane itself doesn't taxi along the taxiways as it should, as it keeps braking). At first I thought this could be a calibration problem, so I calibrated the pedals in Windows. Over there, everything functions perfectly: both pedals, when released, go to their extremes in the calibration utility. Also, there is no flickering of the axis that could be understood as a symptom of the potentiometers failing - when pressing and releasing the pedals, the movement in the Windows calibration utility is smooth throughout. So, it would appear that the pedals are calibrated correctly and function perfectly. But in A10C or P51D, once I press them, they stay half pressed. The only workaround is to press the Wheel brakes key on the keyboard, which releases the brakes fully. But seriously, I didn't spend well over 100 euros on pedals with brakes, just to end up using the keyboard again, right? Any ideas?

I've just seen the Su-27 documentary on Youtube (it is in 4 38-minute parts), where it is available in decent quality, and more importantly: in its entirety. I recommend watching it, although it IS a bit propagandic in nature ;) Here's a link to part one: http://www.youtube.com/watch?v=tD5VXttYF1A

Heh, darn my quick fingers - purchase is done and done. Shadowze, thanks for your link, but you were about 10 seconds too late :) Well, purchasing directly from DCS does give me the added satisfaction of knowing the developers will get more - buying from a dealer usually means the dealer gets a sales margin cut, meaning the devs get less (depends on an individual contract, I suppose, but dealers probably don't sell without getting something in return).