nice with bugs

[Steel Jaw]

If you would stop watching pron you would not need it:music_whistling:

 

You know as well the PTVCW that pr0n just appears outta nowhere on the net... :D

[EtherealN]

when for example Wags stated the next release would not be a final version only for them to release it as a final version

 

Yup, and you know exactly how many and which versions were being created and tested. Your insight is astounding. I guess I should IP-check to see which other account you have that has access to the internal testing sections? ;)

 

Many here just can't hear a negative thing said towards ED, no one is perfect. It reminds me of Apple users.

 

It's not about negative things. It's about negative things that are plain bullshit. That is when people get riled up. People making statements like the one I quoted you making up there, for example, require a level of insight far beyond what you have - yet you state it with such surety. Where did you get this information from?

 

When people make shit up, other people who care about what the truth is get upset. Nothing strange.

 

If you want to use the apple example, of COURSE Apple users would get upset if someone says "Apple makes crap quality products". It's just not true. They make superbly finished and high quality products. (People like me just don't like the pricetag, compare hardware/price of a MacBook Pro and an ASUS G17 for example, or a regular macbook and a G15.)

 

Also, you need to realize what reality is for a software developer. It really is not an easy life to lead. Goes something like this:

 

 

Men: developers

Women: customers

 

;)

[galagamo]

Vista flashbacks I guess

Whenever I see someone talking about missing textures and CTD's I think yup it's that damn UAC again! Trying to run old programs, on vista, I had my fair share of grief.

[hassata]

Is the stutter problem use-error?

 

This thread, and turning shadows to medium, solved my stutter issue.

 

Edit: forgot the link.

http://forums.eagle.ru/showthread.php?t=68060

Edited March 4, 2011 by hassata

[Nate--IRL--]

32bit can work fine, see my sig.

 

However the system specs state

 

Minimal system requirements

Operating system: 64-bit Windows XP, Vista, and 7

Processor: CPU: Core 2 Duo E6600 or AMD Phenom X3 8750 or better

Memory: 4GB

Hard disk space: 7 GB

Video: Shader 3.0 or better; 512MB NVIDIA GeForce 8600GT DirectX 9.0c or better

Sound: DirectX 9.0c-compatible

DirectX®: 9.0C

 

Nate

[Damage]

32bit can work fine, see my sig.

 

However the system specs state

 

 

 

Nate

 

 

I concur, 32 bit can work fine.

 

On Med-High settings I get 20-35 FPS on the airbase and 35 - 60 FPS in the air. In either case the game runs smooth without stutters.

[Yoni63]

I think 'full of bugs' is an overstatement.

 

Not to flame but have to agree, there's a few glitches here and there. Most of what I see on mine have already been reported as far as I can tell so I'm just hanging out waiting. I'm sure they'll address it. In the mean time, there is waaaaaay too much that we can be learning on areas of the game that are working really well. Something this good isn't going to come out without some bugs.

[Sgt.Baker]

the A-10C Warthog Final Release might sell better in Mexico.

[PhoenixBvo]

My annoyances with an otherwise superb sim:

1): Too many stutters/lag, will try the thread suggested by Hassata, but ED can't expect ordinary customers to know and apply that stuff in order to have a decent sim experience.

2): Toebreaks on the CH Pro pedals remain inverted, whatever I try. This was NOT a problem in the betas. Lua editing (including both copies in C:\users\... and the game folder) is without effect and in-game control setup doesn't change behavior in the sim either.

3): The Wingie still flies straight into the hornets nest when told to attack something with Maverick. He doesn't maintain standoff range to known threats. Or gets too low when using GBUs. Why is that so hard to implement?

4): Warning beeper goes off continuously at starup (known bug).

5): Plane repair. Regardless of damage, when you make a rearm/refuel landing and want to repair, you have to at least shutdown the engines. This causes hydraulic pressure inconsistencies. The dials show values in the green, but trying to raise the gear causes Left Oil pressure warning and later also Right, causing loss of control... (Has been reported somewhere as well)

[bmbpdk]

My annoyances with an otherwise superb sim:

1): Too many stutters/lag, will try the thread suggested by Hassata, but ED can't expect ordinary customers to know and apply that stuff in order to have a decent sim experience.

2): Toebreaks on the CH Pro pedals remain inverted, whatever I try. This was NOT a problem in the betas. Lua editing (including both copies in C:\users\... and the game folder) is without effect and in-game control setup doesn't change behavior in the sim either.

3): The Wingie still flies straight into the hornets nest when told to attack something with Maverick. He doesn't maintain standoff range to known threats. Or gets too low when using GBUs. Why is that so hard to implement?

4): Warning beeper goes off continuously at starup (known bug).

5): Plane repair. Regardless of damage, when you make a rearm/refuel landing and want to repair, you have to at least shutdown the engines. This causes hydraulic pressure inconsistencies. The dials show values in the green, but trying to raise the gear causes Left Oil pressure warning and later also Right, causing loss of control... (Has been reported somewhere as well)

 

1) No answer

 

2) The new config/setup/pilot profile is located at: C:\users\"your user"\saved game

 

3) No answer

 

4) That is because of low hydralic preasure, atleast in my game

 

5) Turn on ground power, shut down engines and that should give you a "controlable" plane (remember that the plane switches on "Ground safe" mode, wich disable some funtions)

But why on earth would you try to raise your landing gear when on the ground?!

[hassata]

4): Warning beeper goes off continuously at starup (known bug).

 

Try this (I haven't myself yet):

 

I've been pulling the "Aux ESS Bus tie" on windy days...yeah, even inside :-)

 

It's the bottom right most circuit breaker. I have no idea what horrible horrible things will go wrong if you leave the breaker out, but I do know one thing: it cuts off the BEEP BEEP BEEPER (among other things).

 

Proabably a really good idea to push it back in after your engines are started. PAC at least becomes disabled, there are probably other systems that rely on that breaker.

[PhoenixBvo]

But why on earth would you try to raise your landing gear when on the ground?!

 

LOL!! No, that would be after taking off again, of course!

Somehow restarting my engines after rearming/refuelling and repair causes oil pressure problems. I follow the complete ramp startup checklist, which works perfectly at mission start. So, why not after a maintenance stop?

 

@hassata: Thanks! Will try that.

[Jinja]

Nate,

 

I can see why that links in your sig (the "bcdedit /set increaseuserva 3072" tip)...

It has instantly solved all my CTDs, texture glitches. Graphics settings have all gone from low to high...

Couldn't be happier.

 

 

maybe there should even be an auto-check in code that:

 

On startup of DCS, IF OS == Win7 AND Installed RAM == 4GB AND bcdedit userva < 3072, show a messagebox recommending this performance tweak?

 

Thx Usul for opening this thread! ;-)

 

:thumbup::thumbup::thumbup:

Edited March 5, 2011 by Jinja

[EtherealN]

Jinja, not an option.

 

The tweak we are talking about is a system-wide change, and does not rely on a given amount of RAM. (It works with adress space, which is similar but different.) Performing system-wide changes to a system through an installer, even with a caution box, is extremely touchy territory.

[Jinja]

For sure, having the installer do the change would be tres bad, but just showing a message box with a link to an online DCS KB-article or similar might lead lots of horses to water...

there must be many other purchasers of DCS titles in same boat as I was and that didn't happen to stumble across this game-saving tip on a random forum thread.

 

Sounds messy though. Either way, I'm happy now.

[hassata]

I've been pulling the "Aux ESS Bus tie" on windy days...yeah, even inside :-)

 

It's the bottom right most circuit breaker. I have no idea what horrible horrible things will go wrong if you leave the breaker out, but I do know one thing: it cuts off the BEEP BEEP BEEPER (among other things).

 

Probably a really good idea to push it back in after your engines are started. PAC at least becomes disabled, there are probably other systems that rely on that breaker.

 

Probably. I spent half an hour and a couple of reboots trying to figure out why the Anti-skid, Taxi Light, and Nose-wheel steering weren't engaging lol. Wut-a-Sim.