Limaro
Members-
Posts
292 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Limaro
-
When having a lot to setup, and multiple controllers, it's a painful scrolling, checking, testing (when they ar enot well named). In order to make the controller configuration more comfortable, it would be great to have one column with which you can work to manage setting up new inputs. Just by automatic recognition of what controller made the input. Anyhow, this is actually the way most games I knew do it. Having one column, in which then the button assignments are listed with corresponding controllers. But for the current purpose it would already be great to have that auto column. Or, secondary Idea: When chosing the wrong controller, pressing a button, DCS could see that and offer a "Ok, then assign this button from the other controll".
-
Seams really to work. Thanks a lot
-
Which ingame settings are you running?
-
Anyone else noticed increased CPU load after few last patches?
Limaro replied to Youda's topic in Game Performance Bugs
The general performence went better with last patches. However, I've heared from people using VR that it became unplayable. Also, that it came with 2.7.11 - in combination with SteamVR. You could try VR alternative to steam. : -
I would say your CPU from 2015 is the limitting factor. But I dont have any good explaination why the monitoring you showed did not look like as if. General Idea: Switch off addons like TacView. This costs me most performance in larger missions. If any addon is responsible can be easily checked by just renaming the C:\Users\<user>\Saved Games\DCS.openbeta\Scripts - folder. also post your last dcs.log file in C:\Users\<user>\Saved Games\DCS.openbeta\Logs together with DxDiag in order for ED to easier verify your case.
-
Being here just with my phone, short quick things to check: - rename your Scripts-Folder in dcs saved games. Just to verify that tacview or srs are steeling power (especially as yor pc is not extremely performant). - Check with the performance overlay of nvidia which of Gpu or Cpu workload which of both is limiting factor. That may help to see the bottleneck. Edit: question: du you have 3 Memory Bars?!
-
2.7.11 still wiping the coordinates Pleaaaaaaaase fix this
-
Does someone have this activated and can tell how the impact on performance was for DCS? I did so, and had a loss of performance... can't tell why. So I am curious for other experiances.
-
One 28" 4K display vs Three 1440p displays (or large curved 1440p screen)
Limaro replied to lwalter's topic in Home Cockpits
Personally, I'd suggest to use the 4k one Screen. The reason for that thinking is my experiance I had with VR: For me there the main immersion gain came with the larger vertical field of view - and not the horizontal of having three screens. A friend of mine uses three screens, but arranged VERTICALLY. This tells me that he had same feeling About performance, just calculating.. I'D say that 4k is more performant than 3*1440: ~11 M vs. ~8.3M Pixels. -
Only getting 2fps and about 10% GPU utilization
Limaro replied to MuscleMarker's topic in Game Performance Bugs
Very glad that it helped. If I would guess, I'd say it's the Scripts folder. That already caused some issues an my PC. After "restoring" them, with newest versions (Tacview, pw-dev, etc...) it worked also still well. -
correct as is Artillery not fireing on point, when over 2.2nm away
Limaro replied to Limaro's topic in General Bugs
With my very initial post and mission, there was another type of artillery. They did fire immediately or not at all - and that for me, not obvious reason. But this other type.... Needs 3 minutes. -
correct as is Artillery not fireing on point, when over 2.2nm away
Limaro replied to Limaro's topic in General Bugs
Wow, that was a simple solution, thanks a lot -
correct as is Artillery not fireing on point, when over 2.2nm away
Limaro replied to Limaro's topic in General Bugs
I have to reopen this. I tried everything. but artillery is never fireing. independet from what type, distance, direction or anything else. maybe someone can help me. Mission attached. Artillery Issues.miz -
Hi, I was retesting some things for runway attacs for a mission - to take out runways. The results with all GB31-V1-4 were... ludicrous. Did this happen with the last Patch? See Screenshot the pothole... Even on our streets we have more bigger ones Also with the AGM-84... sometimes, they are smaller than the weapon.
-
Only getting 2fps and about 10% GPU utilization
Limaro replied to MuscleMarker's topic in Game Performance Bugs
I have some questions and suggestions: 1. Did it happen with the latest patch (2.7.11..), and before it was ok, or did this suddenly happen? 2. Does it also happen when creating a very basic mission in Caucasus, using a SU-25T, and not a F16? (Later question will point on this) > In log file it looks like you play the liberation mission. Here in performance part of forum I heared a lot about issues. 3. Can you Install the stable version? (not with all mods terrains or modules, just the core game) 4. Did you really clean the install ? I ask, ss the TACVIEW is still active in your posted log file..? 4.1 Just rename the Saved Games folder once, to check if it behaves differently: (C:\Users\<user>\Saved Games\DCS.openbeta_BAK) 5. Is your windows up to date? Refering to question 1. > Check your energy management and ensure maximum performance. > Check game mode or HDR is deactivated. 6. Maybe try in non-fullscreen mode. just curious if it changes something. generally, play with settings and check if anything changes. -
high-end system performance issues -- stuttering
Limaro replied to dmatsch's topic in Game Performance Bugs
What are the real values, without vsync? After having bought a new graphic card, I also thought it would make sense to activcate it. but in situation where without I am getting stable > 80FPS, it still drops down to 30. -
Deactivate VSync. This drops also my fps too much. Even when I would get 80FPS it drops down to 30. Also I checked your settings now from my pc (previous post from smartphone): - Set Shadows to middle, and terrain Object shadows to flat. This sould increase Performance in general. - Then you'll be able to test, if Preload Radius has to be that small, - also I never observed much difference to Anisotropic 8x to16 (I have 8 only). What can also help a lot, is to deactivate the wake turbulance from the gameplay tab.
-
Glad to here that deleting the caches helped a bit. Did you also deactivate the special graphic card options from Adrenalin software? There is some sharping, scaling etc. which was by default activated on mine. Please also post your ingame graphic settings to get a better feeling. Also, what is your CPU und RAM? What I also recommend is to show the overlay metriks from Adrenalin and observe (post here) the load of gpu, cpu and ram while flying. are all maps affected?
-
I recently updated from 2080 Super to 6900XT and got the same experiance of unexpected bad performance at the beginning. Try: - Delete content of C:\Users\<user>\Saved Games\DCS.openbeta\metashaders2 - Delete content of C:\Users\<user>\Saved Games\DCS.openbeta\fxo They will be regenerated automatically Also, if you have active scripts, rename the folder C:\Users\<user>\Saved Games\DCS.openbeta\Scripts to something else, to make sure that they are not loaded any more. Espacially the scripts seamed to me causing a drop of fps, feeling like a chain of micro stutters.
-
Ups. I made the screenshot, resized it in paint and .. then forgot to upload.... Here are my settings: Hohe,Hoch = High, Aus = off I have three extra screens with 800 x 1280 (vertical), which leed to that resolution. Main Screen is 4k. EDIT: I made this whole performance stuff, as after update performance dropped enormously including many micro stutters. But Reason was: Deprecated or faulty Scripts. After deleting (and installing most recent), everything worked then even better - which first was suspicious to me
-
Good afternoon, as the performance topic is mostly boils up when it's getting bader, I wanted to open this topic to thank ED for the good work - of this time increasing Performance quite noticable. In my benchmark tracks in Caucasus and Syria, I got these changes: Caucasus 2.7.10 - 74.7 FPS 2.7.11 - 82.5 FPS + 10,4% Beirut (Syria) 2.7.10 - 72.5 FPS 2.7.11 - 78.8 FPS + 8,7% I am curious, if other also experianced this changes - Maybe, with many datasets, we can all help to keep development going in that direction My PC in short: Ryzen 7 3700X, AMD 6900XT, 32 GB RAM, Windows 10 Regads DxDiag.txt Performance_Fly_3_1_Caucasus.trk Performance_Fly_4_1_Beirut.trk
-
Dear ED Team, Whish: A button to show the selected unit in the encyclopedia directly. Alternatively: Showing the information from encyclopedia in a new tab on the right (beside waypoint, amunition, and so on) Also a way to see, what missile a unit shoots would help a lot. Also with link to jump directly to this type.
-
+like I, didn't think about that workarround. It's better then Slewing, but much less efficient as if too would work as expected.
-
2.7.10 still there... How is it possible, that nobody bothers about that - Nobody using JDAMs on F/A 18 ? Do you guys always slews after the drop a bomb to the next target? Without that bug, it was possible, to Orbit the target area, and "save" the targets into the TOO stations, and than with one run, attac up to 8 target at once. this is giving incredible advantages. Espacially when flying towards targets, and attack all at once. When slowing after dropping the first, you are risking to come too close. Please ED, it's just not a really new function, it's only NOT to clear the memory... . Or is there at least a "Trick" to avoid wiping TOO memory when undesignate? Or another Trick, to populate the PP stations with coordinates from the targetting-Pod? (Like shown in a older Video here:https://www.youtube.com/watch?v=Np-TWdfFHV8&t=227s)
-
correct as is Artillery not fireing on point, when over 2.2nm away
Limaro posted a topic in General Bugs
Hi, AI placed artillery units are not fireing on a specific point (with zone) when they are over ~2.2 nm away. I tried two different, and they behave the same. for both, the range should be ~11nm, according to the red circle. I've attached a mission, in which two placed units (copy paste after setup of waypoint options). First is at about 2.15 and the second at 2.2 nm. EDIT: Added mission file Bombem_Nebel_Visibility_Test.miz
