lolwut845

After testing on my rig, the new 1.4.34_beta version of simapppro is much better, but it's still impacting my framerate. Subjectively, it went from unplayable to okayish. In-game fps counter shows a LUA cpu usage of 2-3% without winwing lines in export.lua, 40% with old simapppro version, 8-9% with 1.4.34_beta. Sadly I'm achieving my best framerate without winwing's lines in export.lua and with simappro turned off. Please note that I am playing in VR on an old i7-4790k, so I'm heavily cpu bound.

Yes, but you lose the blinking landing gear lever. It's not a big deal though, given that DCS is almost unplayable in VR with their export anyway

SimAppPro is not what's eating our frame times away. It's the script that occurs within DCS to feed the data to simapppro. To see if you're affected, first check your frame times and the lua usage with DCS frame counter, then go to \Saved Games\DCS.openbeta\Scripts\Export.lua and then comment out those two lines like so -- local wwtlfs=require('lfs') -- dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') Then check your frame times again. For a lot of users, especially in VR, the difference is huge. There's apparently something wrong with the way Winwing is syncing SimAppPro with DCS.

My flight panels from winwing arrived yesterday, so I started using the winwing export again. I'm noticing the cpu/fps performance issue as well on my rig with the winwing lines in the export.lua, even when I remove VAICOMM and Simshaker. Has there been any progress done on this weird export.lua behaviour ?

yup, happens to me too.

You're right, I messed up and mistakenly merged the release and the openbeta. Looking through the registry, my dcs installation was a bit of a mess anyway. I had remnants of 1.5 in the registry (!!!). I binned it all, and restarting fresh with correct paths. Thank you for pointing me in the right direction :smilewink: edit: everything is where it needs to be and everything works correctly !

Thanks for the quick reply ! The log is attached. VAICOMPRO.log

I've been having a blast with vaicom until yesterday, when vaicom decided to update itself. The next time I started dcs, all my menus were flickering. So I followed the faq, reupdated my dcs custom path and then hell broke loose. All the menus just vanished, and even without VA, I can't use the radio in DCS anymore or interact with any of the F# menus. Jester is completely gone, too. Vaicom seems to recognize what I'm saying, but doesn't know which module I'm flying and doesn't seem to interact with dcs. So far I've : 1- repaired dcs -no luck 2- reset vaicom, tried "Hide on-screen text" ticked and un-ticked -no luck 3- repaired dcs again -no luck 4- updated dcs to the latest open beta -no luck 5- deleted all subfolders related to vaicom in my saved games folder, and all i could find in dcs main folder related to vaicom, repaired dcs once more -no luck 6- rolled back to stable -you guessed it, no luck my next step would be a complete reinstall of dcs and VA/vaicom, saving only my liveries and joystick profiles. Before I do that and redownload 200GB, what else can I try ? When I'm running debug mode, vaicom seems to be messing with both DCS and DCS.openbeta folders, which is really weird, since my registry entries seem to be correct and the sliders set to standalone and release/open beta/whatever I'm running at the time. DCS is looking for the files in my "saved games/dcs" folder, not dcs.openbeta Any help would be greatly appreciated

I think you've made a good decision going with the soft cams pre-installed. I'm really looking forward to receiving mine, my vr pit is eagerly waiting :)

looking at the schematics below that, I'm not too concerned about the AB push through. The physical bump looks sturdy. Might even be able to replace/machine that part in the unlikely event it wears out. Jabbers video got me even more hyped. Can't wait to receive mine !

Weirdly enough, even though I'm still on OB 2.5.4.26825, the stutters are gone for me, both for D/RLT mode on the PCN and the radar altimeter at low alt. I don't know if there was a silent update of the open beta when they updated the stable version or if it was my system that played a trick on me, but it's running well now. And the Mirage is still a blast :thumbsup:

Hello, I noticed something while flying on the red flag campaign by Baltic Dragon. I usually fly with my PCN selector on Temps Restant/Vitesse Sol, but when switching to Distance/Relèvement I noticed my FPS tanked hard. It's pretty easy to reproduce, and extremely noticeable and annoying in VR. OB 2.5.4.26825 with the springload fix applied

I haven't played a lot of multiplayer in DCS, but your server was always one of my favourites. Thank you, and good luck in your projects :thumbup:

I wish it lasted longer ! Just finished the campaign, and I loved it ! I loved the immersion, the French accents (ok it's a biased opinion, I'm French), the increasing difficulty which was not unbearable in the end, and even if I experienced a few quirks here and there (mostly because of my lack of radio discipline) this campaign is top notch. Thanks for the great work, and I can't wait for Red Flag :thumbup:

I've made some interesting findings, I can run the game with high or ultra settings everywhere BUT the shadows on "flat only" (every other setting in the shadows make the game crash while loading), right until takeoff. Then the game crashes as soon as I'm airborne.

I got to the main menu through the injection of the dlls posted by skatezilla. I couldn't even get there before ! So I guess it's a start. Now it freezes in the loading screen whenever I try to launch any mission. :cry: win 8.1, intel i7 4790K, Fury X and catalyst 15.9.1 log attached of a crash while loading sam killer mission dcs.zip