RedShoes
-
Posts
167 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by RedShoes
-
-
Still having this. Regardless of the plane I'm flying.
Can easily re-produce with 109 normandy freeflight mission.
Note; if I set FOV to max 130 and pre-rendered frames to 3 or 4 in nvidia CP, the frequency of game freezes reduces a lot. Anyhow, still have them once in someting like couple of hours.
If I do not set above and leave FOV to default 140, I can re-produce the issue with low level aerobatics and moving my view (Trace-IR) and zooming arround in less than 10 minutes.
-
Tried the current GALI mission.
All the Blue bunkers (targets for red team) are invisible :-(
No Joy
Please consider putting some other targets that can be attacked & destroyed.
-
Your resolution is 1680 x 1050. Is that really your native screen resolution?
(just wondering if DCS 2.5 for some odd reason would give you lower quality textures if your screen resolution is below 1920x1080???)
Please give a try at the native screen resolution if that is not already the case.
-
Turn on gsync AND vsync in nvidia control panel.
No in game vsync.
Works just fine for me. I additionally use FPS limiter in riva turner for 97 fps, as my monitor is 100Hz gsync enabled.
Best way to monitor if the gsync is enabled is via fps indicator enabled from the monitor osd. This shows the actual monitor refresh rate.
I can see when I'm not Alt+Enter full screen mode, that the in game fps varies, but the monitor refreshrate stays at 100. When enabling full screen mode (and thus also the gsync), both the in game fps indication and the monitor refreshrate vary, but stay in sync ...and this is also the most clear image i get, no tearing.
-
post your graphics settings
how come is your resolution 1680 x 1050?
...and as said above, check your texture is at "high"
-
I would say, stick it in and see how it works.
Before you stick it in, read your motherboard manual about which RAM slots to use.
You have not told us yet what exact motherboard you have, but what you told us so far, I would assume it supports dual channel. Therefore try first to stick one on channel A and the other on channel B.
Check in your BIOS that the both sticks are recognized before booting to OS for the first time.
Basically it should work.
You might have to make sure your motherboard bios is up-to-date. If it is not working, check your MB manufacturers support page for bios update.
When investigating DCS 2.x microstutters and game freeze problems, I once actually configured 2 identical RAM sticks for single channel (i.e. 2 sticks in, one in channel A, the other in channel B) and compared that to dual channel configuration and found no noticeable in-game fps or performance difference. Back then I was testing with i7-4790K and a MSI Z97 gaming 5 MB and Corsair Vengeance 2400 DDR3, 2x8GB sticks.
-
I've updated from 4790K to 8700K about a month ago.
I did some before / after comparison back then on DCS 2.2 and the performance increase was there about 10% ball park for max FPS with 3440x1440 resolution. Anyhow, as my monitor is 100Hz g-sync I honestly did not really see the difference.
A more noticeable difference was with VR, where I can now get a more smooth experience. Less, if any, dropping in to the low <45 fps area, much more 90fps VR sweetness with the new build.
My update was from;
4790K@4.8GHz, MSI Z87 Gaming 5 and 32GB Corsair vengeance 2400 ddr3
to;
8700K@5.1GHz, Gigabyte Z370 Gaming 7 and 32GB GSkill trident-z 3600 ddr4
Other components like Samsung 960 EVO M.2 drive and GTX 1080Ti were kept the same.
I have a EKWB custom build water loop including both for CPU and GPU with 480 (4x120) and 420 (3x140) rads.
....and I still get an occasional DCS 2.5 complete game freeze (which I believe is a DCS 2.x core game engine bug) :(
Now, weather the update is really worth it is highly debatable. If feel it really depends; few additional fps for 1000 bucks. Not really worth it. Did not really make a difference if I was getting 80 - 100 fps on a 100Hz g-synch monitor compared to 90 - 100 now.
On the other hand VR flying experience with Oculus Rift CV1 is noticeably better now. Anyhow, as small tweak on PD earlier with 4790K, and it was pretty good too.
Other applications like photo / video editing (Adobe lightroom, photoshop, premiere, after effects....) is now of course noticeably faster.
Telecommunication networks related simulation I run for work goes through in 10 vs 18 minutes.
Now, I'm a bit of a PC nerd and I simply like messing around with latest gear, so hell yeah! It was worth it :thumbup:
-
...ok, it was the track file that was too large.
Crash log without the track attached here.
-
Once off crash during online game. Burning Skies server.
C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\AsyncNet.dll
# C0000005 ACCESS_VIOLATION at DE836B0F 00:00000000
crash log NOT attached as it is too large!
When I try to attach to forum post, It says;
dcs.log-20180209-222035.zip:
Your file of 33.52 MB bytes exceeds the forum's limit of 9.77 MB for this filetype
Crash log available in;
https://mega.nz/#!1txHXK6S!PxMDDWRUudlbARhSS7YyoQI7UCh46tvrPQiHAL62wqw
-
I've had these game freezes since release of Normandy map when I started using DCS 2.x versions. Several other people have been reporting the same.
https://forums.eagle.ru/showthread.php?t=196211
https://forums.eagle.ru/showthread.php?t=189729
https://forums.eagle.ru/showthread.php?t=188804
I believe that it is a fundamental problem in ED's new game engine; Some game engine threads get out of synch or stuck. A watchdog expires and they try to re-start the main graphics engine. That fails and the result is a game freeze. If the re-start of the main graphics engine works ok, all you see is a bit of stutter.... but not being anyway related to ED or their SW development team, this is all of course pure speculation.
The only thing that has helped me is to;
- limiting max FOV to 120 - 130 (.lua file edit for CameraViewAngleLimits) and
- setting nVidia control panel setting max pre-rendered frames to 3.
to me that is not a fix, but a workaround that at least in my case helps a bit. In the end ED need to fix their code.
-
What is your monitor resolution and refresh rate? What are you trying to achieve with your update?
Upgrading CPU on your current mobo does not really make sense. You might want to check if you can overclock your current i7-3820.
I have a older system based on Asus P9X79 and i7-3930K and GTX 980 and it is actually still quite good on 1920x1080 resolution.
I would advice GTX 1070 (or GTX1070Ti) instead of 1060, but that depends of course on your available funds and if you are aiming better than 1080p @ 60Hz.
Do you have a SSD in your system? If not, you should definitely get one together with new graphics card if you update.
-
^ go for 130
For me FOV 130 and max pre-rendered frames at 3 is already a big improvement.
...and yeah, it's not a fix, just a workarround. Especially for people with wide multi monitor setups. I have 21:9 aspect ratio ultra wide monitor myself and FOV 130 is actually pretty ok for me.
-
Yes it seems to be the case for me that, as I said in my post #43 earlier, when I limit my FOV to 120 - 130 and have nVidia Control Panel maximum pre-rendered frames to 3, I do not get the game freeze issue anymore. Both not in single player or not in multiplayer.
I have tested more than 4 hours single player and more than 6 hours multi player and have had only 2 game freeze'es in multi player, but in both cases FOV was 130 and max pre-rendered frames default. With FOV 120 + max pre-rendered frames at 3, not a single game freeze during 10 hours of gameplay.
Although, I can not confirm that the issue is really resolved with these settings, but it is at least a big improvement.
If I reset these values back to default settings, I can re-produce the game freeze issue typically under 10 minutes of flight.
I can also see from comments from other people, that especially limiting FOV seems to improve the issue for other people too.
Hopefully this is something that ED can start with and finally resolve the issue.
I have been reporting the issue now for 6 months, so it would be about the time.
Anyhow, I do not consider limiting FOV and max pre-rendered frames as a fix for the issue, just a work arround.
As already indicated;
- limiting FOV is particullary bad for people with wide multi-monitor setups.
- setting max pre-rendered frames to 3 introduces input lag.
-
1
-
-
- current DCS core simulation supporting only 2 enginesHow is any B17 harder than say the F14 Heatblur are making? ....- current DCS multicrew only 2....
,but yeah, I would love to see a MultiCrew full fidelity B-17 in DCS. Simply the idea of one well placed burst from mk 108 giving you 10 online PvP kills is very exhilarating :gun_rifle::devil_2:
-
...
PS: I checked some other "crash" threads and it seems I'm not the only one getting freezes and crashes. For example this one seems very similar :
https://forums.eagle.ru/showthread.php?t=196211
Makes the game pretty much unplayable for me.
I have been having DCS 2.x freeze issue since I installed it when the Normandy map came out.
I have tested pretty much every setting, swapped pretty much every HW component in my rig, done numerous clean DCS and windows installs,.... and nothing helped
see more details in;
https://forums.eagle.ru/showthread.php?t=189729
https://forums.eagle.ru/showthread.php?t=196211
...until I made two changes;
- nVidia Control Panel; Maximum pre-rendered frames. If I set this to 3 or 4 the game freeze does not occur as easily as with default or with value 1.
- FOV; The default maximum Field Of View seems to be 140. If I limit this to something like max 120 via CameraViewAngleLimits settings in C:\Users\UserName\Saved Games\DCS.openalpha\Config\View\Server.lua I also seem to have less game freeze occuring.
In Server.lua set
see; https://forums.eagle.ru/showpost.php?p=3319437&postcount=43
I'm still testing, but it looks good to me sofar and other people have also given some positive feedback. Perhaps give this a try?
-
My experience is that DCS 2.2 performance is better, more fps, more smooth, less stutter than earlier DCS 2.1.x versions, BUT only for single player! Multi Player is just as bad, if not worse.
That can also be seen here on the forums in terms of number of new MultiPlayer performance related issue threads raised since release of DCS 2.2.
I have not monitored RAM usage accross the versions, but if I set pre load radius in the in game settings to about half way. DCS 2.2 is using arround 8GB of RAM (based on Windows Resource Monitor and MSI Afterburner RAM usage statistics). If pre load radius is at max, I see 11 - 14 GB of RAM is beeing used. That is Normandy map and applies also to Multi Player.
-
I'm getting frequent disconnects from the server.
The logfile shows sound and .json errors.
00238.318 ERROR SOUND: invalid source_params(woLA-16777731:aircrafts\engines\packardmerlinprop\engspatial): gain 00395.201 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_dam_fuz_front.dds'. 00395.207 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_cocpit_dam.dds'. 00395.220 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_dam_fuz_rear.dds'. 00408.968 ERROR SOUND: invalid source_params(woLA-16777474:aircrafts\engines\rollsroycemerlin\engine): gain 00597.783 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 00618.519 ERROR VFS: Can't open file //models/tracer_bullet_white.edm.json. 00618.524 ERROR VFS: Can't open file //models/tracer_bullet_green.edm.json. 00618.655 ERROR VFS: Can't open file //models/tracer_bullet_yellow.edm.json. 00668.441 ERROR SOUND: invalid source_params(woLA-16777474:aircrafts\engines\rollsroycemerlin\engine): gain 01061.847 ERROR SOUND: invalid source_params(woLA-16777474:aircrafts\engines\packardmerlinprop\engspatial): gain 01071.915 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 01100.813 ERROR SOUND: invalid source_params(woLA-16777730:aircrafts\engines\rollsroycemerlin\engine): gain 01469.950 ERROR SOUND: invalid source_params(woLA-16777477:aircrafts\engines\packardmerlinprop\engspatial): gain 01593.341 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 01696.885 ERROR VFS: Can't open file //models/tracer_bullet_red.edm.json. 01719.367 ERROR SOUND: invalid source_params(woLA-16777730:aircrafts\engines\packardmerlinprop\engspatial): gain 01737.431 INFO NET: disconnected: 1 01737.530 INFO NET: disconnected from server 01737.530 INFO NET: client has stopped 01739.358 INFO Config: netview stopped
00267.056 ERROR VFS: Can't open file //models/tracer_bullet_yellow.edm.json. 00267.289 ERROR VFS: Can't open file //models/tracer_bullet_red.edm.json. 00269.753 INFO COCKPITBASE: lua state still active MACROS, 12 (status undefined) 00269.753 INFO COCKPITBASE: lua state still active INTERCOM, 15 (status undefined) 00269.762 INFO DCS: dbox failed Initialize -7 00270.417 ERROR SOUND: can't load wave: "effects\weapons\missilelaunchin" 00347.579 ERROR GRAPHICSVISTA: Can't open model FW-190-oblomok_stab. 00386.948 ERROR VFS: Can't open file //models/tracer_bullet_white.edm.json. 00386.971 ERROR VFS: Can't open file //models/tracer_bullet_green.edm.json. 00480.393 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 00488.319 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_damage_main_2.dds'. 00488.366 ERROR DX11BACKEND: Can't create 2d texture for '/textures/damadge elements.dds'. 00488.510 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_damage_main.dds'. 00489.018 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_cocpit_n_instrument.dds'. 00489.046 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_engine.dds'. 00489.050 ERROR DX11BACKEND: Can't create 2d texture for '/textures/p51d_cocpit_n.dds'. 00495.721 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 00545.517 WARNING LOG: 1 duplicate message(s) skipped. 00545.517 ERROR SOUND: invalid source_params(woLA-16777475:aircrafts\engines\rollsroycemerlin\engine): gain 00555.341 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 00576.364 ERROR SOUND: invalid source_params(woLA-16777480:aircrafts\engines\rollsroycemerlin\engine): gain 00582.644 ERROR SOUND: invalid source_params(woLA-16777733:aircrafts\engines\rollsroycemerlin\engine): gain 00604.213 ERROR SOUND: invalid source_params(woLA-16777479:aircrafts\engines\rollsroycemerlin\engine): gain 00870.250 ERROR SOUND: invalid source_params(woLA-16777480:aircrafts\engines\packardmerlinprop\engspatial): gain 01131.856 ERROR SOUND: invalid source_params(woLA-16777737:aircrafts\engines\packardmerlinprop\engspatial): gain 01180.752 INFO NET: disconnected: 4 stream error 01180.887 INFO NET: disconnected from server 01180.888 INFO NET: client has stopped 01182.066 INFO Config: netview stopped
I have plain vanilla installation, no mods, not even tacview installed.
DCS_updater cleanup, repair and update done prior to connecting to the server.
eekz, have you been reporting / discussing these frequent disconnects with ED?
Any response from them?
Attaching logs just in case these would be any use.
For me DCS 2.2 is more stable / better fps than earlier 2.1 versions in single player, but Multi Player is just as bad, if not worse.
-
How about my initial answer on this thread;
2.2 seem to have some new issues in there that effect especially Multi Player. If you are fine on single player you might be best off waiting a while for the next patch.What are your in game settings?
Preload radius does affect also RAM usage of the game. Try lowering it a bit.
a small preload radius means small RAM & VRAM requirement and lots of small terrain loading from disk.
a large preload radius means larger RAM & VRAM requirement and less frequent, but larger terrain loading from disk.
If you do not have a SSD, you might want to consider.
i.e.;
1 - DCS 2.2 seems to be buggy and especially multiplayer performance is very bad. Either get youself a killer rig or cross your fingers and pray that ED actually fixes some issues for the next patch instead of just creating new ones.
2 - Check your ingame settings. These can effect your performance greatly.
3 - Consider updating your system with a SSD drive, if you do not already have one.
-
Well I will upgrade RAM and see how it works out, if its not the answer I go for a news system soon.
another PC hardware noob question: with currently 16GB of RAM, what would you recommend ? another 8 GiGs ? or 32 GB configuration
with your current system with 16GB of RAM, I would recommend that you review your in game settings, so that you stay below the 16GB. That's the cheapest way. ;-)
...What are your in game settings?Preload radius does affect also RAM usage of the game. Try lowering it a bit.
a small preload radius means small RAM & VRAM requirement and lots of small terrain loading from disk.
a large preload radius means larger RAM & VRAM requirement and less frequent, but larger terrain loading from disk...
Post your ingame settings for review.
additionally, I would recommend a SSD
From you Motherboard link earlier, your PC supports SATA 6Gbit/s
Gesamtanzahl der SATA-Ports 5Maximale Anzahl der SATA-6,0-Gbit/s-Ports 2
Therfore, I'd recommend the SSD 6Gbit/s sata drive I recommended earlier.
...If no support for M.2 PCIe, check for example this out; https://geizhals.de/crucial-mx300-525gb-ct525mx300ssd1-a1481819.html?hloc=de...and ofcourse if you do have the funds, go with what Jonny Rico said;
...Want some good advise?Build or if you cannot build it yourself get a mate to build you a new system, that one is far too olde
to even consider spending anymore money on
If you are short on funds, go ahead and just get the SSD first. 500 GB is plenty to get Windows and DCS installed on it. If it does not help you to get the performance you want, you can still use it when building a new rig.
-
Ok thx,
:thumbup:
as Im a total noob with SSDs can you maybe recommend me one, which fits to my systems specs ?- ( in case the specs determine which SSD one can take)
you can also PM me with a link leading me there... Im truly happy about any adviceI can get here
cheers
What motherboard do you have? Does it support M.2 interface?
If it does, check what M.2 SSDs are listed as supported on the motherboard manufacturers supported devices list on their web site for you particular motherboard.
I have Samsung 960 EVO and find it good. https://geizhals.de/samsung-ssd-960-evo-500gb-mz-v6e500bw-a1511200.html?t=alle&plz=&va=b&vl=de&hloc=at&hloc=de&v=e&togglecountry=set#filterform
If no support for M.2 PCIe, check for example this out; https://geizhals.de/crucial-mx300-525gb-ct525mx300ssd1-a1481819.html?hloc=de
-
No thanks.
TL DR, ...but why do you want an another prop trainer? Is TF-51 not working for you?
-
2.2 seem to have some new issues in there that effect especially Multi Player. If you are fine on single player you might be best off waiting a while for the next patch.
What are your in game settings?
Preload radius does affect also RAM usage of the game. Try lowering it a bit.
a small preload radius means small RAM & VRAM requirement and lots of small terrain loading from disk.
a large preload radius means larger RAM & VRAM requirement and less frequent, but larger terrain loading from disk.
If you do not have a SSD, you might want to consider.
-
...again, 2nd time in a row
00161.442 ERROR VFS: Can't open file //models/tracer_bullet_yellow.edm.json. 00263.876 ERROR VFS: Can't open file //models/tracer_bullet_red.edm.json. 00295.548 INFO NET: disconnected: 0 00295.648 INFO NET: disconnected from server
Logs attached
-
I was just about to take off on a 109 from Lingerolles, when I got some stutter and then got disconnected.
My log file show;
00301.328 ERROR VFS: Can't open file //models/tracer_bullet_yellow.edm.json. 00301.424 ERROR VFS: Can't open file //models/tracer_bullet_red.edm.json. 00303.569 ERROR VFS: Can't open file //models/tracer_bullet_white.edm.json. 00303.574 ERROR VFS: Can't open file //models/tracer_bullet_green.edm.json. 00443.945 ERROR DCS: Error: Unit [spitfireLFMkIX]: No shell for property records XCockpitElement03 XEng0WaterPump XFuelDroptank0 XFuelLineD XUCWheelC. 00487.745 INFO NET: disconnected: 1 00487.845 INFO NET: disconnected from server
looks like the old tracer_bullet....edm.json issue is causing us trouble again???
It was perhaps arround 22:08 CET
my log attached.
Unit magic
in Object Bugs
Posted
Burning Skies server has red for Bunkers, that are visible from some angels, invisible from others. Visibility is also dependant on zoom level, so that when you attack them and zoom in to get a good view, they sometimes just disapear :doh: