Redglyph
-
Posts
1644 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Redglyph
-
-
That feels very weird.
Why is there such a profound change after all this time?
And regarding the long stick course forward, if the real stick has a shorter course, wouldn't that be better to simply saturate the pitch after half its course forward instead?
-
By the way, there isn't a TF-51D unit either, I think this one deserves some love, she's been neglected ;)
-
Updated to 1.5.8 and 2.1.1. Sort of, there was no change anyway.
-
DCS 1.5.8.12265.407
The track doesn't seem to work with this version anymore, the Gazelle hits the ground after a while, bounces and makes funny things, so I expect there were changes that made it incompatible.
I just tried, what I observe:
- in speed hold, works as expected, trim up/down change the altitude, speeds remain constant
- in alt hold, first the altitude must be level for this to engage
- if I trim nose up, slows down at constant altitude
- if I trim nose down, first the attitude changes to nose up, then after a while it decides to finally nose down and accelerates at constant altitude. If I release the trim button and do it again, it directly goes nose down without the nose up, and if I trim nose up, it directly changes the attitude to nose up and slows down.
- if I trim nose up, slows down at constant altitude
That is a bit weird.
In DCS 2.1.1.11762.287 it seems to do that sometimes and for a shorter time, it was less obvious than 1.5.
- in speed hold, works as expected, trim up/down change the altitude, speeds remain constant
-
No problem SnowTiger, I understand how it is :)
The track is a bit desperate and probably won't help much, just to reduce the possibilities of what went wrong and from what you said, it could be either an update bug or a config that went south after the update (or still other things perhaps). That last one shouldn't happen, it's weird, but something had to happen at some point... I've had those bad configs once or twice but different.
EDIT: yep, forget the track. It's 2.1.1, doesn't use the alt hold, and I see the same problem as you (I think) in 1.5.8 anyway. Let's see in the other thread.
I see you had posted one as well in the other thread, I'll have a look, this makes more sense because I probably haven't used the trim much in my track.
Yeah, Polychop hasn't come back on this problem yet, you could send borchi_2b a PM to ask whether they had a chance to talk about that.
Or you could also revert to before the update you suspect. I've done that in the past and had no problem, check this page for the versions, and the instructions if you scroll up a bit. That'd be the more definite, but it could take a while to download stuff.
-
Again .. and for the last time ... Everything Appears to work correctly in that the Trim Controls work .. the TRIM Itself Does NOT work. I don't know how else to explain it.
I have spelled it 3 ways 5 times.
Well then, why did you post here saying you've got a similar problem? I'm not forcing you, just trying to help, but do as you wish.
-
That's weird. I just modified one of my uploaded files and it worked.
What did you see exactly (message, ...?), and could you give a step-by-step description of what you did?
-
Hello,
Just noticed there was no unit for this new aircraft yet, it could be useful to have one :)
Already a few files placed in random categories as work-around...
Thanks
-
Ah, that's probably why the Special settings shows the "Option 1, option 2, option 3" laconic checkboxes then? That's what I assumed anyway :)
-
I confirm I see the same, on the several test missions from cold start.
Additional info:
If I disable TrackIR, no change - good, it's not me shaking with delight, even though I am delighted ;)
If I disable "Head Movement by G-Forces in Cockpit" in the MISC settings, no change.
Changing cold start to hot start makes the shaking disappear.
DCS 1.5.8.12265.407, this issue was not in 1.5.8.12162.
-
Hi,
Is there any good way to start learning the f-18 sistems of the f18? This way, whan it comes out i could already have all the knowllege needed to fly it. :helpsmilie:
You can find the complete manual, including the performances, on Avialogs (performance charts are missing in the NATOPS version):
It's a long read :)
-
I have a low end rig, and my PC runs 2.1 just as well as 1.5.x
I'm guessing that if anything, 2.5 will be BETTER optimized. Hopefully that helps ease your concerns :)
That's surprising, but what do you mean by low-end? It's very relative ;)
Have you tried the Epsom campaign? For my part it's simply not possible. I have no big problems with a single airplane or even a few aircraft around, but there's a lot of stuttering with a full-scale campaign, and it's regularly below 20 FPS with periods of noticeable freezes.
Another example is the antialiasing: without it the performances are better but it looks very bad. With AA, unfortunately, the framerate is quite impacted. And this is permanent, even with no other traffic, it's just the scenery. From the long threads in which people were trying to tune the settings and improve that, I'm not alone to experience this.
It will surely be better optimized than now, for sure, but how much gain is left... a 980 Ti is not enough, and a recent processor is definitely mandatory. So if 1.5 can live a little while longer, I won't complain :)
-
I can feel RAZBAM's frustration from where I am sitting, that is a rough bug, especially in the context of 2.5 being weeks away. The day the devs can close the 1.5.x branch and never look at it again they are going to celebrate.
Well, not too soon hopefully, many of us don't have a system poweful enough for what 2.x requires ;)
It must be frustrating but it's apparently a potential problem they noticed, chances are with a more serious load (DLC campaign with many aircraft...) this would have come up anyway.
In any case, no one would expect an early release to go perfectly smoothly, it's just an FPS drop after all. What's already there more than makes up for that! :)
-
I think this is a 1.5.8 issue as all other aircraft I've tested have noticeably lower FPS as per the Harrier when compared to 1.5.7 release using the exact same settings and options. Might be worth a look there. Have tried lowering all settings to Low and this had marginal gains.
Still that being said....still fun to fly/crash.
Most of us reported otherwise, by comparing the different aircraft in 1.5.8. We are not comparing to 1.5.7.
It is very fun to fly :) ... and crash ;)
-
They are going down this road, but it may get tweaked, we will have to wait and see.
As for servers going down, you could say that about any online service, even steam goes down sometimes.
That was my earlier question and suggestion, if anything in the connection is down, there's one chance in 4 that DCS is unavailable to the user, provided they log in every day. If that is not the case the chance quickly becomes one in one, and it's pretty safe to assume most people don't have the time to log in every day.
Hopefully the new system can take that into account but it doesn't seem to be the case right now.
To answer someone else's question, yes, servers or Internet connections do go down now and then, I've witnessed other sims for which it's frequent every single time there's a release - everyone's rushing to test it and the server lags then shuts down. So it is very real and really frustrating on those days. That is my main concern with the always online requirement (and as shown before, this system is equivalent to such a requirement).
-
1
-
-
Hello,
Again a little test with those switches and knobs, to see if they're consistent with the usual DCS rules on mouse click and avoid the sad fate of the A-10C ;)
DCS 1.5.8.12162.404
Inverted mouse switch logic:
- Flaps power switch
- Compass lights/Test lights
- Armament mode control
- Fuzing control
- ... all 8 armament switches actually - the knobs are fine
Misc inconsistent behaviour:
- COMM1 has push animation, not COMM2
- MPCD push interaction is only 1-way for the corner, 2-way switches (DAY/NGT, ...)
Probably WIP?
- Stopwatch not interacting (Stopwatch start/stop)
Other/questions:
- INS mode know cannot turn to test from off, has to be turned clockwise all the way, on purpose?
- Flaps power switch
-
What you describe is not lag, it's low framerate, there's already another long thread on that.
-
I've been told that Senaki is a FPS sink no matter what aircraft. We will edit the mission.
But from Sukhumi I don't experience the same issue with an A-10C (for ex) with the FPS hit depending on the aircraft heading when it's on the ground, so is Senaki really the explanation?
Did a quick test at Kutaisi (very bad no matter the heading), Kobuleti (bad), Batumi (50 FPS with 180° heading, otherwise 40-ish FPS)
At Vaziani, fluid 60 FPS (capped) except heading 270 where it's 50 FPS.
At Beslan, it's fluid 60 FPS for any heading. Same on a road nearby.
-
Wouldn't it be much safer if it was trying to connect each time, even in the background to avoid waiting, and registering the last successful validation, THEN have a n-day tolerance?
Otherwise, if the server is down or if an Internet connection is not available this 4th day, it means DCS is not available, correct? So in case of problem there's a 4-in-1 chance we can't access it.
I also find 4 days quite short, is there a reason why it's 4 and not larger as usual in other systems? It's not as if everyone was running DCS every day, so the 4-in-1 chance would still remain in most cases.
-
VSYNC didn't change anything for me.
I realize in my previous tests, I had to change the starting position of the Harrier.
If I'm at Sukhumi, and start from the ground facing 0° or 90°, I have 30-40 FPS, apparently the time of the day doesn't change anything, I even tried at night. Facing 180° or 270° I get 60 FPS.
That's pretty weird. Is the compass acting up? ;)
EDIT: shall we triangulate to see the source of the problem?
EDIT2: takeoff from ground facing 90, on a road West of Senaki, it's even worse, down to 20 FPS.
-
Ah, so it's not a hidden feature we have to find :D
-
Ouch, same here, very low FPS in DCS 1.5.8.12162.404 with the A/V-8B.
System specs in the signature, nVidia drivers 388.31 which should be the latest or close.
I've tried both the Quick start/Cold start mission, I have about 30 FPS before touching anything in the cockpit. Usually I have 60 with rare exceptions (vertical sync ON, so it's capped).
I made a custom mission (in attachment)
- with the Harrier in parking 01 at Sukhumi, an A-10C in 02, same results
- with the Harrier in parking 03, 60 FPS, same without the A-10C
EDIT: scratch that, it seems to be something else after all. Sighs.
=>The proximity with another aircraft seems to be the problem.
-
There are no activation's, it is linked to your ED account.
You can only use The AV-8B from this version number on-wards, so older versions can not be used for the AV-8B
Yes of course, I meant for the other aircraft once they change to this new protection scheme.
That's great, thanks!
-
Is there a limited number of activations (or even a concept of activation?), in case we switch back to an older version of DCS for example, then back to the latest, or re-install DCS, ...?
Any news at all from M3?
in Magnitude 3 LLC
Posted
They are still alive! :) I was really concerned though.
https://forums.eagle.ru/showthread.php?t=185366&p=3298194