kablamoman

Perhaps bug fixes and updates to mustangs in general could be financed by a new B/C module? A new Mustang B/C module would be worth the purchase for existing owners and new ones alike, while the work done on it or covered by the team's scope could cross over and cover much of the existing D module, making the old module attractive to new users and bringing it up to standard for the current owners.

It passes IC. The shield is green. I used it on SoW all the time. Perhaps important is which directory it's installed in: I think it has to be the windows user profile "saved games" folder as described above.

Negative. It works fine in MP and passes Integrity Check.

clean_canopy_v6.1.zip Extract contents to the following folder: %USERPROFILE%\Saved Games\DCS\ Should cover all the warbirds.

For me personally, I've reassessed the time I am willing to spend with the sim since SoW closed up shop. It's not helped that I don't find combat in the cold war, nor the more modern jets compelling enough to put up with general VR performance problems and the many bugs.

Hey guys, on this topic -- I actually like that the NWS doesn't bring up the comms menu. It's better for use with SRS. Idealy there would be an option to enable/disable this behavior for both PTT switches in the module. Razbam's M2000C has the option for this in the special options section (disable PTT bringing up comms menu) and it's a godsend when using SRS with the in-game PTT binds. I would like to request that this feature be made standard across all modules.

Don’t think there is a key bind for the radio PTT switch on the throttle, either.

I think it's a bit more likely the cockpit in the F86 is just roomier. If you have your IPD set properly in an Index (with the index, you use the physical slider), it not only adjusts the physical space between the lenses, but it passes that value onto Steam VR, which in turn passes it on to DCS so it can set the proper world scale. The option in the DCS game options is just a manual override, but lets you adjust distance between the in-game "eyes" without moving the actual physical alignment of the lenses, which has the effect of letting you hack the world scale. Feel free to correct me if I'm wrong about any of this. Probably the best course of action is to accurately measure your IPD (it's pretty easy using a mirror and a ruler), make sure the IPD slider on your headset (or the software setting, if you use an oculus device without physical adjustment) is set correctly, and then make sure the in-game option is not checked so the game uses the Steam VR or oculus value. If that's all set properly and a cockpit isn't to scale, it would be an issue with the cockpit not having been modeled to the correct dimensions, which I find hard to believe given the exacting nature of the sim and the full fidelity modules.

Looking for this, too. It seems you can actually click on the switch with your mouse (button on the throttle), but I can't find the actual binding to assign it to a button.

@grafspee Yep. Brutal.

Can't agree with you here, sorry. More WW2 assets would be great, for sure. But you can do as much or as little planning as you want and there's still plenty of fun to be had whether focusing on air-to-air, bomber interception or escort, airfield raids, or ground attack at the numerous objectives. In the last few months they've added trains that can be strafed and AI C47 and Mossie flights you can find and destroy if you're looking for them. They do quite well with creating an immersive and fun environment with lots of communication with the SRS integration including lots of human GCI participation. I think they've been regularly setting new records for their highest player participation each month. Many squads are active on the server as well.

You should check out the Storm of War server. They do amazingly with the limited assets currently available in DCS, and completely contradict your "lost cause" outlook.

Yeah it's not working at the moment but they are overhauling the bomb fuzing in the sim, so hopefully it'll be fixed and ready to go in the near future.

In the 47 there's a ram air effect that heavily impacts your manifold pressure, independent of your throttle position. So if you set it when you're going fast, but then slow down (ie. bleed energy in a climb or turn), you'll end up with less ram air/less manifold pressure and vice versa. Also, if you're running with the throttle and boost levers interconnected, you probably will get an even less linear relationship between manifold and your throttle position as the turbo spools up and down. Long story short, it's more of a handful. You can try splitting your boost and throttle levers and using them independently (the boost portion will still lag a bit in response), but you'll always have to watch the changes due to ram air with your speed.

I'm not sure where exactly you're getting the numbers, but it's been a well-known issue that the hit-to-kill counts are nowhere near accurate since the SoW admins updated the stat tracking to include those stats again. They can only scrape the logs for the info and DCS seems to have a problem logging individual shots/hits with the rapid fire WW2 air-to-air weapons.

I suspect that’s exactly what it’s for.

Hey sorry for the late reply, friend. As others mentioned this is just a windows issue — looks like you need administrator rights to edit the file. If you’re not sure how to run notepad as admin, you could try saving a copy of the file to your desktop, make the change and save, then try copying/dragging it back to the folder — hopefully you’d get a prompt for admin approval to overwrite the original file and can simply click to allow it. Good luck.

For what it's worth, I haven't had to re-edit for at least the last 4 open beta releases.

Not sure if you're aware but if you bind it directly to a key without fixing the lua problem the lever in the cockpit will move, but you won't get the actual system changes (ie. no ram air boost). The proper way to fix it is to simply change 2 single digit numbers in the lua, then you can properly bind it to a key or button and get the proper response. Here is the fix: Open the file: \Mods\aircraft\P-51D\Cockpit\Scripts\clickabledata.lua Search for the following lines: elements["pnt_134"] = default_movable_axis(_("Carburetor Cold Air Control"),devices.ENGINE_SYSTEM, device_commands.Button_8, 134, 0.1 ) elements["pnt_135"] = default_movable_axis(_("Carburetor Warm Air Control"),devices.ENGINE_SYSTEM, device_commands.Button_28, 135, 0.1 ) Change the underlined variable to the following and then save the file: device_commands.Button_7 device_commands.Button_27 It is literally as simple as changing an 8 to a 7 (two instances). @NineLine can we get this one pushed through, already??

I've taken the jug out a few times on SoW and it's the one engine I can't get to behave reliably (and I fly the Dora pretty regularly, so that's saying something). I've often experienced the same failure mode (loss of power, engine oil temp rising) after an hour or so of flying, often with a reduction of power -- it's especially frustrating when you successfully RTB after a long sortie only to have it roll back on you in the pattern. I've checked and double checked and as far as I can tell I'm not exceeding any limits, and as a rule any changes to prop, throttle or boost controls are done very gingerly. Open to any suggestions as I'd like to fly it more, but it's just way too fragile to use online as far as I can tell.

There is a well-know, but separate bug with the Dora engine where if you run it at ~2700 RPM failures will occur, seemingly at random. To prevent this, it is suggested you just run it at 3000 RPM for cruise, and if you need economy, pull it all the way back to 2400 RPM. For emergency you can of course still firewall it. I've not had any issue with random failures this way, and anecdotally I'd also add, try to make smooth adjustments (don't slam the power lever back and forth).

Fair enough — I only ever really fly it on Storm of War (No MW50) — so my experience may be limited by that. I think in principle it should behave the same, though. I have heard about it potentially not auto regulating properly if you touch the control (perhaps some kind of bug), so I am a bit curious: Have you experimented with not touching it at all, from start-up to cruise, and then boosting? I am not at home right now or I’d give it a try myself, but I wonder if you can get the full 10 minutes with no problem if you try that. Also important not to be doing that at low speed (ie. a steep climb) or it will overheat for sure.

Yikes… Looks like a lot of arguing over nothing in here. I don’t know if people read the original post (looks like a few were merged) but the whole point of it was to have hard limits as an option for those that want it and soft limits still available for those that didn’t (and no limits at all as an option on servers that allow it or offline). In my mind, nothing is taken away from anybody in that scenario. Nobody would be forced to get sick. Again, for the record, I am a VR user advocating for this.

That’s the thing though, the rad flaps open themselves. The rad control in the Dora is totally automatic. The knob is just a control that sets the thermostat temp, and by default it will actuate the doors to regulate around 100° if I remember right. If you “open” the rad you’re actually just resetting a lower temp for it to maintain so you will just be flying around with more drag than you need (it will try to regulate at like 70° Instead, as an example, and so open the doors needlessly). keep it at the default and the doors actuate themselves. If you start to overheat the doors will already be fully open — you need to increase your airspeed and/or reduce power to cool down your temps.

Hey didn't want to derail your thread, as I agree more binding options are always better! But as an aside I would recommend not touching that particular control at all -- you really don't need to. But yes, an axis bind would be nice!