fencible

Issue resolved for now. I made a 6th attempt at a repair last night, and this time it worked. The game started up after the repair was finished, and I was able to log in. So - issue solved - thank you!

ISSUE RESOLVED. I was ejected from an on-line server which detected that I had a tainted load. A Viggen texture file had become corrupted. I removed the corrupted file and ran DCS_updater.exe repair (I have followed this procedure successfully in the past). After the repair, DCS failed to come up. When I ran the run.exe nothing appears to happen. If I run the task monitor while trying to start DCS, the dcs task appears only for a few seconds before exiting. I've re-run the repair 5 times or more without success. So my beta standalone DCS (with my new Super Carrier and P-47D) is dead in the water for now. The stable version runs, of course.

The problem with delayed fusing is that there is certainly no accounting for the effects of delayed fuse bomb penetration. Bombs exploding 5 of 10 feet under the ground should have their blast radius reduced considerably - but that would be so complex to calculate. You would need to classify all the terrain on any map by how deep the soil (if any) is at any location. Same for building structures. I think that DCS does account for penetration delay on hardened targets like bunkers, but that's about it, as far as I know.

For now you can do the following on home-made scenarios: reduce the gun ammo on the JU-88s to 5% or 3% in the scenario editor. Then make dummy runs at them until they unwisely hose off all of their bullets in one very long barrel-melting burst. After that they have no guns, and only avoidance maneuvers (which they're pretty good at) to save themselves. The JU-88 was a formidable, fast aircraft for its' time.

Merci Croustie - I did check the circuit breakers and one was popped out (for the cabin lighting). I pressed it in. No other breakers were popped that I could see. That is why I mentioned the incident here. I have also seen my airspeed indicator get 'stuck' at about 230 mph after a long flight over the channel. There seem to be a few instrument issues at this time.

Just tonight since the latest patch I find that the oil temperature gauge never moves from 0 degrees. The other oil gauges appeared to work properly.

P-47D has 8x.50 cal guns, not 4. Each gun has 425 rounds - more than the P-51D.

In rebuttal to the statement that the Normandy and Channel maps are too small, I point out that they are very dense maps with enormous detail (down to tables and chairs outside French cafes, and detailed garden contents in the back yards of row houses in London). In addition to these intense details, both maps are historical ones (not modern), and the research needed to produce them would have been very exhaustive and time consuming - and that means, expensive. But with detail levels as seen on these maps, are required large computer resources. The Persian Gulf map was purposely limited in size because users' PCs couldn't handle anything larger. Finally, these WWII era maps will mostly be flown in warbirds - much slower than modern jets, so their 'small' size is less of an issue. postscript: I just bought the Channel map and the P-47D

Nick Grey said "May". So, unless they've had a set-back, I think we should see it on Friday.

I'm pretty sure it is voiced by Sheriff who does Sheriff Sim Shack videos. He speaks very clearly and succinctly. He also gives the best, most concise training instructions.

May I suggest that the WWII warbirds ARE slow by comparison to the jets we normally fly in DCS. In the Spitfire, you are cruising somewhere between 240 and 280 mph - that equals 208 to 243 knots. in a dive with power on, 400 mph = 347 knots (cruising speed for most jets), and 500 mph = 434 knots. If you fly at 208 knots in any jet, it feels slow, too. Plus, your altitude affects your perception of apparent speed. The higher you are, the slower it feels like you are traveling.

This is a general problem that I have with all the warbirds. If I fire more than about a half-second burst - the burst will continue sometimes for seconds after I have released the trigger. It looks to me like a buffer somewhere is being filled up quickly by firing impulses. It is most annoying and wastes tons of ammunition, particularly on strafing runs. Since no one else seems to have this problem, I am assuming that there is a well known solution to it. Can anyone share that with me?

I'd love to have the G6 too, but it would be vulnerable to the spit IX and P-51D. Maybe a later mark like the G10, G12, G14. It is a mid-war design. Maybe someday we will have G6, the Spit V, and P-51B or C. I think we would all love early war models too, from The 109 E, F, through early G models (The Finns would like to have the earlier Gs flown by Finland). I think the G6 would hold its' own against the P-47 at the low altitudes typically found in DCS multiplayer servers. But maybe ED does not want to steal thunder from IL-2 - the two companies are on friendly terms.

Yes, I am quite sure I entered Long before Lat. Since the distance from takeoff to the test-fire area is small, I cannot imagine that NAV drift plays much of a part in it. Still, since none of you folks seem to be having any similar problems with this, I will assume that I am doing something wrong. Thanks for your answers.

Yes, I am using the correct format and taking the coordinates from the F10 map. Has anyone else tried this method? If so, what are your results?

Since I cannot currently enter way-points on multi-servers in the usual way (via F10 map), I have been testing hand-entered way-points by taking coordinates from the map and entering them directly. After that I designate the target(s) by TAKT, press '9', press desired way-point button. I am finding that these way-points are not accurate enough for the BK-90 cluster munitions. They seem to be about 0.5 km off-target. I am entering the local atmospheric pressure for the target area, as near as I can estimate (practice targets are very near sea-level), yet still a large discrepancy. So there seem to be two issues with the current open-beta build: 1) the well established method for entering way-points in online servers is not working, and 2) hand entered way-points in the cockpit seem inaccurate or transformed.

I just can't wait for this Big Beautiful Brute to become available. It is a high-and-fast boom and zoom king, patently NOT a turn fighter, but great in the vertical. BUT it will be THE supreme ground-attack warbird in DCS - 8X.50s, rockets, bombs - huge tough radial engine, and an airframe that can take a beating and just keep on flying. Woe to the opponent who gets caught by a burst from a P-47! Watch this!

This is a most pleasant and exciting surprise!!! And what a development team - no one does flight technology better than Germans! This is going to be such an important module!! Best of luck with your work!

Get close. The guns are synchronized for 300 yard range - that's 900 feet on the range dial on the side of the K14 sight mounting. Setup your K14 gunsight to 900 feet, and don't shoot until you are that close. The K14 gunsight, (with its' gyro turned on) actually works (not for snap-shots - for stabilized tracking shots)! Set the target size to just under 35 feet for a fighter-sized target, and map the range increase/decrease functions to the HOTAS. Fit the target wing inside the circle of pips, and the lead will be correct to fire - but as I say, wait until you are at about 300 yards. Make a practice mission for yourself that has easy drone targets, and practice with the sight. You'll soon be getting good reliable hits. Practice, practice, practice.

"Maybe a thought. Is there a way how I can make it to the settings to have it as a checkbox in the mission editor? Like Mi-8MTV2 have for the extra armor? Or maybe to create extra plane/duplicate it t to have option to choose P-51D_2guns and P-51D_3guns, if it make sense?" I think not, the developer would have to compile stuff like that into the code. it would be GREAT to have that option, though.

You CAN change the gun configuration if you are willing to edit the .lua file for the P-51 mod - I have tried it, and will again now that they have just fixed the projectile dispersion modeling. Modifying the file invalidates your system from joining multiplayer servers, however, and you can only run single-player missions. File is: Edit E:\Eagle Dynamics\DCS World OpenBeta\CoreMods\WWII Units\P-51D\P-51D.lua Comment out the left outer gun and the right outer gun. Then change "count = 270" to "count = 500" for the middle guns. That does the trick. But you will not be allowed into multiplayer servers with this file, so make sure you backup the original file so you can switch back. Yep, just tried it. Works a treat!

ED has fixed up the projectile dispersion formulas and ammo loadouts on the Warbirds in the latest open beta release! Wow - the P-51 (and the Spit - still haven't tried others) is deadly - bullets go where you aim, and concentrate instead of scattering everywhere, so instead of a few ineffectual hits, the target gets clobbered. Because dispersion is now realistic instead of extreme, you can see bullet strikes 'walking' along wing surfaces, and concentrated hits when firing at convergence ranges....so realistic now....so deadly destructive! Thanks ED - what a big step forward!

Aha! Yes, thank you both - I have found he 'Stores release' cover and programmed it to my HOTAS. Thank you for your patience and help. Different terms are used by different module designers for the similar items. Other makers use the term 'Weapons Release'. 'Stores release' is a new one to me. All is now well, thanks to your help!

Thanks I'll check it out - I have one on-the-stick safety switch, which I open, but you say there are two?

I didn't hear any whistling when my small-town street got beat up by an F4U a few summers ago. It sure was LOUD though! I heard a vicious snarling, roaring aircraft engine and ran up from the basement to to my front yard. There was a fully restored F4U from the warbirds museum in Ottawa doing low passes over the house 3 doors down. That's where one of the volunteer mechanics who worked on the restoring the plane lives (he did the massive carburetor). This was a salute to him for his work, apparently. What a wild sound - but no whistling. Maybe if the throttle had been backed off, but not with the throttle on full roar!