hazzer
最新回复 发布由 hazzer
-
-
On 9/4/2025 at 10:30 PM, RustBelt said:
You want to tell that to the server host not The Devs.
But fixing it would be nice, and probably won’t ever happen.
Yup seems the only way. Personally I believe the issues like this shouldn't make it into the game. If it was an aircraft flown more often it would make it borderline unplayable.
-
On 7/20/2025 at 10:38 PM, ex81 said:
Thank you. Looks strange.
You'd be correct in it looking strange, but it seems nobody developing anything for dcs has paid much attention to reality. The exhaust shouldn't be visible in the daylight. At night time it should be, it certainly shouldn't look like that.
-
2
-
-
Had the misfortune of joining a server where someone is flying the CEII. The horrific sounds still remain + for some reason they (STILL) have some mixing issue, a p51 was next to me and the CEII further away, yet the CEII sound was louder than that aircraft and my own. This aircraft should be fixed or removed as to not hamper user experience.
-
Almost 2 years later since the start of this thread. Decided to make the ever rare attempt at playing DCS. This shutdown and incorrect operation is still present.
-
1
-
-
nullCan't find any other post referencing this. Have tried to launch dcs multiple times. The window is stuck in the corner as shown in the screenshot. The launcher does not appear to have any ability to move the window either.
-
I have just been reading flypast magazine, with Steve Hinton discussing the mosquito.
He says how everything is a bit odd in the mosquito like the on position is down and not up. This has made me check and realise the dcs mosquito is different. The question is, is it wrong? In the mossie the magneto on should have the switches down, but in DCS it is reversed.
-
2
-
-
On 5/23/2024 at 4:13 PM, some1 said:
What is considered weak in real world applications is still very strong by flightsim hardware standards. According to the linked document, a change in airspeed of 50 kts in landing configuration still results in a force change of several kgF on the stick.
Meanwhile in Heatblur's implementation the change in these conditions is something like 0.15 kgF on a VPForce Rhino... when measured at max deflection, and much less at neutral trim position as measured in the real test. It's basically a limp stick. Even the strongest FFBeast hardware will not produce realistic forces with FFB inputs like that.
Here's a comparison of how FFB works in practice. Blue line is DCS F-4 at stock settings. Red line is DCS F-4 at 250% gain, even when scaled it is still very weak at approach speeds. Yellow line is how other ED aircraft with aerodynamic forces on the stick are implemented. Not great either, as FFB spring saturates quickly, but at least the stick is centring nicely at low speeds and feels more like a real airplane.
A green line is a possible compromise solution that would both provide decent centring force on takeoff and landing, while also retaining the effects generated by F-4 Phantom control system.
*The lines are drawn from a few data points so they may not be fully accurate, it's just for illustrative purpose.
Thankyou for this graph, it is good to visualise what I have been feeling. I would very much like to say the F4 FFB is generally very good (the F14 having the best FFB in the sim). Like others have said, the low speed really is an issue as the forces are just not there. I think the compromised solution is pretty accurate, as long as we have some force around 20% at 100 knots. FFB enables us to have a more realistic sim experience, but there does have to be some compromise ad not everything can scale the same. This all doesnt have to be made the only option, as there is of course no harm in having a few options.
Many thanks.
-
There are many things wrong with DCS. But to claim there is an issue with the p51 with no further information is laughable.
I have had the p51 since it's release and there are no such issues. Only technique.
-
54 minutes ago, Graphics said:
Full set of features will be announced prior to early access
And due to this I will not be preordering. I have been bitten one too many times from ED early access.
Will the Chinnok release with LODs as multiple previous aircraft have not?
I couldn't help but notice there was no clip showing crew loading into the aircraft, same with the vehicle. That should be implemented along with bringing that to all the other applicable helicopters in the sim.
I look forward to purchasing, when the dust has settled and it's clear what exaclty is being sold.
-
6
-
-
On 12/13/2023 at 1:07 PM, BIGNEWY said:
We have a report open for the length of time the engine takes to shut down when cut off is pulled, there seems to be a difference with cold starts and hot, I will link this thread to the report for the team to take a look also.
thanks
Just to clarify it's not just the legnth of time (and it's not just the Mosquito). The fuel cut off, or the mixture going to idle cut off, removes the fuel from the engine... So there shouldnt be any backfiring once the cut off is selected.
-
1
-
-
2 minutes ago, =Andre= said:
I saw it before as a result of installing/updating NLR seat software. What can you see in the
SimShaker for Aviators -> View -> DCS Debug window during the mission?
Just managed to fix it, I there there was a conflix with script exporting. Solved now!
-
Hello I keep getting this error in DCS with simshaker.. Any advise? Flying in the Mosquito.
-
Can someone from ED please confirm this issue (with all the merlin aircraft not just the Mosquito) is now being looked into and fixed. Please do not just close the thread as not a bug or reported.
We have clearly raised an issue here and I fear just like a lot of them they fall on deaf ears.
There is no question that the shutdown dynamics are wrong, even the startup ones aren't amazing. This is part of the simulation of these great aircraft, please improve it.
-
2
-
-
Looking at this, I think this is an issue with the game. We should be able to drop below the max hz of the display without stuttering and having those horrid frame timings.
I now have a 4090 and whilst it is smoother. I do get those drops. The gpu usage isn't maxed out either.
-
On 11/30/2023 at 9:49 PM, corbu1 said:
With SSA you can run 6 motors. The NLR software uses the 8 motors of the HF8.
I run it with SSA. I like the helicopter specific effects and can run it simultanously with buttkicker bassshakers.
Yeah i'm aware it runs with 6, hence me asking if there is anyone who could magic into running with 8!
-
I wonder if it is possible to get the SSA working all 8 motors on the hf8 instead of 6. Any ideas?
-
On 11/29/2023 at 3:00 PM, SUNTSAG said:
To be fair I realise no one is/was questioning the shutdown procedure but no one was using the correct one. So to be helpful, I provided the correct documented information.
As part of any route cause analysis, the starting point to determine if there is an issue or improvement opportunity; is to use the correct procedure as prescribed in the pilot notes. Any variation to the actual procedure could potentially result in the issues being encountered. Therefore in the first instance, common sense dictates follow the correct procedure.
Also during route cause analysis a single data point is insufficient to determine that a problem exists and statistically 8 data points are preferable and will potentially highlight a trend if charted. I hope this helps as to why I provided this information. I am not saying there isn’t an issue but I can confirm I haven’t experienced it personally. Cheers.
Sorry but as art has said, is 100% unavoidable if shutting down as per SOP in any merlin aircraft in dcs. So you might be missing the issue that we are highlighting.
-
23 hours ago, SUNTSAG said:
This is my preferred approach to following the documented procedure….a picture paints a thousand words. Cheers.
I don't think we are questioning the shutdown procedure. The point being is that when you still get backfires and splutters when you shouldn't which is an incorrect modelling/simplification of the shutdown process, which applies to all the merlin aircraft at minimum.
-
1
-
-
1 hour ago, average_pilot said:
I agree. The point of the thread is that in DCS the engines are capable of violating the most essential physics and keep turning endlessly without receiving any fuel, which is something worth to look at and fix for the sake of physical coherence of the simulation.
Edit: To further clarify my point, you may damage an engine IRL not following the correct stop procedure but it will surely stop moving no matter what if the fuel is cut off.
Yeah agreed. In other situations with the carbed engines, I have had to shutdown an aircraft by going to full throttle with the mixture in cut off (as it kept running). Which killed the engine as it got too much air. My point being is that it it seems the dcs engine simulation is actually a lot simpler than I initially thought. What is impostant though as stated here, the current shutdown script is wrong.
6 minutes ago, Art-J said:I remember Yo-Yo's post in one of the wishlist threads (for less regular startup and shutdown sequences) where he said coding all idiosyncrasies of fuel, ignition and exhaust during these transitional phases would be a waste of time in combat sim where most of folks just want to take off and blow s..t up. I kind of understand that, because no matter how cool the nerdy-feature is, once the novelty wears off majority won't care about it anymore. So, simplified sequences are here to stay and I can deal with it, even though I use DCS primarily for non-combat flying.
There are, however, some noticeable issues even with these simplified procedures.
To sum it up, there seem to be two scripted shutdown sequences in all Merlin-powered DCS planes, one quick and "clean" without excessive backfire (maybe just a few muted pops) and one longer, "dirty" with excessive and loud backfire. In Spit and Mustang you'll get one or the other depending on engine RPM when mixture cutoff is activated and on moving the throttle lever forward or keeping it aft.
In Mossie, though, looks like you get clean sequence in all hot-started mission no matter what, and dirty sequence in all cold started missions, no matter what. That doesn't make much sense.
Its a shame that this is the case, as like you I rarely actually fly combat and just enjoy the flight model and messing around in VR. I wish the engine simulation was far more realistic in many many ways, this startup issue along with the abnormally high oil pressure in startup playing a big part in my irritation with the sim.
I hold out hope that one day these things will actually be fixed.
-
2
-
-
This is one of the many engine issues I have tried to raise in the past which seem to be ignore.
As stated above this issue spans into almost all of the warbirds (mainly the merlin engined ones). When you shut the engine down you should cut the fuel off, in the aircraft it is usually mixture cut off or similar. In DCS it is as if there is still fuel getting into the engine making them splutter and backfire. Completly unrealistic.
The only way to make it cut off correctly is by turning the maggs off which is not realistic.
-
2
-
-
On 9/19/2021 at 9:33 AM, hazzer said:
That would be amazing, watching the guys go into the gear bay to prime the engines and stood there with a fire extinguisher etc.
I would really love this. It is needed to bring the airports to life.
To add to this, also the ground crew shouldn't always prime it perfectly. They don't always require the same amount of priming!
Still would like this to be actioned.
Following on from this. It should be possible to prime the aircraft off field without a ground crew, since there are 2 crew members and a door...
-
5 hours ago, Dangerzone said:
it looks like you're locked into 60fps (except for when it drops down). Would I be correct in assuming that when it's below 60fps, it's saying GPU bound, and when you're at 60fps it's saying CPU bound?
if so - it looks like it might be locking to the frequency of your HMD. Just remember, it's always going to say either "CPU Bound" or "GPU Bound" - ALWAYS one or the other. If the GPU has overhead room (such as if it could go to 65fps, but is being locked to 60fps because that's all you need) it is going to say CPU bound - even if you have overhead with your CPU too.
Not locked to 60fps, my headset is 90hz (reverb g2) so I have locked fps to 90.
I think it just happened to drop to the nice round number of 60fps. I'm not going to loose sleep over this as I'm sure when the 4090 shows up ill be getting some gains either way.
-
nullHAGS disabled, It appears I now have higher FPS however the game is still bouncing between CPU bound, main thread and rendering thread. Given my gpu load is essentially between 97-100 I would think that it is still limited by the GPU. Anything else I can do to get the most out of my CPU in dcs?
-
10 hours ago, Dangerzone said:
Have you gone through the optimization procedures. Things like ensuring that the clock speed is fixed/set above 5.0ghz (no throttling is going on), disabled HAGS, disabled CPU parking, RAM is running at optimum speed, etc?
It does sound strange that it's CPU limited - but I know with my 13900K I had to do a lot of tweaking in order to get advertised speeds. Straight out of the box I think there's a lot of things (both BIOS and Windows based) that will severely hamper it's ability to perform at it's capabilities.
Thanks for your response, so far I have:
Undervolted and limited the power draw of my cpu so it doesn't burn a hole through the floor. It is able to run at around 5ghz fully loaded. In DCS the cpu load isn't that big so it will be able to maintain 5.5ghz.
I'm using project lasso and enabled bitsum high performance which has prevented the cores from parking. One thing I'm not sure where DCS stands currently is hyperthreading on or off?
The one thing I haven't yet done is HAGS off. Just going to try that now and will report back.
It isn't like I haven't gone into this without trying to change settings and optimise the cpu. Just seems very surprising that it says this, I posted on reddit as well and it has been suggested that the overlay could just be wrong.
I have a 4090 on the way tomorrow and I'm hoping that it does actually allow for some improvement. Fingers crossed.
Prop animations in VR
在 Object Bugs
发布于
This still exists and is an issue.