HarpO74

So I cranked the TR to 4Ghz and then 4.2Ghz. Results below. Two things seem apparent: 1 - Despite the insane peaks at the start, by 1/3 of the way through they basically equalized. 2 - The higher you go with CPU, the less Vulkan is able to push the GPU. At 4.2 it only pushed the GPU to 88% load. Make of that what you will. Cheers HarpO74

Worrazen, DX11 to DX12 is an evolution... taking what ED has already developed with the EDGE engine and extending that further to take advantage of the new features in DX12. DX11 to Vulkan is largley a re-write of the EDGE engine. When you take into account that the Vulkan engine is much more diffcult to code for becuse it operates at a lower level and that Vulkan does not include native support for Sound or other peripherals, ED has to do a mountain of work to make all of that run correctly. The mirad of different hardware combinations that ED have to account/code for, and test with to ensure stability, increases almost expenentially. Even if the advantages are that ED now has much more control over the engine and how it uses the hardware, they still have to code for it. And that alot of work, it's huge. ED is a small company and they have made an unbelievable product. There isn't anyone here that hasn't just gone flying around in the jets just to marvel at the scenery and how awesome it looks. But EDGE needs an overhaul and performance is main thing everyone wants to see. In terms of bang for effort... it seems Vulkan is on the wrong side of the ledger. I just hope ED have done their homework and chosen this path for the right reasons. Maybe ED have the Yoda of Vulkan coding working for them. :thumbup: Time will tell, hopefully not too much time though.

Yeah $#% Windows :mad: can poff There's a sound reason to do a major change like this. The real thing that DCS needs is more performance, period. Everything else it already has in spades. There was no great hand off to the CPU on those results, if there was, the TR would of smashed past the DX numbers. I'll search for some other tests that compare the API's. I'd rather base my thoughts on real results. So far I don't see the benefit. Maybe that will change. Cheers HarpO74

..

After I watched the two videos Skates posted earlier on the thread, I ran the tests myself. I don't see any benefit. The draw calls were higher, but the overall FPS didn't improve, in fact it was slightly worse with vulkan. Given the spec of the system I would of expected to see some better FPS. I haven't OC'd anything, but with this level of system I shouldn't have to to see some increase, even small. There was also some anecdotal info that as Vulkan is the OpenGL replacement, its a pure graphics API and doesn't natively support sound or peripherals like DX does. If that correct will that complicate the support of those types of devices for DCS? Maybe evolution to DX12 instead of revolution to Vulkan would be the least path of resistance. I love what ED has done and DCS is unreal, but am not sure that this will be an easy path, nor bring any great improvement. Hopefully this will turn out OK. Cheers HarpO74

For anybody with the Vive Pro, I found the V12 settings on this page to be the best. https://www.thingiverse.com/thing:2837804 Instructions on how to alter the settings on the unit are below:- https://www.reddit.com/r/Vive/comments/86uwsf/gearvr_to_vive_lens_adapters/dwdigxa/ Cheers Harp0

Sweet. Thanx DDSSTT Cheers Harp0 Sent from my ONEPLUS A6003 using Tapatalk

Has anyone here completed the lense swap to use the gear VR lenses in the VIve/VIve Pro? I'm curious to know if the barrel distortion correction that needs to be applied for Steam VR will apply to DCS as well. Recently bought the pro and it's fantastic, but by all the reports, it seems the freznil lenses are holding it back. Cheers Harp0 Sent from my ONEPLUS A6003 using Tapatalk

Thanks again hansangb :))))) So anyone else can do this... Forget putting any kneeboard references in the monitor.lua file, just specify the the number of screens. eg below... _ = function(p) return p; end; name = _('2 Screens'); Description = '2 Screens - 1 Main Camera, 2 - Kneeboards' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 1.777777778; }, Tablet = { x = 3840; y = 0; width = 2000; height = 3000; aspect = 2.3; }, } UIMainView = Viewports.Center Set your resolution to cover the total, so for me it was 5840 x 3000. Next, per the post above, alter the viewportHandling.lua file to move the kneeboard to where you want. Just a small note, the line to edit is now line 33. So for me that line is now: dedicated_viewport = {3840,0,2000,3000} Surfacebook's native res is 3000x2000, so it drives that no issue. Windows 10 allows you to project to a surface via wifi, and its only a 13.5" screen so the res is amazing. I use it mostly for work, but it now has a extra job. :smilewink: Cheers Harp074

HA ! Thanks hansangb :thumbup: Yep that fixed it, now it shows up in the option screen. Figured I was doing something stoopid ! :doh: Kneeboards still show up on the main screen though, so you're right, Viewport option didn't work. Just got to figure how to move them now. I'll keep trying. Cheers Harp074

Hi All, After a bit of help. Sorry if this has been addressed before, but I haven't seen anything to help me out. AM running 2.5 Openbeta for FA-18C Have 2 screens. a 43" 4K as main monitor and am using my Surface book screen as second monitor. I just want to use the the Surface for the kneeboards. Have the surface (Tablet) positioned below the main monitor, vertically lined up along the left edge. I have created a second LUA in the monitors folder, but I can never get it to show up in the options screen. I'm presuming I've got the code wrong and DCS is rejecting the file or something. Code is below:- _ = function(p) return p; end; name = _('2 Screens'); Description = '2 Screens - 1 Main Camera, 2 - Kneeboards' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 1.777777778; } Tablet = { x = 0; y = 2161; width = 2000; height = 3000; aspect = 2.3; } } UIMainView = Viewports.Center Kneeboard = Viewports.Tablet Any Ideas ?

For TM the Warthog throttles - moving the left throttle into the cutoff position (lifting the lever) depresses button 29. - moving the right throttle into the cutoff position (lifting the lever) depresses button 30. - moving the left throttle out of the cutoff position releases button 29. - moving the right throttle out of the cutoff position releases button 30. Is there a way to program this into the lua ?? If there is, we can mimic the RL action of the throttles for the engine start and stop sequences at least. For carrier ops, we'll have to just use the 9 & 0 keys. Cheers JH

Thanks Sabre. Any idea when it will be available for the release stream. I just switched out of the Beta stream for the merge. I don't really want to run two streams. Cheers Harpo_74

Hello, The download fails with the below error. === Log opened UTC 2018-04-28 00:28:22 INFO : DCS_Updater/2.6.25.40 (Windows NT 10.0.16299; Win64; en-AU) INFO : cmdline: "C:\Program Files\DCS World\bin\dcs_updater.exe" --apply install MAPLEFLAG_F15C_AGGRESSORS_BFM_campaign F15C-THE-GEORGIAN-WAR_campaign A10C-TTQ_campaign F15C-REDFLAG_campaign STATUS: Initializing... INFO : basedir: C:\Program Files\DCS World INFO : DCS/2.5.0.15365.345 (x86_64; EN; WORLD,AVIODEV_C-101,MIG-15BIS,MIG-21BIS,BF-109K4,F-86F,FW-190D9,A-10C,FC3,P-51D,A10C-REDFLAG_campaign,SU27-ULTIMATE_campaign,NEVADA_terrain) INFO : branch: STATUS: Connecting to update servers... INFO : Got reply from http://www.digitalcombatsimulator.com INFO : Got reply from srv3update.digitalcombatsimulator.com STATUS: Verifying cached version info... STATUS: Preparing to install MAPLEFLAG_F15C_AGGRESSORS_BFM_campaign,F15C-THE-GEORGIAN-WAR_campaign,A10C-TTQ_campaign,F15C-REDFLAG_campaign ... ERROR: Unknown module MAPLEFLAG_F15C_AGGRESSORS_BFM_campaign === Log closed. Any ideas how to fix this?? Cheers Harpo_74

Cool. Great system. You'll love it once you get it all sorted. Monster machines are great fun. You went full on with the cooling. I'm still bumbling along with my aio. I think before I do the cooling thing, I'll change my case. Trouble is I can't seem to find something I like right now. In the mean time I can clock up many hours in the F-15C and drool waiting for the F-18C to drop. Cheers Sent from my ONEPLUS A5000 using Tapatalk