Insanatrix

Did you try china hat aft short with the TAD selected? No idea if it works but it might.

You can get tearing above below and at 60fps steady. Vsync sync's the rendering of frames to your monitor's refresh rate. I only get like between 16-38fps and get tearing like crazy without Vsync enabled.

I believe AFAIK whatever UHF frequency you set in the ME will be preset 1 on your UHF radio. IT wont default to it though on startup you have to move the dial over to preset mode and select preset 1 unless you do a runway start.

graphics.cfg file under the config folder. under DisplayMode you will see { resolution = {800, 600}; bpp = 32; fullscreen = 0; aspect = 1.333333333; sync = true; Interface Make sure sync = true is set and Vsync should be enabled.

To each their own, I'm not saying I haven't seen "Yahoo's" before but I try not to let 1 or 2 people make me feel ill about the rest.

Vsync actually sync's your FPS to your monitor's refresh rate. Not just 60fps. meaning it displays 1 frame per refresh cycle. Just limiting your FPS to 60 fps or under is not the same as having Vsync enabled. Tearing is simply the simulator drawing and displaying a frame in between refresh cycles of your monitor. You can get tearing with 30fps, there is just less chance for it with lower frame rates as there is less of a chance for a frame to be rendered in the middle of a refresh cycle.

Useful information, thanks for sharing.................. Seems like a good initiative towards getting a more open multiplayer community. One thing I run into alot is that TS info usually isn't given in the mission briefing. Usually if it is I try to log on to it.

It's an interesting idea in that you can buy 1 or 2 planes that you want and you don't have to buy the full game.

You can change UHF frequency under the main tab where you specify number of planes in the flight, there's a tab right above the skill selection that says frequency.

Generally it defaults to 251 for player flights and 124 for AI?

Not if it has been reset or just flipped from STBY to A-G mode.

There's nothing wrong with knowledge unless you choose to flaunt it over someone in a condescending or one-up manner. It doesn't help them or you and doesn't serve much of a purpose other than personal gratification. I guess it depends on your definition of eliteist.

It was there a long time ago. My guess is the Apache was going to be a module based on data ED had acquired but was not an active project for the military. Then the A-10C DTS came along and it got pushed to the backburner. Possibly the new US Jet they are going to model for the next module may also be tied to a defense contract of some sorts. Hence why it is being pushed ahead of the Apache. If they are going to have to create a DTS for the military it's alot easier to port that over to an entertainment product rather than work on that and try to produce an Apache module as well.

Same, I love the Shark more than the Hog. I'm really just waiting for the compatibility patch for the Shark. I do like learning the systems for the Hog though.

Just wanted to say Nate I love that new Hard preset. It has the blur from the old beta HDR but it's not as "fuzzy" and while it does somewhat lower the contrast it's a fine tradeoff.

Thanks nate I will try it out.

I'm liking the Hard preset so far just due to the vibrant color scheme it seems to give. Normal and Soft almost give a washed out look. Is there any way to get the Blur from the Soft preset into the Hard preset?

Yeah it says that to me as well for most people I try to rep. I gave up using it haha.

NP! :thumbup:

Switch from HARS to EGI on the Nav Panel.

Somewhat related but is there a way to adjust the 5 seconds it takes to autohide maybe down to 2-3 seconds?

Is that why I get weird flickering black boxes in my TADS display seemingly random?

You would be amazed how well a tan tank blends into tan sand :P

Sure it's bottlenecked at the CPU. Basicly your cpu is queuing information to process in cache and processing it when it can which creates overhead which in turn creates a "slow down". Split all the threads up now and stripe em across 4 cores. The threads still have to talk to each other. Physics need's info from input and graphics needs data from physics and sound needs data from input etc... What happens when the Physics thread calls for data from Input and Input isn't done calculating the data? or Graphics issue's a function call to the physics thread and it's working on calculating something else? Guess what, It still gets queued, you still have overhead. Why do you think every game out there isn't optimized for multi-core's even though they've been around for what like 5-6 years? Even the one's that are truly don't even utilize all the core's effeciently. There's no easy way to get around it.

oddly enough just because a program can use 4 cores doesn't mean it's using them effectively. Granted you can possibly seperate the different systems like physics, avionics, ballistics, sound, graphics.. etc into seperate threads and then hand those off to different core's for processing. A big problem you run into is when one thread needs something from another thread that isn't finished. Say for instance the graphics thread needs an update from the physics thread on where a missile is so it can render it's position. That's rather a simple task but imagine what the phyics thread is doing processing all the calculations and roll angle's etc... You would basicly be in the same position you are in right now with apps that use only 1 core. So yes all 4 core's can be used but is it really any more efficient than 1 core?