Battlefield 1

Questions about Wine on Linux
Post Reply
cusa123
Level 1
Level 1
Posts: 5
Joined: Sat Jan 27, 2018 11:31 pm

Battlefield 1

Post by cusa123 » Sat Jan 27, 2018 11:43 pm

https://ibb.co/bvYNjG
When installing bf1 i get this!.
Ubuntu 17.10.1 wine 3.0
amd ryzen 1700 GTX 970sc "NVIDIA Drivers 384,111 ".
Attachments
Sin nombre.png
Sin nombre.png (25.85 KiB) Viewed 4096 times

User avatar
Bob Wya
Level 12
Level 12
Posts: 2759
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Battlefield 1

Post by Bob Wya » Sun Jan 28, 2018 6:45 pm

Since Battlefield 1 requires DirectX 11.0 support Wine may be missing an extension for this particular game...

What's the output from (terminal commands):

Code: Select all

export WINEDEBUG=+wgl
cd < game directory >
wine < game executable > &>~/wine_bf1_log.txt
You need to change directory to the main game directory and put in the main Battlefield 1 executable name.
DON'T just copy-paste those terminal statements unmodified!
See: WineHQ FAQ: 10.1.1 How can I get a debugging log (a.k.a. terminal output)?
See: WineHQ User's Guide: 3.1.1 How to run Windows programs from the command line.

Unfortunately Battlefield Bad Company 2 - using the older Frostbite engine - runs like ass under Wine...
So I wouldn't hold out much hope for a playable Battlefield 1 - since the Frostbite engine it uses will be even more advanced.

Bob

cusa123
Level 1
Level 1
Posts: 5
Joined: Sat Jan 27, 2018 11:31 pm

Re: Battlefield 1

Post by cusa123 » Mon Jan 29, 2018 6:49 pm

https://www.youtube.com/watch?v=IBpFRajClp0
Apparently in windows gives the same problem.
It would be interesting to install nvidia drivers on winehq.

User avatar
Bob Wya
Level 12
Level 12
Posts: 2759
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Battlefield 1

Post by Bob Wya » Tue Jan 30, 2018 7:48 am

cusa123 wrote:https://www.youtube.com/watch?v=IBpFRajClp0
Apparently in windows gives the same problem.
It would be interesting to install nvidia drivers on winehq.
No they don't... That is a different issue...

Legacy Nvidia cards (8800 series - 300 series I think) are only supported by the 34x.xx Nvidia drivers.
That is what the linked Youtube video is referring to.

Please supply the debug log - as requested... Then we can check if your Nvidia card is being detected correctly by Wine.

Ta
Bob

cusa123
Level 1
Level 1
Posts: 5
Joined: Sat Jan 27, 2018 11:31 pm

Re: Battlefield 1

Post by cusa123 » Tue Jan 30, 2018 6:45 pm

.wine/drive_c/Program Files (x86)/Battlefield 1
Bash: Syntax error near unexpected element '(' (x86)
-----------------------------------------------------------------
I'm new to this patient.
________________________________________

cusa123
Level 1
Level 1
Posts: 5
Joined: Sat Jan 27, 2018 11:31 pm

Re: Battlefield 1

Post by cusa123 » Tue Jan 30, 2018 9:19 pm

For some reason eh eh uninstalled and reinstalled but outside of (x86). After installing net framwork 4.5 the error is the 2log.txt.
I do not know the reason but i can't see the uploaded file in the forum so he left also the result of log.txt.


--------------------------------------------------------------------------
fixme:winediag:start_process Wine Staging 2.21 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:wer:WerSetFlags (2) stub!
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:process:SetProcessShutdownParameters (00000380, 00000000): partial stub.
err:module:import_dll Library MSVCR120_CLR0400.dll (which is needed by L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscorsvw.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscorsvw.exe" failed, status c0000135
err:service:process_send_command service protocol error - failed to write pipe!
fixme:service:scmdatabase_autostart_services Auto-start service L"clr_optimization_v4.0.30319_64" failed to start: 1053
fixme:ver:GetCurrentPackageId (0x21f180 (nil)): stub
fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS)
fixme:thread:SetThreadIdealProcessor (0xc4): stub
fixme:thread:SetThreadIdealProcessor (0x144): stub
fixme:thread:SetThreadIdealProcessor (0x150): stub
fixme:thread:SetThreadIdealProcessor (0x140): stub
fixme:thread:SetThreadIdealProcessor (0x160): stub
fixme:thread:SetThreadIdealProcessor (0x16c): stub
fixme:thread:SetThreadIdealProcessor (0x178): stub
fixme:thread:SetThreadIdealProcessor (0x198): stub
fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x6a7e10, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0x1, mode_count 0x2453cf00, desc (nil) partial stub!
fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x6a7e10, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0x1, mode_count 0x2453cf00, desc 0x23e87970 partial stub!
fixme:nvapi:unimplemented_stub function 0x1053fa5 is unimplemented!
fixme:service:QueryServiceConfig2W Level 6 not implemented
fixme:service:QueryServiceConfig2W Level 6 not implemented
fixme:service:QueryServiceConfig2W Level 6 not implemented
fixme:service:QueryServiceConfig2W Level 6 not implemented
fixme:service:QueryServiceConfig2W Level 6 not implemented

User avatar
Bob Wya
Level 12
Level 12
Posts: 2759
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Battlefield 1

Post by Bob Wya » Wed Jan 31, 2018 1:57 pm

cusa123 wrote:For some reason eh eh uninstalled and reinstalled but outside of (x86). After installing net framwork 4.5 the error is the 2log.txt.
I do not know the reason but i can't see the uploaded file in the forum so he left also the result of log.txt.


Code: Select all

...
err:module:import_dll Library MSVCR120_CLR0400.dll (which is needed by L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscorsvw.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscorsvw.exe" failed, status c0000135
...
Wine support for 64-bit .Net 4.0(+) is pretty non-existent.

You'll need to install the native 64-bit VC Runtime 2013 and the native 64-bit .Net 4.0 frameworks[/url].
I'm not actually sure if that's possible at the moment - certainly Austin English hasn't managed to come up with a working workaround / hack for winetricks to-date...
Take a look at the WineHQ AppDB guide for 64-bit Google Sketchup...
Perhaps this will work for you?

Good luck with that! 8)

Please also use the forum Code:

Code: Select all

Code
tags for terminal output and commands...

Ta
Bob

cusa123
Level 1
Level 1
Posts: 5
Joined: Sat Jan 27, 2018 11:31 pm

Re: Battlefield 1

Post by cusa123 » Fri Feb 02, 2018 10:23 pm

Unfortunately I still have the same problem with other games that gives me the same result.
As I tried to resolve through its methods of installing VC Runtime 2013 ...

User avatar
Bob Wya
Level 12
Level 12
Posts: 2759
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Battlefield 1

Post by Bob Wya » Sat Feb 03, 2018 2:22 pm

cusa123 wrote:Unfortunately I still have the same problem with other games that gives me the same result.
As I tried to resolve through its methods of installing VC Runtime 2013 ...
I am one of those people that boycott all Origin games - because I trust EA as far as I can spit...
So excuse my ignorance about any Origin-only game releases... 8)

I presume that you can't install Battlefield 1 in a 32-bit WINEPREFIX - it's a 64-bit only Windows game release - right?
Or wrong?

If a 32-bit version is supported - then obviously that is the version you want to test first!
You'll probably still find the game fails at some later stage anyway...

Bob

dj--alex
Level 3
Level 3
Posts: 59
Joined: Sun Aug 23, 2009 4:59 am

Re: Battlefield 1

Post by dj--alex » Mon Oct 08, 2018 6:20 am

I found video
https://www.youtube.com/watch?v=vygsIchfZCU
How you install this.

I nstall and get message Nvidia driver your using is 331 get new 375 driver. I already Have DXVK 80 , wine 3.17-staging and Nvidia -410 driver and GTX 1080 card and game no works/

Maybe i need go to future to 2030 year and install Nvidia 800 driver?

lle
Newbie
Newbie
Posts: 1
Joined: Mon Oct 08, 2018 3:16 pm

Re: Battlefield 1

Post by lle » Mon Oct 08, 2018 3:35 pm

dj--alex wrote:I found video
https://www.youtube.com/watch?v=vygsIchfZCU
How you install this.

I nstall and get message Nvidia driver your using is 331 get new 375 driver. I already Have DXVK 80 , wine 3.17-staging and Nvidia -410 driver and GTX 1080 card and game no works/

Maybe i need go to future to 2030 year and install Nvidia 800 driver?
You must disable the nvapi64.dll and/or nvapi.dll. I use wine-staging latest version, Mesa 18.2, NVIDIA 396.54.02 Driver. After disable nvapi.dll and nvapi64.dll in the Winecfg Override Libraries settings (disable!) and Battlefield 1 run in Single- and Multiplayer. Please make sure you also setup the dxvk override entries for dx11 and dx10 and dxgi dlls (native).

With this settings also Titanfall 2 or Battlefield 3/4 and hopefully also Battlefield V :-)
Please keep in mind some Games or Application need the nvapi..dll. You can use a special wine prefix or enable the nvapi..dlls entries in winecfg.

Good luck
lle

dj--alex
Level 3
Level 3
Posts: 59
Joined: Sun Aug 23, 2009 4:59 am

Re: Battlefield 1

Post by dj--alex » Tue Oct 09, 2018 4:11 pm

Your first man adequate answer on this topic on 10+ forums and social networks
Thank you! !

User avatar
Bob Wya
Level 12
Level 12
Posts: 2759
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Battlefield 1

Post by Bob Wya » Tue Oct 09, 2018 4:19 pm

lle wrote: ... NVIDIA 396.54.02 Driver. ...
Surely that should be: 396.54.06 ?
Or is there some regression, with these newer Vulkan beta drivers?

Bob

dj--alex
Level 3
Level 3
Posts: 59
Joined: Sun Aug 23, 2009 4:59 am

Re: Battlefield 1

Post by dj--alex » Tue Oct 09, 2018 7:11 pm

396.54.06 is outdated too
But i still don't know how to install Nvidia-410 (with Vulkan 1.1.82) into Linux Mint 19 and MX Linux 17.1
I thinking authors of distros hate new Nvidia drivers

User avatar
Bob Wya
Level 12
Level 12
Posts: 2759
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Battlefield 1

Post by Bob Wya » Tue Oct 09, 2018 7:24 pm

dj--alex wrote:396.54.06 is outdated too
But i still don't know how to install Nvidia-410 (with Vulkan 1.1.82) into Linux Mint 19 and MX Linux 17.1
I thinking authors of distros hate new Nvidia drivers
Often Nvidia don't port Vulkan beta features to the next beta version of their regular driver.
So Nvidia driver version 396.54.06 may be more up-to-date than driver version 410.57, for Vulkan features / bug fixes! :roll:
Of course Nvidia driver release notes, being what they are (i.e. rubbish), it's not exactly clear! :? :(

Btw there are plenty of Linux distributions that can give you bleeding edge packages (e.g. Arch, Gentoo, OpenSUSE Tumbleweed)...
You don't have to run Debian stable... :wink:

Bob

dj--alex
Level 3
Level 3
Posts: 59
Joined: Sun Aug 23, 2009 4:59 am

Re: Battlefield 1

Post by dj--alex » Sat Oct 13, 2018 9:32 am

this really works
1)removing nvapi64.dll Disable
only this dlss disable
2) turn on desktop mode (with blue @wallpaper@) on winecfg

https://www.youtube.com/watch?v=h8600EBqj18

Post Reply