AussieFX
-
Posts
166 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by AussieFX
-
-
Thanks mate, I just paused it and thought I would check in to see if there's a solution.
You're a lifesaver!
Oops in reply to ariyaner
-
Yeah, same problem.
Is it all the quick missions broken?
It's a shame, I enjoy this bird.
At least they are working on a fix.
-
Worked a treat.
I was just about to give up on this module and all it was, was curves.
Funny thing is I don't usually have curves set with the helicopter modules.
Cheers!
-
I've had the same problem with my G940.
Will try removing the curves, thanks for the tip!
-
The TF-30 is an interesting engine that's for sure. It seems it was one that required the right airframe and even the right inlets to perform.
It's interesting reading how troublesome it was in the F-14. I would love to know when pushed how fast a TF-30 powered F-14 really was.
-
Disagree.
Nevada is destined to integrate with the "public" version of DCS. I'd rather have the problem identified and corrected now before the unification of Nevada.
What is being said is we "might" be able to get the aircraft to work in Nevada without the radar if the bug can't be found soon. Not that they would stop searching for the bug in the meantime.
It's just a way of getting to fly the Nevada map whilst they continue working on the fix.
-
Something with our radar code is interacting poorly with Nevada (or, vice-versa) -- thus the sim crashes when the radar is on. This seems to be a more complex problem which reared its' head just recently.
We're working on a fix. Worst case scenario, initially the aircraft may work when cold starting (no radar) and crash if you turn it on, in lieu of a full fix.
Thanks for the update Nicholas. :thumbup:
-
Any update on progress with the patch?
-
Hi, since the 1.5 update and now in 2.0 my x+y axis (roll and pitch) have become ultra sensitive.
To the point where it's unflyable, even the slightest twitch will send me out of control.
I don't normally use curves in any modules but it's so bad in the F86 I've had to drop the sensitivity of both axis to 50% and now it feels like a flying brick.
I didn't have any control problems in 1.2.x.
I'm using a Logitech G15. FFB.
Anyone else noticed a change, has there been a change?
Thanks.
EDIT my hotas is a G940 not G15...duh! Too much Logitech gear here.
-
The T53-L13B in the UH-1H has dual-orifice fuel nozzles. The primary nozzles open automatically around 8-12% N1 and the secondary around 32% N1 from memory.
This ensures that there is sufficient air running through the engine prior to the introduction of fuel, without the need to modulate the throttle as per some other turbine engines.
As per the FM/CL the throttle should be set just on the decrease side of the idle stop prior to starter engagement. No modulation of the throttle is required for a normal start.
The starter should be held until 40% N1 or 40 seconds, whichever occurs sooner.
There is no two minute warm-up period for the UH-1H, there is a two minute cool-down for the shutdown.
I don't know how the DCS version is modelled, this is for the real UH-1H.
- Horsey
Cheers.
Never operated a T53, pretty much the same as most I've operated it seems (C20's, Arriel mainly)
IIRC the 2 minute warmup was a company requirement.
I've been wanting to shoehorn a time expired T53 into my ski boat for years. :D
-
How about night flying?
That's where my logbook is not working.
-
Seen in my sig below, I run with 32GB of extremely fast RAM serving a CPU humming along at 4.6 GHz and two graphics cards in SLI. If I fly downtown LV, I get about 6 fps with everything set to max. I get 120 fps with everything set to off or low. If I fly up high and out in the desert, I usually get around 90 FPS with everything set to max.
In an anomaly, I had once set everything to max and began reducing things to see what was causing the death of the FPS. The first thing I cut off was Distance. Downtown LV gave me in the 80's FPS with everything set to max. I said, "Eureka!" I turned the Distance back to max and, of course, got the 6 FPS again. In a proof of fix, I returned the Distance to zero again. Unfortunately, the FPS did not return as I had thought. My 80's FPS was an anomaly.
I cannot stress enough that this release of 2.0 is in Alpha stage and will... repeat... will have some crippling bugs for a while. It is to be expected. Above all, IT'S HERE! We just have to let the cake cool until we get to eat it!
Something wrong with your puter champ.
I don't have any problems at all in LV, always stuck on 60 using frame rate control and I'm only using an old 290X with no overclock.
All settings on max 2560x1440 DoF off.
-
I have noticed that any night flying is also not logged in any of the modules or as a total.
Once the sun goes down the logbook goes off to bed to awake again in the morning. :)
Anyone else seeing this?
-
My post is saying don't touch the throttle DURING start. As in if you are touching the starter button as well as fiddling with the throttle, you're wrong. The way I learned is set to idle before you press start. Then once temps and pressures are stabilized move to fly. But that's how I do it. Never had a flame. That's also how the computer does it for autostart if you watch. Maybe the book procedure is different
No. Doing that will get you a molten lump of exotic metals.
You need air running through the motor before adding fuel.
IRL you let the engine idle for 2 minutes before rolling the throttle up. (slowly)
Same with shutting down. Idle for 2 minutes.
Procedure should be, gas producer to 12% before adding fuel, lightoff, keep the starter engaged until it hits ~50%, (gas producer should increase to ~60-70%[unfamiliar with the T-53]) idle for 2 minutes, then throttle to full.
Beep until the power turbine stabilises at 100%.
I use the home key to engage the starter, then use the mouse wheel to roll just past the idle stop and then roll it back down to idle once the motor has reached lightoff.
My guess is the fire is being caused by getting off the starter too early.
Something has changed WRT temperature modelling in the Huey, it seems to me it's a work in progress and this flame is the first step.
-
There's no need to make a new thread about. this.
http://forums.eagle.ru/showthread.php?t=153737
We already have a discussion going on and so far ED has not responded
SLI and Crossfire are different beasts.
-
30 hours and only 4GB to go...
You chaps really shouldn't be complaining about 10 hours, there are some suffering far worse than me too.
Thanks for the write-ups though, it appears there's no memory leaks, major bugs?
-
zero seed zero peers
Same.
-
Good on you for doing this.
I'm currently getting 6kb/s.
EDIT: Typo...6KB/s
And only 5 seeders.
-
I've been searching for about an hour and a half now but can't figure out if I need 1.5 installed before NTTR. Also for us so unfortunate in rural America with slow download speeds and monthly data limits (20gb) is there any way to install piece-by-piece on another mobile device where faster Internet is available, and then install all later like dcs world 1.2 could be? Help...?
Sounds like Australian internet. :music_whistling:
Just returned from Cambodia where it has gigabit internet. While we have dialup like crap! :cry:
Currently getting 6Kb/s. I got better than that on PSTN.
-
No. As soon as the download is done the installer stops seeding. There is no way to continue seeding after the installer closes.
Trust me, I asked - I wished I could have continued seeding throughout the night for everyone.
Mine has hung on disconnecting from the swarm, the updater won't close so I can't proceed with downloading the terrain.
Any ideas, restart maybe??
-
Wow it took three pages to get the correct answer! :)
We nearly got there on page 2.
-
As said, it depends on FOV. You set FOV yourself effectively by using zoom. If you set your FOV to a "realistic" setting in accordance to your monitor, you will feel like looking through a straw but the runway will look like you know from reality. So there is a tradeoff due to the fact we only have a relatively small monitor. This is simply a fact of life, sometimes you need to compromise. Or get a huuuge projected screen or VR.
Damn I just lost a long post on peripheral vision. Grrr.
Anyway, years ago a mate invited me to the Qantas 747-400 sim at Mascot for a few hours and what is essential is peripheral vision.
I had a discussion with an owner at a scenery forum once and was promptly banned when he stated 3d was the second coming and I disagreed. :megalol:
My chopper used to like blowing landing lights and at night it was so much easier touching down on the runway using the edge lighting for altitude reference. Quite disorientating landing off airport using a next to useless taxi light. It's amazing how much we subconsciously rely on our peripheral vision.
I find that when I'm vertical in jets in DCS I'm always turning my head and looking out over the wing for references.
I doubt VR will help. AFAIK it's using the same 16:9/16:10 aspect. I have never tried occulus rift though.
-
Roughly 3.3 feet to a metre.
1000m (1km) ~3300 feet or so.
3000m is close to 10,000ft.
1.6 km/h is 1 mph.
1.604 to be exact.
A rough rule of thumb.
-
Hi just purchased FC3 in the sale, it has downloaded fine but when I look at my download folder it is marked as; "This program is not commonly downloaded and could harm your computer"
MSE hasn't detected anything but it I do have a message saying it's unsigned by the author.
I'm not overly concerned but thought I might check if anyone else has seen this. I own pretty much all the modules and haven't seen a warning such as this before with DCS products.
Spring Tensio 2.5 not working
in DCS: Mi-8MTV2 Magnificent Eight
Posted
Can't find the trigger point in the 2nd mission.
Outpost on top of the hill (can't recall it's name)
I landed between the tent and AA gun - no joy.
Anyone found it?