I do not have tearing problems on AMD cards anymore - it was caused by driver.
Wine 2.3
========
Performance tests (Intel)
---------------------------------
Prologue: 70-90 FPS
Midnight Surprise: 50-70 FPS
The Underground City: 100-120 FPS
Too Many Targets: 50-90 FPS
Halong port: 60-120 FPS
Performance tests (AMD)
---------------------------------
Prologue: 70-80 FPS
Midnight Surprise: 50-60 FPS
The Underground City: 80-120 FPS
Too Many Targets: 50-70 FPS
Halong port: 50-120 FPS
Wine staging 2.3. + CSMT
-this is NOT official release of Wine, it can improve performance but it also could be more unstable
=================
Performance tests (Intel)
---------------------------------
Prologue: 110-130 FPS
Midnight Surprise: 70-90 FPS
The Underground City: 110-140 FPS
Too Many Targets: 80-120 FPS
Halong port: 90-130 FPS
Performance tests (AMD)
---------------------------------
Prologue: 90-130 FPS
Midnight Surprise: 50-90 FPS
The Underground City: 80-180 FPS
Too Many Targets: 50-80 FPS
Halong port: 50-180 FPS
Wine staging 2.3 + Gallium Nine
-this is NOT official release of Wine, it can improve performance but it also could be more unstable
-Gallium Nine is native D3D9 implementation for some Linux open source graphic drivers (not available for Intel)
===========================
Performance tests (AMD)
---------------------------------
Prologue: 90-130 FPS
Midnight Surprise: 80-120 FPS
The Underground City: 100-160 FPS
Too Many Targets: 60-90 FPS
Halong port: 80-160 FPS
Summary:
-crashes very often in missions Too Many Targets and Midnight Surprise (my tip is that flares caused this)
If graphics card drivers were the same in matter of effecienty (Linux and Windows), then it is expected that game in Wine will be slower than Windows, simply because of that Wine has to translate some Windows calling and translate D3D to OpenGL during the runtime. In reality, Wine version can be faster in some situations because of badly supported graphics API on Windows - good example is D3D8 support in newer Windows. As Vietcong players know, there was significat performance increase when VCStarter switched from D3D8 to D3D9 - maybe because of fact that D3D9 are much better supported in newer Windows than D3D8 (which is really old).
Anyway, i dont know what are your FPS on Windows with the same hardware, but lower FPS could happend because of overhead while translating D3D -> OpenGL (as I told), worse drivers on Linux than on Windows or becuase of old Wine version (there was some performance optimalization). But it is great that you were able to run it on Linux!
sonic wrote:
If graphics card drivers were the same in matter of effecienty (Linux and Windows), then it is expected that game in Wine will be slower than Windows, simply because of that Wine has to translate some Windows calling and translate D3D to OpenGL during the runtime. In reality, Wine version can be faster in some situations because of badly supported graphics API on Windows - good example is D3D8 support in newer Windows. As Vietcong players know, there was significat performance increase when VCStarter switched from D3D8 to D3D9 - maybe because of fact that D3D9 are much better supported in newer Windows than D3D8 (which is really old).
Anyway, i dont know what are your FPS on Windows with the same hardware, but lower FPS could happend because of overhead while translating D3D -> OpenGL (as I told), worse drivers on Linux than on Windows or becuase of old Wine version (there was some performance optimalization). But it is great that you were able to run it on Linux!
LOL . you are too smart for me , just say it easy for me ....
Well, WINE is recursive acronym for Wine Is Not an Emulator, so technically it is not an emulator, but it is something similar...so yes, you are right.
Btw, Vietcong game can not handle more than 500 maps in a maps folder (i dont know exact number, maybe it may be different for some users). Not folder size, but number of files (maps) in folder is a problem in my opinion
Small update, after having small talk with Brchi and Wine developer we have made little progress: the game do not crash (bug 9337 )...but it show graphical defects now
But it should be possible to fix it.
If you are interested in more info: https://www.winehq.org/pipermail/wine-devel/2017-August/118619.html
More as 4,7Gb or 500 Maps in Windoof or Linux > Vietcong startet NOT !!!!
Vietcong Adddon Fist Alpha is starting and Multiplayer Ok !!!!
Spoiler:[ShowHide]
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme3d:state_zenable W buffer is not well handled
fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4070407, 0000: semi-stub!
err:hid_reportrocess_hid_report Device reports coming in too fast, last report not read yet!
err:hid_reportrocess_hid_report Device reports coming in too fast, last report not read yet!
fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
fixme:msvcrt:__clean_type_info_names_internal (0x37054c) stub
i think that the 500 maps issue is not Windows/Wine problem, but the Vietcong bug - we can do nothing about it, just back up some some maps and move them temporary out of the maps folder (maybe it could be possible to fix it somehow in VCStarter? I dont know).
About these errors:
Code
err:hid_report:process_hid_report Device reports coming in too fast, last report not read yet!
err:hid_report:process_hid_report Device reports coming in too fast, last report not read yet!
fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
I never saw them before. If is it working, just ignore them :) (you can ignore fixme messages for sure, but I do not know what caused these err messages).
I was told that the game preloads *.cbf map files or some of their content. The limit serves as protection from using too much RAM. That would make perfect sense 13 years ago but now? I dont think so.
i think that the 500 maps issue is not Windows/Wine problem, but the Vietcong bug - we can do nothing about it, just back up some some maps and move them temporary out of the maps folder (maybe it could be possible to fix it somehow in VCStarter? I dont know).
About these errors:
Code
err:hid_report:process_hid_report Device reports coming in too fast, last report not read yet!
err:hid_report:process_hid_report Device reports coming in too fast, last report not read yet!
fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
I never saw them before. If is it working, just ignore them :) (you can ignore fixme messages for sure, but I do not know what caused these err messages).
Nosek: yes, it sounds reasonable, but the problem is that Vietcong just crash without warning and you do not know what is happening - no err message, info, nothing.
420Ninjutsu: mm yes, I am trying (btw your inbox is full, I am unable to send you a message)
I forgot to inform you about progress made by Wine developers:
1) bug 42588 which appeared in Wine 2.1 has been fixed
2) bug 9337 has been fixed in Wine staging (testing area for Wine patches), so we can expect it landing in official Wine sooner or later.
Linux user Xpander69 also created video showing Vietcong running on Linux:
(click here video is not working: https://www.youtu...FHvSqtIr9c)
I took small break in doing Blender plugin and during Christmas started digging into Wine again. I focused on radio-relay bug, despite the fact it is fixed by VC-starter. The reason was that fixing this issue might help other application running it Wine (it showed up that this was not true) and also that the demo versions can not be run with VC starter. Surprisingly the crashing on radio relays on newer Windows is not Windows/Microsoft fault, but the fault of Vietcong creators. The game depends on specific behavior of kernel32 dll, which has changed with Windows Vista. For more details see the bug #43567. Although I found a way how to fix this issue, it probably will never be accepted by Wine because it is application specific bug and may break other applications. But it showed us a workaround which we may use.
About the other Vietcong related stuff during the last year, there was nothing special, except:
-Wine staging is unusable for Vietcong at the moment, do not use it
-there were regression bugs, which have been fixed so they will not make it into upcoming stable release
-thumbnails of game saves are being created corrupted, but the patch is on the way (bug #46375)
I think it is time to sum up how to run Vietcong in Wine:
- stay away of Wine staging, it is broken since Wine-staging 3.9 (bug #45278 and bug #45623)
- install VCStarter 1.70Beta (exactly this version, older will not work) as a workaround for bug #9337 and radiocalls bug #43567 (you need to enable fix in VCStarter config)
- install native directplay library to be able to join game servers (bug #33295). You can install it for example using winetricks: winetricks directplay
- add following line to your /etc/hosts file, so Vietcong server list will work properly: 65.112.87.186 master.gamespy.com
-your ingame screenshots (F2) will probably not work, I am not sure yet where is the problem, but it happens only with VCStarter
x 1
x 1
x 1
rocess_hid_report Device reports coming in too fast, last report not read yet!
x 2