Hiromachi

Yes. Weight. P-51B was quite a bit lighter without that radar, two more brownings and couple other things while operating at same engine ratings. But if we speak of P-51B then I think best visual differences are in the cockpit and tailfin area. Personally I wish for a P-51 with Malcolm hood.

I see. Well, with all four dimm slots occupied you will have issue reaching higher frequencies. Still, your score is very fine if its 4 x 8 Gb. With Ryzen 1 that could be tricky if not impossible to achieve. Your IMC must be better binned than mine in this case.

3533 should really work on something like Cl15 or Cl14 even if you have a good chip. I took a different path and right now run 2700X with features enabled on Asus motherboard, so its as follows: CPU PE2 enabled with -0.04375V offset (all core 4.05 Ghz, single core 4.3 Ghz) SoC 1.1 RAM 3466 mhz CL14 Low Latency setup at 1.4V The last one really makes me wonder whether DCS would benefit more from a higher frequency of the ram or perhaps tighter timings. 3466 low latency is supposedly the best of both worlds. I know some people can get 3600 mhz at CL15 but my chip to get something useful of that would require a lot of tweaking and voltage. Its unstable beyond 3533 mhz so I've decided to step down a bit and get tighter timings.

A few more pictures were posted guys: https://www.facebook.com/media/set/?set=a.2023648294524505.1073741836.1586481878241151&type=3

Yes, we are of the issue. We will investigate it and look for a fix as soon as possible.

I wonder what benefits will I see compared to my current system. Before the weekend I've preordered R7 2700X, Crosshair Hero VII, G.Skill 3600 Mhz Cl15 B-die kit and Samsung 960 Evo M.2 SSD. 2600k sits normally OC'ed to 4.8 or 5.0 Ghz, but memory is very bad in this one. So until the above glory setup arrives I keep reading threads about overclocking, precision boost override and memory overclocking to figure out where it may get me.

So am I. But Rudel even more since it's a lot of work and I bet he would like to be done with it :)

Sure I can! As a matter of fact last night I felt my post was missing something and reached guys to get some picture on what is going on with most pressing issues related to pit. Here are pictures, as you can see canopy glass glare is already fixed: As for the rest, gauges and needles are being modeled to prevent alpha blending errors. Original needles use alpha textures to create intricate shapes. Ufortunately the alpha blending errors causes some needles to appear either in front or behind others. Lights will be fixed after UV of needles are complete.

I'm sorry Applesinduck, but that's just not true. There was a number of fixes since CE2 announcement, some of them very important and concerning many users, namely the collision model issue that affected performance and was causing low FPS when more than few MiG-21 were up close. For more details check DCS 1.5.8.12162, 1.5.8.12823 Update 1, 2.5.0 changelogs. Plus a few smaller ones, not indicated in changelogs, like recent issue causing game freeze. I know that pace of development is not as fast as you would wish, but statement that there was no significant update since CE2 simply lacks basis. Particularly with New Years update where Corsair was teased.

This is exactly what I meant by P-51B with Malcolm hood Though it should have a tail-fin by the time of Normandy.

Since I'm flying ww2 on daily basis and we have Normandy map along with ground units complementing it I think it would be reasonable to ask for plane-set that suits this map and conditions. A coherent plane-set so to speak. Something that fits early to mid 1944 ? I also remember it was mentioned that there would be 190 A-8 in development as an Ai, if so and you are putting an effort to make a model of it then why not go a step further and make it a completely flyable module ? What I think should work fine and enhance the experience of Normandy is: - P-51B (with malcolm hood preferably) - Hawker Typhoon - FW-190 A-8 - Bf-109 G-6 AS / ASM - Mosquito (a great first step into multi engine aircraft) - Ju-87 G - Me-410 Either way, very nice of you to ask for an opinion of what is required.

Guys, cockpit glass along with the rest of cockpit textures is still under development. We've mentioned that in previous development update so it's known and being worked on, dont worry. But despite what some may seem to be suggesting, it is not an easy fix and reworking textures simply takes time. Rudel is doing this as fast as possible.

Yes, the freeze issue is already well known and worked on. In future please try to take a look if something wasn't already reported as in this case it was: https://forums.eagle.ru/showthread.php?t=204553&page=4

I don't think it's going to be deleted, since nobody employs such actions in this section. We're open to our customers opinions. However this comment is unfair and unsubstantiated since it places blame on us without even knowing which file or part of code could cause it. DCS 2.5 is currently in open beta phase and a lot of changes are going on throughout the game, some of which may involuntarily affect some modules. Recent patch was in terms of size and changes significant so there is a lot to check for us. For now we are aware of the problem and working on it to find a solution. This particular problem is unusual in that some experience it and others not - for example under every condition and on any map MiG-21 works for me flawlessly. But for others it doesnt work at all. We've already ruled out any hardware reasons, since it occurs regardless of AMD/Intel cpu and AMD/Nvidia gpu. When I will know more, I will provide an update.

Ok guys, we're investigating this issue and looking for possible source of problem. Please keep attaching your logs.

Burning Skies. As far as I'm aware there is no wind on that one.

No worries, I did not wish to sound harsh mate. If I did, please accept my apologies. All I know is that I've been flying P-51 for four years now and broke my wings number of times, but in most of events I knew why it happened and that it was clearly my mistake. This is a rare instance where I did not understand why it happened (particularly in game it surprised me as it looked like something hit me as both wings exploded). It is possible that racks affect G tolerance, but then I wish this was indicated in manual and how far they do. But I also was flying at some very low weight, a few hundred pounds more than empty weight so there is that. It just always surprises me that wing fails in P-51 often at moderate G's. Especially seeing Galloping Ghost accident, where aircraft in a split second reached a vertical acceleration of 17.3 G and a moment later only a section of the left elevator trim tab separated. Wings remained attached until crash. But then again, it also had 8 feet shorter wingspan which would surely affect the maximum load tolerance, even though it was still a ww2 air-frame to some degree.

I dont buy that, I have exceeded manual limit of 8 Gs once for a very brief moment and it was a minimal excess of 0.2 G, where 8 G limit has to be taken into consideration with 1.5 safety factor. Any other time I stayed below 8 G limit so I stayed in manual limits. Besides, read what I've posted. There was no next hard pull failure, the failure occurred during the moment I was relaxing the stick and G's were decreasing. I thought that perhaps deceleration was too fast, but dont think 3 G deacceleration in 2 - 2.5 sec is rapid.

A few days ago during online mission I had an unexpected event, as during pullout both of my wings failed and this was accompanied by sort of an explosion animation (??) as both of my wing roots started burning and smoke was coming out of wing root while I was rolling and going straight to the ground. At first I thought that I was hit by friendly AA but that turned out not to be the case and as it appears both of my wings failed during pullout which is peculiar in that it happened not at the peak load but at a time when my speed was decreasing and I was slowly relaxing the stick. I did not record that live as my FPS in game does not leave good enough margin to keep recording all my flights and also because it was totally unexpected, but thanks to Tacview I managed to get flight situation in detail and capture it. Here is the video: As you can see during dive I was flying near the dive limit (505 mph - 813 km/h indicated) but eventually when trying to obtain firing solution and pull out of dive (for obvious reasons) I reached 6.8 G's, which was significant so I started relaxing the stick and trying to let her come out of the dive gently. Then, about 2 - 2.5 seconds later when speed dropped by 15 km/h and acceleration was only 4.1 G's both of my wings sort of ... "exploded". I presume this was a peculiar wing failure but cannot understand why it happened at that moment, not when I was at the peak of acceleration but when I was already in process of gentle pullout. I have maneuvered mildly during previous combat, though two to three times I've reached 7.1 - 7.3 Gs and once in diving roll I've reached 8.2 Gs for about a quarter of a second. Weight during this event was very low as I've expended 502 rounds of ammunition (27 %) before and fuel state was aprox. 43 gallons (15 on left tank, 28 on the right). So I guess my weight was around 8600-8650 lbs during this event. Not sure if its important, but my aircraft was equipped with underwing racks as before entering combat we've used external fuel tanks. In any case, I felt its worth investigating and checking for a potential bug, since I couldn't explain it myself.

I've checked other threads about micro-stutters but being unsure of their nature I figured its best to create separate one of what I've been encountering for the past few days. So flying on Normandy (Burning Skies server) in the last few days, when server gets a decent number of players, I start encountering stutters. Basically my FPS drop by 10 to 20 and that causes the stutter. It occurs every 2 to 4 seconds, so one moment I have 70+ FPS, then 64 FPS and then 57 FPS ... and then I'm back to 70+ FPS. This loop of constant drops is the source of stutter I'm seeing, that prevents any effective combat flying since aiming is near impossible when you jump with reticle all over the place. Now the thing that I wonder is what is the source of this constant drops ? When mission is fresh, after server restart, its all fine. But once a number of ground targets gets destroyed and particle effects like fires and smokes are present on the map this happens. So I started associating issues with particle effects, but cant exactly confirm that one. Otherwise could it be server overload ? I know that none from my friends is experiencing this in such way so it cant be server side thing. Those are my graphic settings: No fiddling in Nvidia panel except for G-sync. System specs can be found in signature. I've tried lowering graphics, turning off mirror, switching MSAA to OFF and using FXAA via Nvidia Control Panel but despite FPS increase to 80 or 90 those stutters did not vanish. And effects gave me unpleasant shimmering so I'm back to MSAA x4 which my pc can handle. If anyone has experienced something of this nature and could help I'd appreciate that :helpsmilie:

Great, thank you Eekz!

Good change, +1 from me Eekz.

@Try running DCS repair and if it keeps happening, please be so kind and post pictures of the issue and game logs. That way we can try to track the problem.

Yes, air starts included. I tried a couple of duels ( damn, I'm really not that good Fishbed pilot :megalol: ) but still everything worked fine. Every time. Its really not possible to track something that one cant reproduce despite spending hours on it and repeating it every few weeks. And I've tried it on 1.5.8, 2.2 and 2.5 now. It just always work for me.

I concur. We are back to old base rush and vulch fest that resembles war thunder instead of historical mission that DCS as a flight sim is supposed to show. Caucasus is much larger and now with beautiful graphics there is plenty to see and play around. Same for Normandy. And as DefaultFace said, lots people came back to BS. One can now take advantage of this.