Jump to content

Recommended Posts

Posted

well I'm getting 14 to 15 FPS on P51D, this v6288.

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||

  • Replies 692
  • Created
  • Last Reply

Top Posters In This Topic

Posted (edited)

I'm still having a blast with standalone version 1.0.0.9. A constantly smooth-running experience with frames consistently at 34-60. No stutters, no crashes, no frustration. World is nice and pretty, but the 10- fps during explosions is just too much of a compromise.

 

Huge props to ED on the progress though!

Edited by rockyalexander
Posted (edited)
please correct mig-31 pylons

 

and the nose gear too, please. . . it still doesn t touch the runway while taxying. . .

Edited by flanker1
Posted

F-18 Rudder Surface animations are backwards.

 

Centerline Fuel Tank goes through gear doors

 

IR/Target Pod goes through Engine intake,

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
I'm hardly seeing a bright future unfortunately.

 

The only thing clearly broken right now is MLRS salvos slowing the framerate to a crawl. Other than that the sim is running very well for me, and all in all certainly much better than either v1.1.1.1 or v1.2.0 ever did. So I'd rather say the future is BRIGHT if anything :thumbup:

 

And what's with the doom-mongering anyway? As someone from the team already stated somewhere, it's not as if the devs just sit on their arses and play gin rummy all day long. They're aware of the problems and constantly work towards fixing them.

The DCS Mi-8MTV2. The best aviational BBW experience you could ever dream of.

Posted

Flying the Mustang, low over cities and mountains, maxed out I get a solid 60FPS with vsync. That is great. A-10 and Ka-50 cockpits eat more FPS however. And of course this is a combat sim, so AI reduces frame rate and once things start going boom I get a slide show.

 

The new effects are hardly optimised. I also think they are overdone: the .50 CAL hitting ground looks more like a 20mm cannon (tracers too) and Vikhr missiles (shaped charge AT weapon) produce an explosion the size of a bomb.

 

The new explosions just need to go, or be reworked to look more realistic and be less taxing on the hardware. The next logical optimisation should be moving AI to another CPU core.

Posted
The new effects are hardly optimised. I also think they are overdone: the .50 CAL hitting ground looks more like a 20mm cannon (tracers too) and Vikhr missiles (shaped charge AT weapon) produce an explosion the size of a bomb.

 

The new explosions just need to go, or be reworked to look more realistic and be less taxing on the hardware. The next logical optimisation should be moving AI to another CPU core.

 

Seconded.

 

Major bug with 6288 is just that - effects: high rate of fire will crash the game, CBUs will kill FPS and it all looks worse than in 1.2.0 when IMHO they got it just right.

 

Not to mention the black buildings in TGP.

P8Z68 | 2500k @ 4.5 | GTX 1080Ti | 2x8 GB @ 1600 | TM Hog (extended 7cm) & MFG Crosswind (S/N 007) | TIR v5

WWII bomber formations | DCS P-51D: [TEST] TO distance / gross weight / temperature

Posted
Seconded.

 

Major bug with 6288 is just that - effects: high rate of fire will crash the game, CBUs will kill FPS and it all looks worse than in 1.2.0 when IMHO they got it just right.

 

Not to mention the black buildings in TGP.

 

maybe on your system but not mine....

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||

Posted (edited)
maybe on your system but not mine....

 

Don't get me wrong, the overall FPS is close or almost as good as v1.1.1.1, just the effects are killing the fun occasionally.

 

Both the black buildings and high rate of fire crashes (see post above yours for example), have been reported many times already.

Edited by T}{OR

P8Z68 | 2500k @ 4.5 | GTX 1080Ti | 2x8 GB @ 1600 | TM Hog (extended 7cm) & MFG Crosswind (S/N 007) | TIR v5

WWII bomber formations | DCS P-51D: [TEST] TO distance / gross weight / temperature

Posted
Don't get me wrong, the overall FPS is close or almost as good as v1.1.1.1, just the effects are killing the fun occasionally.

 

Both the black buildings and high rate of fire crashes (see post above yours for example), have been reported many times already.

 

black building what system and what video cards. I play KA50, and P51D haven't seen any black buildings. Might be profile setting need tweaking in the video cards?

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||

Posted

I wished this wasn't moved here. I liked having a thread with info about all the micro-updates right in DCS: World. =\

 

I get the black buildings also via the TGP. One other thing that bugs me is the buildings flickering when you get close. I'm told they always have done that but I'm noticing it more lately.

Intel i5-2500k @ 4.4GHz w/ H70 liquid cooler, ASRock PRO3-M Z68 Mobo, 32G 1600Mhz Mushkin RAM, EVGA GTX970 4GB , OCZ Agility 3 128g SSD, SanDisk 240g SSD, Win7 64-bit

--Twitch: http://www.twitch.tv/livingfood --

Posted
Specs in the sig, game: A-10C - black buildings only when viewing through TGP.

EDIT: Alt-tab related I'm told.

 

Well, whatever they did to the Alt-Tab, I'm now able to Alt-Tab without the program locking up.

Posted

At least thats a plus. :)

 

In v1.1.1.1 I used to lose HRD when using alt-tab, now I get black buildings. Looking down into the pit and pausing the view before alt-tabing would have prevented the loss of HRD but there is no workaround for black buildings.

P8Z68 | 2500k @ 4.5 | GTX 1080Ti | 2x8 GB @ 1600 | TM Hog (extended 7cm) & MFG Crosswind (S/N 007) | TIR v5

WWII bomber formations | DCS P-51D: [TEST] TO distance / gross weight / temperature

Posted
At least thats a plus. :)

 

In v1.1.1.1 I used to lose HRD when using alt-tab, now I get black buildings. Looking down into the pit and pausing the view before alt-tabing would have prevented the loss of HRD but there is no workaround for black buildings.

 

 

Well, at least its an improvement. Lets hope the next patch gets rid of the black buildings.

Posted (edited)

[EDIT: answer to a now deleted question from GregP]

 

You are talking of a different bug that isn't fixed up to now...

 

Serious: I have a hard time to understand why ED decided to have the "Aero interface Off" by default right after installation, as it causes so much trouble for the end-user that isn't aware what this does.

And if he wanted to find out...He cant!! -There is NO GUI manual that tells what this option is about !

Yes ED, sometimes I think that you don't have a working QA at all.

 

-anyway-

your answer is here: >>>

Edited by PeterP
  • Like 1

Posted

/Thread cleaned up.

 

Gentlemen, kindly leave the bickering off the boards. If you simply cannot, then do so respectfully via PM, keeping in mind that forum rules apply equally to the Private Message system.

 

Ta

Novice or Veteran looking for an alternative MP career?

Click me to commence your Journey of Pillage and Plunder!

[sIGPIC][/sIGPIC]

'....And when I get to Heaven, to St Peter I will tell....

One more Soldier reporting Sir, I've served my time in Hell......'

Posted (edited)

OK - once again:

 

Question:

Why is the option" Disable Aero interface " checked On by default after a new installation , even if it is well known that this causes a serious bug in the simulation , so no click-able item will work properly ?

 

This only needs a edit of a entry in the DCS World\MissionEditor\data\scripts\optionsData.lua of the default settings.

 

Ok- It will not fix the problem at all , but it will prevent that it happens in the first instance for many people.

Every day there are new posts of forum members that are desperately asking for help.

 

And many have wasted much time already and even reinstalled.

And members/Moderators are answering the same questions on and on.

 

"Fixing" this via a Micro-update will may not help these that have already installed and run it for the first time, as it is already written down in the "saved games".

 

But it will stop it for everyone that is installing DCS in the future because they run a update automatically while the first run.

 

Why?

Edited by PeterP

Posted
Why is the option" Disable Aero interface " checked On by default after a new installation

 

IIRC, so not having it activated by default is causing crashes for the whole software right within the loading process of a Mission. I think that was related to some MFCD requirements which wouldnt be able to run with activated Aero surface in the background. I dont know whether this is correct, I might be wrong.

Posted

No - this isn't the reason.

Never had it and never read about it.

 

And on the other hand , even if this is true:

 

Disabling Aero just to prevent some crashes - just to be faced with a inoperable mouse courser in Win7 during the mission.

I miss the logic behind this.

Posted (edited)

I know . but when you are disabling Aero (and also functions of the WDM drivers), it will also make a GPU crawl while running DirectX applications in windowed mode in Win7.

...and there are more things -but this isn't the point. (Disabling the render at all will also save performance and free up you total V-ram)

-anyway-

 

I'm still searching for a answer that tells me why it is advisable to introduce and use a undocumented option that brakes a crucial function of the program, instead to leave things as they are and only introduce them if there are no problems with it?

Edited by PeterP

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...