Sylosis

First off, why the passive-agressive condescending tone? With your statement, I assume that you have absolutely never bitched about anything in your life that isn't related to your area of expertise? For example, suppose that you are... A surgeon... I would assume you never express an opinion on something that isn't medical related. How could you comment on, say, cars....? After all, you're not a car engineer or something.

Maybe not helpful, but do you have DCS installed on a SSD? It makes a very big difference in reducing the "short pauses" and "stutters" that are often caused by map loading, or whatever. Speaking for myself I was having a lot of those, until I switched DCS from my HDD to my SSD.

Yes as a matter of fact, I did change them, though not clearly mentioning it. When using the graphic preset "High" they are set to a higher settings. I don't remember which one, but I think they are set to "High", or at least something better than the Low option.

All right so it seems I'm talking to myself in this thread but whatever.... I'll post anyway in case somebody has the same issues as I have... I realize that, when I re-installed the Open Beta, it probably didn't delete the Open Beta folder in the Saved Games path. The fact is, I still have the DCS Open Alpha (pre 2.5.0) folder in Saved Games, though I have deleted that version of DCS a long time ago. So I should try yet again to re-install the Open Beta, but making sure I completely delete that Saved Games folder called DCS Open Beta (and Open Alpha while I'm at it)... I'm losing faith and I'm not super confident it'll work... but it's worth a try.

AAhhhhh.... Now it's perfectly clear. Wow ok...I never understood the concept of SPI like that. Quite an important thing to know!!!

Sorry here they are Logs.zip

I tried re-installing the previous GPU drivers (doesn't make sense, but why not try right?) Doesn't help either... I'm lost here... Any chance I can have some kind of support by ED? Also, attached are the log files, if that helps in any way... :(

All right, so after deleting the 2 folders, named "fxo" and "metashaders2" from the OpenBeta Saved Game location, nothing changed. The SU25T looks exactly like the screenshot posted above. Is there, maybe, something that could interfere between NVidia Control Panel and DCS Open Beta? I'm throwing ideas... however I have no clue what I Should be looking for...

As an update, I have tried the following: - I deleted and re-installed DCS Open Beta. Before downloading my modules, and even copying my config files for controls, I first tried an instant action with the Su-25T. Still ugly on high settings. - I tried the cleanup and repair method that was suggested. Still didn't help. See a screenshot of how it looks like. I will then try to delete the folders, as suggested and let you know what it did.

Thanks a lot Yurgon. What I understand of your explanation is that my "intent" was correct, however I was not using the proper tools. To kind of "save" my last point of interest, it's a markpoint that I must create, and not a SPI, since it'll most likely move due to the TGP gimball limit. I'll definetely try this... It should help a lot finishing that damn Hammerfall Part 3 mission and kill that damn SA-9!!! :pilotfly::thumbup:

I've tried looking for info in the manual and in this forum, but I wasn't able to find what I was looking for... Maybe I used poor keywords, or something... Anyway I'm having issues with the A10C and the TGP. Whenever I scan an area, 99% of the time I'll spot something, but it'll be too late to have a good lock, or too late to shoot. Or for example, it'll be a transport truck that I see, yet I know there is SAM near and I want to find the SAM in my next pass. So, that being said, what I would like to do, is create a SPI on the Transport (for example) and lock the TGP onto it. So, I push the TWS up short once, and again up long, to both lock the TGP on the Transport and create the SPI onto it. What I have as a problem is that as I go away and come back for another pass, ,my TGP will have completely lost my target. I guess this would be normal... as I know the TGP can't turn in any possible direction... is does have its limit I assume. But then, if I push China forward long to send all sensors onto the SPI, it won't even be where it was (on the transport truck)... It will be in the middle of nowhere. I'm sure there is something I don't understand, but I thought creating an SPI was marking it "indefinitely" or something... or at least until I reset the SPI to the steering point, or create a new SPI. Because of this, I'm very inefficient at getting ground kills... I basically have to be able to find what I want in one pass, else I have to re-do everything all over again. So, if everything is behaving normally, this would mean the method I was hoping on using is shit. Would you have other recommendations? Because, for example, if I want to drop a GBU12 using my TGP, often you might not have enough time, after your TGP lock, to drop the bomb, and you'll need another pass. If you lose the lock, as so happens to me, you basically have to manage to lock and bomb in one pass... but I'm sure something can be done right?

Deleting the folders competely or just their content? Also, if you don't mind me asking, how do you do a repair on DCS (standalone). Is there a repair utility tool somewhere in the files?

Tried everything of what you both suggested and nothing works. I am joining more screenshots, this time of the Mig21bis, as it is a lot more obvious than the A10 I showed The A10 is not as ugly, but it still is, versus the released version. The screenshot seems to make it look a little bit better, maybe because it is a smaller image, versus what I see on my 32in monitor. As for the Mig21, you'll see 2 screenshots taken from a night mission (which makes it even worse). One is from the Open Beta, the other one from the Released version. The ugly one is from the beta. And it is taken with the "High" preset from the settings. It's right after the start of an instant action. I didn't touch any lights. This is why the other screenshot is so dark. I wanted to keep the same cockpit settings, so I didn't turn on any lights. So ya, that dark screenshot, but still nice, is from the Released version. And by the way, copying the config file from the released version to the beta version made it absolutely worse. The textures were all over the place. For instance, the altimeter numbers were in the middle of the cockpit, and not where the actual gauge is... !! haha

Sorry, posted the wrong screenshots BTW, I have the latest video card drivers

Here is an example of how it looks. Here is also a screenshot of my graphic settings

I'm still trying to figure out how to share screenshots... For some reason I'm too dumb to do it, or so it seems. Nevertheless, it looks like FSX in 2012... But, actually, the gauges look great. Altimeter, etc... but everything else is shit. It's extremely bright, blurry, can't really read the text in the cockpit because it's blurr, etc... My rig: GTX 1060 6Gb i7-6700k 16 GB ram Windows 10-64 bits

I have tried the Open Beta for the first time and I have an issue with graphics. I know the settings reset, so I went and set them roughly as I have them in the released version... and man... it looks like I'd have everything on low... My friends, with whom I play, don,t have that issue... I've searched the forum and didn't find anything that seemed like my problem.

Is there something I don't get in this mission...? I've looked at the mission in the mission editor and it's really something like 24 against 12. And, though the briefing seems to indicate that I shouldn't attack fighters, they pretty much wipe the group of Mirage and the group of F16s with ease... Leaving me 2 against 24... And, the Mig21 is probably, from a general perspective, the worst aircraft in that mission, I don't see how I can survive. My missiles have something like 2nm of range, versus A120, R77, etc... So I don't what the campaign creator had in mind, but this mission is nonsense...

You need to realize that not everyone wants two instances of a 100Gb program on their SSD... This is the only reason why people opt for the Command Prompt method. :lol: Kinda funny that you stated that with so much confidence, as if nobody here thought this through hahaha! :lol: (don't get me wrong, I'm not making fun of you, but laughing of the situation)

Thanks for this. It is a nice simplified explanation than what was originally listed in the old thread. It is condensed in a few steps and therefore, much easier to follow :)

Even if everybody brought forward very reasonable justifications as to why there is a beta versus a released version, the fact of the matter is that DCS "released" version has been irrelevant for quite some time now and it will probably be like that for a long time.. Hell everybody who answered said they were only on beta. Moreover, almost everybody justified the existence of the released vs beta for testing purposes, which is, we'll all agree, the usual reason for beta vs released. However, considering how "not great at all" the current released 2.5.0 is, one can question how much this stil stands in DCS. Clearly it required a lot more testing and tweaking, yet it got released. So, in my mind, I can understand the OP's question. I've never seen a "game" where the beta is the mainly used version. On anything else, beta is usually quite unstable and a fraction of the population uses it. On DCS, I don't see many complaints about the beta being broken (or at the very least, it doesn't seem worse than the released version), plus almost everybody is on it. So ya... "In theory" the released version has its relevance. But in practice I don't really see it.. Don't you think?

Well, at the moment I am 90% of the time on Caucasus, and that is when I have issues. That is, I'm on 2.5.0, not the beta (though considering ED seems to think their beta is the official version I'm seriously thinking of making the switch). So ya, I have that issue on Caucasus and it's all the time, on any airport. I don't remember a time where I got the takeoff clearance while being far from the runway. I was able to, now that I know that trick, consistently have clearance by being at that precise position (almost on the runway).

Yes and I will try it! :) Even though I am uncertain, I kinda understand where you guys are coming from with the suggestion. There is some logic to it, so I'll try, that's for sure. :P

Don't take this the wrong way, please, but I feel I should clarify that I am not trying to find "the easy way out". Too often on the forum, I feel a lot of people are quick on the trigger to assume people "are not committed enough" or something, or just looking for some "easy way out". This is not my intention at all, and maybe it seemed like it was...? I don't know... To say again something I mentioned before, the basis behind my "search for a curve" was after looking at real pilot video and realizing they were not doing "micro-movements" of the stick to do small corrections. While it felt like this is what I was doing on my side... So I thought "Hum ok... maybe this is why I am having a hard time". So, if anything, I wasn't trying to find an easy way out, but rather making things more realistic... And also, my girlfriend surely things I'm spending enough time on DCS... So it's not like I am not putting in the hours ;)

Thanks for the list, as it might help others who would perhaps read this thread. However, speaking for myself, I was aware of pretty much all that you said. The problem that I was having: - When stopping before the runway, to ask for takeoff clearance (as you pointed out), I was a couple of feet too far from said runway. As it was mentioned, it seems ATC is expecting you to have the nose of the airplane further away, in such a position that it is actually above the runway, with the rest of the airplane being still on the taxiway. Only then will it answer your request for takeoff. If you are too far by only a small amount, you won't get any answer.