Limaro

Wow, that was a simple solution, thanks a lot

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.

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.

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)

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

Hi, thanks for you feedback. No i checked, and I am not in Easy mode. Also, the fligpath marker is looking to the ground. Here a screenshot, in which I assume, that it should work (doing the training):

Hi, this might be a stupid question, but somehow I got stuck, doing the tutorials. I am doing the M13 Sensor and taret deisgnation tutorial. - I managed to create a waypoint - I can designate it, and slow the diamond. - without designated Target, Switching to INS mode (Seonsor control FWD) Shown on MPCD, and the TDC press - I cannot do anything. I unterstand it, that it should create adiamond arrond the Flight path idicator, but it doesnt. what do I do wrong?

I found a solution, not the real error. Just for all: Do not load the moose.lua with "Mission Start" event. I may lead to problems. Just make no event, I also included now some seconds delay before moose and some more seconds for my mission script.

Hello everyone, I become totally desperate. I was starting to make a test mission, using moose, to test several things. I already tested successfully some test missions from the Git page. And now I wanted to start my new mission, adding a new menu. And this fails, since hours, and I cannot tell why. This is my whole script (reduced to the actual problem): local radio radio = MENU_COALITION:New(coalition.side.BLUE, "NewMenu", nil) When loading this script, I am getting this ingame: I am using the latest moose.lua (2.7.8). it's being load at mission start. My Script is loaded when more than 5 seconds.

Ah ok. that was a quite unexpected soolution. thanks for that. Do you also know if there is a way to adjust the font weight shown? Everything is so fat. (I observed that the displays in my main screen automatically increase font weight when moving head backwards, and gets thinner, coming closer. so i hope that this is adjustable. By screens resolutions are 800 x 800)

Hello Everyone, I am currently testing the AV-8B and tried to figure out, how to get my two extra screens used. I saw this thread: I removed the two dashes from MPCDR_init.lua and MPCDK_init.lua in C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AV8BNA\Cockpit\MPCD\indicator try_find_assigned_viewport("RIGHT_MFCD") And my screensetup looks like this: _ = function(p) return p; end; name = _('2Camera + RMFCD'); Description = 'Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 3840 / 2160; } } RIGHT_MFCD = { x = 3026; y = 2258; width = 800; height = 800; } LEFT_MFCD = { x = 3; y = 2259; width = 800; height = 800; } CENTER_MFCD = { x = 1525; y = 2261; width = 800; height = 800; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center This is selected in DCS, and working well for A10 and F16 and F18. However, for the Harrier is remains black on my left and right screen. But they are somehow active. They show things like mouse, control input (ctrl+Enter) and the kneeboard. Does anyone have an idea?

Good news for 2.7.9 It looks like, that Flappies experiances with 2.7.9 matches with mine. I already tested 2.7.9 on my main PC and on my last posted third environment. I repeated the test missions (initial post) - Main PC: Stable 2.7.6: 84,775 FPS OB 2.7.9: 84,785 FPS - Third Env: Stable 2.7.6: 43,4 FPS OB 2.7.9: 43,01 FPS Thanks Flappie, thanks ED! Wish you very nice Christmas and a happy new year!

Thanks for that great news! . After a long day this made me a bit more optimistic this evening. And I still crossing the fingers like @speed-of-heat

Me again, sharing some data. I had the chance to reactivate an old computer. - I put it together with a old Geforce grafic card, - installed a new windows 64 bit pro, and then - Installed very fresh DCS Open Beta 2.7.8 (crutial, first installed fresh OB) - installed Stable 2.7.6 - made performance measures Guess what.... Open Beta 2.7.8: 36,5 FPS Stable 2.7.6: 43,4 FPS As metioned in a previous post, I pointed out the settings, that have a bigger effect on this performance drop, like shadows and resolution. So I've chosen these settings that shows the bug. As always, all my data attached. Even though it would be really hard for me to belive in any more "cannot reproduce", but after all the time I am really interested in a official comment to this topic - if there is any news. Tracks&Logs.zip Stable.2.7.6.csv OpenBeta_2.7.8.csv

Wow i never saw those. Thanks a lot