Talisman_VR

I agree with this and request if it is possible to increase the piston engine effects for the Spitfire and P51 because it feels very weak. Thanks in anticipation. I very much enjoy and appreciate SSA. Happy landings, Talisman

Any chance of Normandy map for WWII flying soon? Thought I read somewhere that the Normandy map would be available on this server in January 2019. Is radio channel D working for the Spitfire yet reporting enemy aircraft contacts? I ask because all we got was German broadcasts on the Spitfire radio channel D a week ago. Wanted to fly with a mate last night, but left as the map was confusing as we could not tell which airfield we had spawned in at or were the enemy airfield was either. Map was very off-putting, briefing did not help understanding and last week no Spitfire channel D working properly, so we left without taking off. Happy landings, Talisman

If only we had a map for the war in Korea and a complimentary set of aircraft, including carrier operations. Suddenly I think things could light up big time then, but DCS doesn't seem to want to be that kind of combat simulator. That's why I don't do much DCS, because it is not 'joined up' that way. I like the historic aspect of combat simulation flying, so I tend to lean more towards combat flight simulation that enables more historically based scenarios. I love the Mig-15 in DCS :) Happy landings, Talisman

Time fused bombs get 2 mentions on this historical film of the day: https://defenceoftherealm.wordpress.com/2015/02/26/hedge-hopping-in-world-war-ii/ Happy landings, Talisman

I hope we get historical low level bombing delayed action fuses for the Spitfire soon. 2nd TAF used delayed action fuses set from 0.025 seconds to 72 hours for their fighter bomber activity. If bombs were delivered low-level as opposed to a dive, 11-second delays were fitted to enable the attacking aircraft to get beyond the danger of debris when the device exploded. Source: https://www.amazon.co.uk/2nd-Tactical-Air-Force-Camouflage/dp/1906537011 It would be good to get historically accurate weaponry modelled for the Spitfire soon. Delayed action fusing is a fundamental issue for WWII bomb modelling. Happy landings, Talisman

Sincerely hope that DCS are able to provide low level bombing delayed action fuses before the Mosquito is released; officially commissioned history of the Royal Air Force specifically mentions 10 second and 30 second delayed action fuses. Happy landings, Talisman

https://www.amazon.co.uk/2nd-Tactical-Air-Force-Camouflage/dp/1906537011 Re WWII bomb delay fuses for Fighter Bombers. The above book states bomb delayed action fuses could be set from 0.025 seconds to 72 hours. If bombs were delivered low-level as opposed to a dive, 11-second delays were fitted to enable the attacking aircraft to get beyond the danger of debris when the device exploded. Also, I have a book named Royal Air Force 1939-1945 Volume III The Fight is Won, by Hilary ST. G. Saunders, which specifically states delayed fuses of 10 seconds and 30 seconds for Mosquito low level bombing missions. Low level bomb fuses are needed for the WWII aircraft that have been shown to have historically used them. Surely this needs to be sorted soon. We already have aircraft that need delayed action fuses and soon we are to get the P47 and Mosquito. The fast jet side of DCS gets all sorts of sophisticated weapons, but so far not even delayed fuses are available for WWII. We have waited many years for historical delayed action fuses. Any news on progress towards delivering historically accurate bomb delayed fuses for WWII NineLine? Thank you in anticipation. Happy landings, Talisman

P.S. Jetseat works OK in sound mode though, just press the 'mode' button on the jetseat and change the indicator light to sound mode and seat will vibrate with sounds, rather than SSA. Happy landings, Talisman

I must say that I agree very much that Torque is something that DCS has done very well and I wish other flight simulations did it as well. Happy landings, Talisman

Hi Rob, I appreciate what you are saying, but as far as I am aware, and please correct me if I am wrong, this is the only WWII server at the moment, and one needs the open beta version to play it as there is nothing going on in the release version. This alone speaks volumes I think regarding progress on the WWII front. Also, I am not sure that I have actually blamed anyone in my post, rather I think I have expressed a frustration with WWII on DCS. Frustration which I admit boiled over with this latest issue that has a negative effect on things. Anyway, trying to relax now, LOL. I sincerely hope this issue can be resolved soon. But I have to say the time taken to resolve issues tends to take a long time in DCS world. Happy landings, Talisman

Hi, I am not sure that I can say, as I don't want to break any forum rules. However, I am talking about WWII aircraft and scenarios, so you can probably work things out from there. My squad has given up on DCS WWII, but a couple of us are holding on and trying to keep faith with DCS in the hope of better days to come. So, two of us keep our hand in for a couple of hours each Friday night. For us and many other squads it is all about multiplayer, community and human teamplay rather than single player, so that is were I am coming from. So what I mean as 'better', is in terms of multiplayer, the WWII experience, scenarios and aircraft sets and how our squad as a group value the product and feel valued as customers. So, I cannot give you a definitive 'better', as better is something that can always be open to interpretation and differing opinions, depending on different priorities and feelings. I am pleased that Burning Skies is playing it's part to help development and would like to continue flying the server. It strikes me that flight simulations can be frustrating for developers and customers alike. But when its good its very good! I hope this Tacview issue can be solved without having a negative impact on jetseat users. Happy landings, Talisman

Dev's, please fix this issue with the Spitfire canopy. Also, it would be nice if you could give us a commitment to do so soon. Thank you in anticipation.

https://forums.eagle.ru/showthread.php?t=130161&page=231 Folks, The thread in the above link points to issues with Traceview (cheating?) that looks like data export won't be available on MP, meaning we can't use our jetseats. Sorry if I have got the wrong end of the stick, but this looks like bad news. __________________

https://forums.eagle.ru/showthread.php?t=130161&page=231 Folks, The thread in the above link points to issues with Traceview (cheating?) that looks like data export won't be available on MP, meaning we can't use our jetseats. Sorry if I have got the wrong end of the stick, but this looks like bad news.

What, jetseat not working! DCS WWII is bad enough (air-to-air visibility, poor plane set, etc, etc,) and I have been flying only on Friday nights just to keep my hand in, but now if I can't use my jetseat it is just another reason not to bother with DCS at all. I have constantly been waiting for things to get better on the WWII front and now this. I shall try Burning Skies tonight, but if my jetseat is not able to be used then I shall be jacking it in, yet again, and concentrating on flight simulations that deliver a better WWII experience. DCS is really the most frustrating combat flight simulation I have ever been involved with. I hope it gets there eventually, but I am not sure I will still be around to see it. Happy landings, Talisman

Production Mk IX Spitfires started to emerge from Supermarine plants in June 1942. No 64 Squadron was the first to recieve the new variant in June 1942; it was followed by No 611 Squadron in July 1942 and Nos 401 and 402 (Canadian) Squadrons in August 1942 and No 133 (US Eagle) Squadron in September 1942. Production of the Mark IX built up rapidly. The Mk IX Spitfire entered service in 1942, but the version we have, Merlin 66 engine and .303 machine gun, is the LF version that entered service in Spring 1943, not 44. The Biggin Hill Wing was one of the first to re-equip with the Mark IX LF The Spitfire that would be nearest on the technological time line and release to operational service to the FW 190-D and 109-K versions we currently have in DCS is the Spitfire Mk XIV. The first production Spitfire XIVs appeared in October 1943. The first squadron to recieve the Mark XIV was No 610 based at Exeter, which re-equipped in January and Febuary 1944. During March 1944 Nos 91 and 322 (Dutch Squdrons also began to re-quip with the Mk XIV. All three squadrons of Spitfire XIVs were fully operatonal. Source for above information: The Spitfire Story, Revised Second Edition by Alfred Price, ISBN 1-85409-305-3 (Foreward to the book is by Jeffrey Quill and the Preface by Dr Gordon Mitchell. Below is a combat roport of action between Mk XIV Spitfires and FW 190 dated 7 March 1944: Combat Reports 610 Squadron's Intelligence Officer recorded on 7 March, 1944 what may be the Spitfire XIV's first aerial combat: Black section, (P/O Hussey and F/Sgt. Harding) were patrolling on an east west line about 20 miles south east of Start Point 500 feet above sea level, under the control of Kingswear C.H.L. Station. At approx 17.30 hours the Section was told to investigate unidentified aircraft 15 miles ahead, on a vector 120 degrees. After two minutes this vector was changed to 150 degress (At this time Black one was using only plus 12 lbs boost with his jet tank still on, and the A.S.I. was clocking about 350 miles per hour.) The section was now outside G.C.I. cover, but after about a minute 3 F.W. 190's appeared from 9 o'clock approx 200 feet below, flying in a fairly close vic on a rough vector of 240 degrees; visibility was bad owing to haze, and the section had hardly seen the E/A before they had passed underneath to 3 o'clock. Black Section immediately pulled round to the right, and it seemed that the E/A saw them at the same moment, for as our section turned on their tails, black smoke was seen pouring from their engines as they pushed everything forward and dived to sea level. The F.W. 190 on the left of the section turned south, and the other two turned away and disappeared into the haze and glare of the sun. Our section gave chase to the single F.W. 190 which at this time, was about 800 yards ahead, right on the deck. We closed without difficulty but when 400 yards away, Black 1 noticed a F.W. 190 making a quarter attack on him from between 4 and 5 o'clock, so gave the order to "break right". As he pulled up he saw the E/A fireing at him with insufficient deflection, and it appeared that the turning circle of the Spitfire XIV was better than that of the F.W. 190. Black 1, at 1,000 feet, was now in the haze and lost sight of the F.W. 190 and his No. 2. Black 2, who was on the left of Black 1, saw the F.W. 190 break off his attack on Black 1, and dive south west to sea level, so he rolled down to the left and got on to the tail of the F.W. 190 at a distance of about 800 yards (The F.W. 190 that our section had been chasing originally, had disappeared by this time) At first Black 2, did not close on the F.W. 190 as fast as he would have liked (probably due to the excitement, he forgot to jettison his tank with Black 1 at the commencement of the first chase. The addition of the jet tank would probably take off 30 miles per hour.) Another F.W. 190 now appeared ahead at about 11 o'clock, and joined formation on the left of the aircraft that Black 2 was chasing. Black 2 now found that he was closing in quite fast, around 400 I.A.S. and opened fire on the left hand F.W. 190 from dead astern at 300 yards he saw strikes on both wing roots and panels flew off the port mainplane as he closed to about 100 yards. Not until the strikes were observed did the other E/A take any action. Even then he did nothing for some time, then pulled straight up and round to the left, and tried to get on the tail of Black 2. Black 2 took a final squirt at his target whose only evasive action was pitching slightly up and down, before he broke into the other E/A which was trying to get on his tail (although clocking 360 m.p.h. the turning circle of the Spitfire seemed superior to that of the F.W. 190) The F.W. 190 fired at Black 2 but allowed insufficient deflection then broke off his attack and disappeared into the mist. The E/A was not seen again. 60 Spitfire Mk XIV airpower was over mainland Europe by at least May 1944, With Number 322 (Dutch) Squadron over Antwerp and Volkel, Spitfire Mk IX and XIV aircraft took part in the D-Day Normandy invasion from the 6th June 1944 onwards. The Spitfire XIV is a perfectly valid aircraft for the DCS WWII map, given the date it entered squadron operational service, as well as the numbers over the battle space launched by 2nd TAF (five squadrons of Spitfire XIV) and also from the South of England. The RAF was able to use older less able aircraft like the Spit IX and Typhoon because the Allies had air superiority. Superiority that is not modelled in DCS or any combat flight sim because we would not want that. Therefore, it makes sense for sim developers to pay close attention to the technological time line for the aircraft involved. I suggest that if the Allies had been more desperate and did not have total air superiority, they would have prioritised more Tempest V and Spitfire XIV aircraft, but historically they did not need to. DCS is not totally historical WWII, but it does its best to give us a sense of air combat with some of the aircraft that were involved. The technological time line of the aircraft we have at the moment is somewhat disjointed, but that should improve as time goes on I hope. Happy landings, Talisman

Thanks for the invite folks, but I and those I fly with use TeamSpeak and not simple radio. I do not intend to ever download and use simple radio, but it looks like simple radio is compulsory. So I will sadly give this event a miss, even though I love flying the Mig-15. Good luck and have fun. Happy landings, Talisman

Could not agree more! Why DCS puts valuable time and effort into this is beyond me. I have to spend time deleting all their default assignments to put in my own. Happy landings, Talisman

Thanks Bob. Talisman

This is what we need.

Hi Folks, Just a quick question. Is it still worth turning off hyperthreading in the bios these days, or is that no longer necessary for better performance? I am hoping to progress to VR soon and am not sure if turning of hyperthreading will help. Thank you in anticipation. My system specs: 5Processor: Intel Core i7-8700K Coffee Lake CPU, 6 Cores, 3.7 - 4.7GHz, overclocked Case: Fractal Design Define R6 Case - Black Graphics Card: NVIDIA GeForce GTX 1080 Ti 11GB Graphics Card CPU Cooler: Corsair Hydro H100x CPU Cooler Motherboard: Asus STRIX Z370-F GAMING Memory: 32GB DDR4 3000MHz Memory (2 x 16GB Sticks) OS Drive: 1TB Samsung 970 EVO M.2 PCIe Solid State Drive Secondary Hard Drive: Seagate 2TB FireCuda SSHD Hybrid Drive Optical Drive: 24x DVD-RW Drive Power Supply: Corsair RM850x 80 PLUS Gold 850W PSU Sound Card: Onboard High Definition Audio Operating System: Windows 10 Home 64-bit Monitor Samsung 2433BW 24" TFT, 5ms response time, Res: 1920x1200 MS FF2 Joystick Thrustmaster VG TWCS Throttle Saitek Pro Flight Throttle Quadrant MFG Crosswind Rudder Pedals TIR4(V.5 software) & Track Clip Pro eDimensional AudioFX2 FF Vibration Headset Gametrix KW-908 Jetseat (with SSA software) Happy landings,

Thanks Phil and Dietrich. Your reputation and admirable commitment has persuaded me to download the beta version and give DCS WWII another go. I have managed to convince one other member of our squad to join me, so I hope to be punching holes in the virtual sky on your SoW Historical server soon :) Many thanks for all your work and providing the server. Happy landings, 56RAF_Talisman

Hi Phil, Will this server be on the release version or beta? Happy landings, Talisman

Bos_Man, You need to see this: DCS 1.5.6.1938 Update 2017-02-10 DCS World S-25OF rocket. The motor flame effect increased to S-25L level. Sweden was added to blue coalition by default. Propeller drawing procedure in controllable aircraft was reworked to handle rare negative prop phase values in a way it won't change prop blur mode. Trigger zone can be set to 5 meters radius now, instead 100 meters minimum earlier. Corrected 3D shape of MiG-29S wingtips. Force Feedback can be enabled for Saitek Cyborg Evo Force joystick (need to add ‘input.blacklist_ffb = false’ line into \Saved Games\DCS\autoexec.cfg file). MP. Corrupted F10 map after Changing mission function restored. MP. Client crash after connect to server when RB-04 is in flight fixed. It is also covered in this thread: https://forums.eagle.ru/showthread.php?t=180624&highlight=Saitek+Cyborg+EVO+stick As you will see I had a problem too and got it sorted. Although, I now use the MSFF2. Good luck and happy landings, Talisman Faded UI when set antialiasing 8xQ fixed.