Rotareneg
-
Posts
62 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Rotareneg
-
-
With the regulator damaged so that the MP gauge was pegged, even when well below full throttle, there still didn't seem to be any new effects. I tried at various ambient temperatures and engine RPMs and it never smoked.
-
The ships do roll already, there's even a Blackshark mission where you have to deliver a package to a frigate in bad weather while it's bobbing all over the place.
-
From what I've understood, the "right foot forward to turn right" convention became standard as much as anything because of wheel brakes, otherwise you would have to press the right pedal wheel brake while having to press the left pedal forward at the same time.
When I got my rudder pedals (a full CH setup) I too thought the other way seemed more natural as it matches the other controls: rotate the stick back to rotate the aircraft back, move it to the right to roll right, and rotate the pedals to the right to turn right, but you get used to the traditional "reversed" rudder controls.
-
They really need to tweak/fix/whatever the AI for situations where it's up against slow moving targets because, as it is, an MiG-15bis can out maneuver and shoot down an F-15C, and even I can shoot down an F-15C with a P-51D:
eTHEWLjHVHI
-
-
P-51 vs F-15:
-
-
I'm not sure if this is a bug, but whatever it is it really looks strange:
It appears that the models shear vertically as if they're made of rubber instead of rotating when driving over terrain changes (edges of terrain polygons or streams for example.) This only happens if the AI is controlling the unit, if you've taken manual control they rotate as expected.
-
Or just
-
You can use GPU-Z to monitor GPU usage to verify which GPU is actually being used.
-
WWII style accidental ramming:
Next time just make sure it's an enemy plane, not an RAF bomber...
Oh, and try to avoid the utility poles, they hurt:
-
That's not possible, I don't make mistakes... oh, wait. You're right. :D
-
Ok, ran some numbers:
Assuming an aircraft weight of 9200 pounds,
270 rounds per gun (so they all run empty at the same time,) 800 rpm per gun,
45 g per bullet, 3000 ft/s.
The total weight of the bullets fired is 160 pounds, and takes 20.25 seconds. The resulting thrust is 740 lbf.
Assuming the aircraft is floating in space with no drag, friction, engine thrust or anything, and ignoring the expanding gases from the powder, the aircraft will recoil 530.6 ft by the end of the 20.25 seconds, and end up moving backwards at 35.7 mph.
-
That page is laughably wrong as it assumes that the plane somehow expends all the ammunition instantly.
-
Try starting the setup.exe as an administrator (right click on the icon and select "Run as administrator".) You might try checking the MD5 hash on the files you downloaded to make sure they match what the site says they should be ( http://www.digitalcombatsimulator.com/index.php?scr=product&ProductId=4&end_pos=135&lang=en ), or else just use the torrent link to download them which should insure the files download correctly.
-
Great, now you people have made my engine start seizing! ;) I was practicing taxiing, take-offs, and landings, and was having no engine problems until, while lining up on the runway with the engine at idle, it suddenly seized. No overheating or any other indications of trouble, just... WHAM!!!
-
Slap Chop, my guess would be because you were moving the throttle too fast and because you left the prop control too low.
Also, you need to hold the radio key down while the pilot is talking.
-
I had this happen while watching an AI only fast mission I generated and then edited a little. At one point an SU-30 fires at an A-10 who eventually jettisons his stores when the missile gets close enough, but one GBU, instead of falling like normal, goes through the A-10 and accelerates away at high speed. This happens at around 173 seconds into the track.
-
The attached track of a flight I just made from Vaziani to Batumi seems to play back fine on my end, perhaps you can find something I did different that could explain why your engine seized and mine didn't.
-
I just refueled successfully for the first time myself, filling back up from 25% to full with three disconnects, and including refueling during a turn, and I hadn't practiced for months! :D
For me the hardest part is controlling the airspeed, mainly because the engines react slowly and because I don't have a full sized throttle, just the tiny one on my MS FFB2 stick which takes the most minute adjustments to keep connected.
-
The controls just seem extremely twitchy without curves, but I gave it a try and managed for the first time to complete an A-10 refueling (25% to full) and only had three disconnects, so I guess I mustn't be doing TOO bad. :D
-
I had been just using the FFTest.exe that is in the DCS /bin folder to reset the centering forces after starting a mission, but that simFFB is nicer, thanks. However, it still doesn't help with the fact that you need to alt-tab back to the desktop to run it every time you start a mission in DCS, which is my complaint.
-
I'm using a MS FFB2 stick, but prefer to leave force feedback off for the A-10 and P-51 as the trim effect doesn't seem to work very well when using curves on the axis sensitivities, which leads to another problem: DCS turns off the joystick's default centering spring effect when FF is off, resulting in a rather limp stick... :joystick:
Perhaps DCS could be changed to leave the centering spring effect on when FF is turned off?
-
Okay, I'm seeing now that one really needs to keep an eye on the engine management gauges throughout operation of this aircraft, as temperamental as the engine seems to be.
I was just flying the challenge campaign mission in which you are tasked with navigating hundreds of miles from one airbase to another over the Caucasus mountains. I was at about 15,000 feet, flying with my RPM, Manifold pressure, fuel pressure, oil pressure, and oil temperature in the green areas, when seemingly for no reason my engine seized, just as it did in the previously discussed dogfight mission. My oil temperature had been above the green zone at times, particularly when my airspeed was around 150-175mph in climbs, but (I think) not for too long of periods.
What the heck is going on here? Does going above the oil temperature's green zone cause irreversible damage to the engine, regardless of how much and for how long??
It does seem that the automatic oil cooler control tends to keep the oil temperature rather high, so I've taken to just manually controlling it if it gets above the green arc. I'm not sure if it's actually a problem however, perhaps it's perfectly normal and safe for the oil temperature to hover near the red-line, I don't know.
As far as having the engine seize up, running at low RPMs can be tricky unless you are really careful with the throttle and manifold pressure. The green arcs on the RPM and MP gauges are more for cruising, and on that particular mission you have to climb pretty steeply so you'd do better to run near the maximum continuous power settings of 2700 RPM, 46" MP.
P-51 crash due to cold air temperature
in Game Crash
Posted
In 1.2.16.38741, starting a mission in the cockpit of a P-51 on the runway with low air temperatures (tested at -30 and below) will crash DCS. Attached is an archive with the mission and crash files.
crash_files.zip