| Author |
Message |
|
Bob Wya
|
 Posted: Sat Apr 14, 2018 1:09 pm |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: ...
What to do next to get that version as default? Moving to /opt might run until next regular update.
How to get SIMS2 to the menu with starting from "myWine"?
... You can take the original Sims game .desktop launcher file and simply replace the default Wine path with: /home/frank/usr/bin/wine. To find the .desktop launcher(s) Wine automatically generates for the Sims 2: Code: find "${HOME}/.local/share/applications/" -iname "*sims*.desktop" For more in-depth information... Take a look at: Steam Client Launcher @ WineHQ AppDB :Steam / Official Release . I discuss there how to create a custom Steam Client .desktop launcher file. I'm not aware of this subject being discussed - in this detail - in any of the WineHQ official documentation. Bob
|
|
  |
|
 |
|
Bob Wya
|
Posted: Sat Apr 14, 2018 1:21 pm |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: Why kids...dogs are so much better...  SIMS 2 is also running with NVIDIA 340.104 so Hibernate will work again. Found out that my Quadro 600 isn't known to SIMS. Graphics quality is truly bad. Any idea? Thanks Frank Referring to: Bug 8051 - Sims 2 demo exits prematurely (comment 147)... Take a look at the Sims 2 graphics (textual) configuration files: Code: "${WINEPREFIX:-${HOME}/.wine}/drive_c/Program Files/EA GAMES/The Sims 2 An Introduction/TSData/Res/CSConfig/Graphics Rules.sgr"
"${WINEPREFIX:-${HOME}/.wine}/drive_c/Program Files/EA GAMES/The Sims 2 An Introduction/TSData/Res/CSConfig/Video Cards.sgr" ( those are the paths for the demo version of the Sims 2 - you'll need to mangle them!!) Usual rule applies!! Backup any files up - before you mess about with them!The log files, that the Sims 2 generates, are at: Code: "${WINEPREFIX:-${HOME}/.wine}/drive_c/users/${USER}/My Documents/EA Games/The Sims 2/Logs" Good luck with that! But like many old games - it'll probably need a bit of fiddling to get it working...  Bob
|
|
| |
|
|
|
freewind
|
Posted: Sun Apr 15, 2018 8:13 am |
|
 |
| Level 2 |
 |
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
Bob, Great job - Thank you. A last question, not sure you are the right one to answer: The .sgr files will be twice, one set in ..Res/CSConfig/ and one set in ..Res/Config/ The "Graphics Rules" are different, the "Video Cards" are equal. Which one will be for what? You know? Bob Wya wrote: Take a look at the Sims 2 graphics (textual) configuration files: Code: "${WINEPREFIX:-${HOME}/.wine}/drive_c/Program Files/EA GAMES/The Sims 2 An Introduction/TSData/Res/CSConfig/Graphics Rules.sgr"
"${WINEPREFIX:-${HOME}/.wine}/drive_c/Program Files/EA GAMES/The Sims 2 An Introduction/TSData/Res/CSConfig/Video Cards.sgr" Thanks Frank
|
|
| |
|
|
|
Bob Wya
|
Posted: Sun Apr 15, 2018 4:49 pm |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: Bob, Great job - Thank you.
A last question, not sure you are the right one to answer:
The .sgr files will be twice, one set in ..Res/CSConfig/ and one set in ..Res/Config/
The "Graphics Rules" are different, the "Video Cards" are equal.
Which one will be for what? You know?
... Np About the configuration files... I don't know... But I guess it's probably just CS=" Create-a-Sim": CSConfig vs. the actual game configuration: Config. I'd probably recommend starting by adding your graphics card to the Video Cards.sgr files. Just remember: - Alter one component at a time.
- Backup the files!
 Bob
|
|
| |
|
|
|
freewind
|
Posted: Mon Apr 16, 2018 4:48 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
Bob Wya wrote: About the configuration files... I don't know... But I guess it's probably just CS=" Create-a-Sim": CSConfig vs. the actual game configuration: Config. I'd probably recommend starting by adding your graphics card to the Video Cards.sgr files. Just remember: - Alter one component at a time.
- Backup the files!
Yeap, I'll do it. Thanks Frank
|
|
| |
|
|
|
freewind
|
Posted: Mon May 07, 2018 5:04 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
Hello and back again... after a long trail with NVIDIA Quadro 600 and no luck with the graphics in parts of the game, I have bought another card. An NVIDIA GeForce GTX 750 Ti with 2GB Mem. And...No luck...Same bad graphics on game. After resetting the registry key with the device id 1380 (GTX750Ti) the game starts, run fine the neighbourhood, run fine the building mode and in the family mode I got this well known bullshit screen. Equal what I do with detail settings in game, the problem persists. It looks nearly same as with the Quadro 600. Only difference is, that the building mode works fine. So I think the game is running fine with a supported card like GTX750Ti under Windows. But with Wine it works not in fully. Attachment:
SIMS2 screen.jpeg [ 136.64 KiB | Viewed 1549 times ]
For Info from CUDA-Z Code: CUDA-Z Report
=============
Version: 0.10.251 64 bit http://cuda-z.sf.net/
OS Version: Linux 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64
Driver Version: 390.48
Driver Dll Version: 9.10 (390.48)
Runtime Dll Version: 6.50
Core Information
----------------
Name: GeForce GTX 750 Ti
Compute Capability: 5.0
Clock Rate: 1254.5 MHz
PCI Location: 0:2:0
Multiprocessors: 5 (640 Cores)
Threads Per Multiproc.: 2048
Warp Size: 32
Regs Per Block: 65536
Threads Per Block: 1024
Threads Dimensions: 1024 x 1024 x 64
Grid Dimensions: 2147483647 x 65535 x 65535
Watchdog Enabled: Yes
Integrated GPU: No
Concurrent Kernels: Yes
Compute Mode: Default
Stream Priorities: Yes
Memory Information
------------------
Total Global: 2001.81 MiB
Bus Width: 128 bits
Clock Rate: 2700 MHz
Error Correction: No
L2 Cache Size: 48 KiB
Shared Per Block: 48 KiB
Pitch: 2048 MiB
Total Constant: 64 KiB
Texture Alignment: 512 B
Texture 1D Size: 65536
Texture 2D Size: 65536 x 65536
Texture 3D Size: 4096 x 4096 x 4096
GPU Overlap: Yes
Map Host Memory: Yes
Unified Addressing: Yes
Async Engine: Yes, Unidirectional
Performance Information
-----------------------
Memory Copy
Host Pinned to Device: 5895.37 MiB/s
Host Pageable to Device: 4892.86 MiB/s
Device to Host Pinned: 6343.72 MiB/s
Device to Host Pageable: 4953.95 MiB/s
Device to Device: 32.5817 GiB/s
GPU Core Performance
Single-precision Float: 1205.98 Gflop/s
Double-precision Float: 52.2594 Gflop/s
64-bit Integer: 73.4433 Giop/s
32-bit Integer: 379.557 Giop/s
24-bit Integer: 263.192 Giop/s
Generated: Mon May 7 11:41:52 2018 Output from Wine: Code: frank@dell2:~$ /home/frank/usr/bin/wine /home/frank/.wine/drive_c/"Program Files (x86)"/"EA GAMES"/"Die Sims 2"/TSBin/Sims2.exe
000b:fixme:winediag:start_process Wine Staging 3.5 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
0009:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0.
0009:fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
0009:fixme:imm:ImmDisableTextFrameService Stub
0009:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:wbemprox:client_security_SetBlanket 0x7bdfa814, 0x29f18b8, 10, 0, (null), 3, 3, (nil), 0x00000000
0009:fixme:wbemprox:client_security_Release 0x7bdfa814
0009:fixme:wbemprox:enum_class_object_Next timeout not supported
0009:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
0009:fixme:setupapi:CM_Get_Child 0x329164 0x02a0c518 0x00000000: stub
0009:fixme:setupapi:CM_Open_DevNode_Key 0x00000000 0x00020019 0x00000000 0x00000001 0x329158 0x00000001 : stub
0009:fixme:ddraw:ddraw7_Initialize Ignoring guid {67685559-3106-11d0-b971-00aa00342f9f}.
0009:err:d3d:resource_init Failed to allocate system memory.
0009:err:d3d:resource_init Failed to allocate system memory.
0009:fixme:d3d9:Direct3DShaderValidatorCreate9 stub
0009:fixme:d3d9:uisv_4par uisv_4par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_1par uisv_4par called
0009:fixme:d3d:resource_check_usage Unhandled usage flags 0x10.
0009:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3:
0009:fixme:d3d_shader:print_glsl_info_log Vertex info
0009:fixme:d3d_shader:print_glsl_info_log -----------
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[0].zw" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized
0009:fixme:imm:ImmGetOpenStatus (0x2b5f630): semi-stub
0009:fixme:imm:ImmReleaseContext (0x2006c, 0x2b5f630): stub
0009:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #6:
0009:fixme:d3d_shader:print_glsl_info_log Vertex info
0009:fixme:d3d_shader:print_glsl_info_log -----------
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[0].zw" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #9:
0009:fixme:d3d_shader:print_glsl_info_log Vertex info
0009:fixme:d3d_shader:print_glsl_info_log -----------
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[0].zw" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized
0009:fixme:d3d9:uisv_4par uisv_4par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_1par uisv_4par called
0009:fixme:d3d9:uisv_4par uisv_4par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_5par uisv_5par called
0009:fixme:d3d9:uisv_1par uisv_4par called
...
0009:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #92:
0009:fixme:d3d_shader:print_glsl_info_log Vertex info
0009:fixme:d3d_shader:print_glsl_info_log -----------
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized
0009:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #96:
0009:fixme:d3d_shader:print_glsl_info_log Vertex info
0009:fixme:d3d_shader:print_glsl_info_log -----------
...
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d9:uisv_4par uisv_4par called
...
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:err:winediag:shader_generate_glsl_declarations The hardware does not support enough uniform components to run this shader, it may not render correctly.
0009:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #183:
...
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
0009:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
0009:fixme:d3d9:uisv_4par uisv_4par called Maybe someone is able to point me to a solution. Thanks Frank
|
|
| |
|
|
|
Bob Wya
|
Posted: Mon May 07, 2018 6:10 am |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: ... Output from Wine: Code: 0009:fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
... First off - you need to fix this error. Probably: Code: apt-get install libtxc-dxtn-s2tc0 libtxc-dxtn-s2tc0:i386 for Ubuntu. Nick-picking, but ideally you'd want to start the Sims executable with: Code: /home/frank/usr/bin/wine start /unix "/home/frank/.wine/drive_c/Program Files (x86)/EA GAMES/Die Sims 2/TSBin/Sims2.exe" This is covered in the Wine User's Guide: 3.1 How to install and run Windows programs. Can you supply the full build log for your custom built version of Wine Staging 3.5? This may just not be configured correctly...  That might need to go to a Pastebin-esque site - as they can get quite big... If the file is compressed - you can do something like: Code: sudo apt-get install xclip
gunzip -c <log file path> | xclip -i -selection clipboard # For gzip / gz compressed log files To put the log file in your Desktop Environment clipboard - for easy pasting on the paste website. Obviously if you want to get really sophisticated you can use pastebinit ... E.g.: Code: gunzip -c <log file path> | xclip -i -selection clipboard | pastebinit -b http://pastebin.com Thanks Bob
|
|
| |
|
|
|
freewind
|
Posted: Mon May 07, 2018 7:16 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
|
| |
|
|
|
Bob Wya
|
Posted: Mon May 07, 2018 7:52 am |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: ... Here is the Logfile: http://ge.tt/6pca3ip2Leave that with me... The log looks fine - so I'll need to get my pondering cap on... freewind wrote: That looks good... The former package is just a wrapper for the version-specific latter package (i.e. they are the same thing!) Just make sure you get the full multi-lib package installed: Code: apt-get install libtxc-dxtn libtxc-dxtn:i386 I'd retest the game, after installing this library, just in case this is the actually the only issue you have... Missing this vital texture compression library causes all kinds of Wine weirdness for many 3D games... Essentially some or all textures can't decompressed so you'll get visual artefacts... Bob
|
|
| |
|
|
|
freewind
|
Posted: Mon May 07, 2018 8:02 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
Where did you found them? I get Code: sudo apt-get install libtxc-dxtn libtxc-dxtn:i386
[sudo] Passwort für frank:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Paket libtxc-dxtn kann nicht gefunden werden. (not found)
E: Paket libtxc-dxtn:i386 kann nicht gefunden werden. (not found)
|
|
| |
|
|
|
Bob Wya
|
Posted: Mon May 07, 2018 8:22 am |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: Where did you found them? I get Code: sudo apt-get install libtxc-dxtn libtxc-dxtn:i386
[sudo] Passwort für frank:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Paket libtxc-dxtn kann nicht gefunden werden. (not found)
E: Paket libtxc-dxtn:i386 kann nicht gefunden werden. (not found)
You've already found them... However you haven't enabled the ppa containing them... See: xorg-edgers ppa. Shouldn't cause any problems installing all of those ppa packages - when using the Nvidia proprietary driver... Bob
|
|
| |
|
|
|
freewind
|
Posted: Mon May 07, 2018 8:43 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
Not Found! sudo add-apt-repository ppa:xorg-edgers/ppa == Xorg packages fresh from git == Currently supported releases are Xenial/16.04 and Yakkety/16.10Code: OK:9 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu bionic InRelease
frank@dell2:~$ sudo apt-get install libtxc-dxtn libtxc-dxtn:i386
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Paket libtxc-dxtn kann nicht gefunden werden. (not found)
E: Paket libtxc-dxtn:i386 kann nicht gefunden werden. (not found)
Maybe I'm wrong or tiered or somewhat 
|
|
| |
|
|
|
Bob Wya
|
Posted: Mon May 07, 2018 9:06 am |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: ... Maybe I'm wrong or tiered or somewhat You're pretty much on your own there...  The Ubuntu xorg-edgers PPA page I linked to was actually already filtered for Bionic packages. rant  This is why I use Gentoo. IMHO the whole Debian / Ubuntu package management system is really busted... Launchpad is rusty old trainwreck... Witness the number of projects jumping the sinking ship to Github... I'm always finding crap like this when I try to use Ubuntu. Things definitely don't "just work". Why would Canonical push snaps so hard? Answer: because they know native PPA packages often have conflicts... /rantFile a bug on Launchpad or ask a question on Ask Ubuntu... Bob
|
|
| |
|
|
|
freewind
|
Posted: Tue May 08, 2018 2:29 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
from askubuntu.com Code: I went to the PPA's Launchpad page and the info section states that the packages it provides are only for 16.04 and 16.10...also there's this warning: "WARNING: Do not use this PPA with enabled HWE stack." If I'm not mistaken, 18.04's default kernel does have HWE stack enabled. Furthermore it says not to install packages individually: "This PPA is currently meant to be used as a whole. Please do not individually install packages from it, add it to your sources and let your package manager pull in every update..."
See PPA:xorg-edgers/ppa. Lastly, you had the package name wrong (it's not libtxc-dxtn:i386), but it doesn't really matter since you're advised not to install packages individually
And now? Could this be an alternative: https://pkgs.org/download/libtxc-dxtn0
|
|
| |
|
|
|
freewind
|
Posted: Fri May 18, 2018 12:35 pm |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
OK, time goes by.... Back to 17.10 & NVIDIA 340 because 390 won't work with Artful ... Installed libtxc-dxtn-s2tc + libtxc-dxtn-s2tc:i386 Major failure "fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable" fixed. Same problem. Code: frank@dell2:~$ wine --version
wine-3.8 (Staging)
frank@dell2:~$ /home/frank/usr/bin/wine start /unix "/home/frank/.wine/drive_c/Program Files (x86)/EA GAMES/Die Sims 2/TSBin/Sims2.exe"
000b:fixme:winediag:start_process Wine Staging 3.5 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
frank@dell2:~$ 002f:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0.
002f:fixme:imm:ImmDisableTextFrameService Stub
002f:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
002f:fixme:wbemprox:client_security_SetBlanket 0x7c288814, 0x29c90c8, 10, 0, (null), 3, 3, (nil), 0x00000000
002f:fixme:wbemprox:client_security_Release 0x7c288814
002f:fixme:wbemprox:enum_class_object_Next timeout not supported
002f:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
002f:fixme:setupapi:CM_Get_Child 0x339164 0x029e4590 0x00000000: stub
002f:fixme:setupapi:CM_Open_DevNode_Key 0x00000000 0x00020019 0x00000000 0x00000001 0x339158 0x00000001 : stub
002f:fixme:ddraw:ddraw7_Initialize Ignoring guid {67685559-3106-11d0-b971-00aa00342f9f}.
002f:err:d3d:resource_init Failed to allocate system memory.
002f:err:d3d:resource_init Failed to allocate system memory.
002f:fixme:d3d9:Direct3DShaderValidatorCreate9 stub
002f:fixme:d3d9:uisv_4par uisv_4par called
002f:fixme:d3d9:uisv_5par uisv_5par called
...
002f:fixme:d3d:resource_check_usage Unhandled usage flags 0x10.
002f:fixme:imm:ImmGetOpenStatus (0x2b37b48): semi-stub
002f:fixme:imm:ImmReleaseContext (0x20072, 0x2b37b48): stub
002f:fixme:d3d9:uisv_4par uisv_4par called
...
002f:fixme:d3d9:uisv_1par uisv_4par called
002f:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
002f:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
002f:fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet.
002f:err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0
002f:fixme:d3d9:uisv_4par uisv_4par called
002f:fixme:d3d9:uisv_5par uisv_5par called
...
002f:err:winediag:shader_generate_glsl_declarations The hardware does not support enough uniform components to run this shader, it may not render correctly.
Anything I can provide? Like an Export somewhat? Thanks Frank
|
|
| |
|
|
|
freewind
|
Posted: Tue May 22, 2018 3:48 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
No idea... Back to windows...? 
|
|
| |
|
|
|
Bob Wya
|
Posted: Tue May 22, 2018 7:06 am |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: No idea... Back to windows...? When people type statements like that it simply tells me you're only in the phase of dipping your toes in... Probably you should be dual-booting or just using Windows (with the Linux subsystem thingy perhaps). I'll take a look tomorrow. Is there any chance you can post the full log? There might be something I'm missing in your edits (unless it's purely for line duplication). Dropping the package for 18.04 is probably connected with the fact that the patient has expired on the S3 Texture Compression compression algorithm. I know there was talk of Mesa picking up the library - but I don't think they are bundling it just yet... Bob
|
|
| |
|
|
|
freewind
|
Posted: Tue May 22, 2018 9:16 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
Because of the crying kids... I have a free disk with Win7 and SIMS2 for playing... But I hate always rebooting between the OS's. > There might be something I'm missing in your edits (unless it's purely for line duplication)I have inserted " ..." where I believe it is duplicate stuff. Give me a hint to pipe the output to a file. I have tried things like > or tee with the export command, but I'm not experienced enough that it worked. Did you wanna the output from term or from export? Thanks for your efforts Frank
|
|
| |
|
|
|
Bob Wya
|
Posted: Tue May 22, 2018 5:02 pm |
|
Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2470
Location: Cambridge
|
freewind wrote: Because of the crying kids... I have a free disk with Win7 and SIMS2 for playing... But I hate always rebooting between the OS's. > There might be something I'm missing in your edits (unless it's purely for line duplication)I have inserted " ..." where I believe it is duplicate stuff. Give me a hint to pipe the output to a file. I have tried things like > or tee with the export command, but I'm not experienced enough that it worked. Did you wanna the output from term or from export? Thanks for your efforts Frank There is a bit of steep learning curve moving from Windows to Linux. The former holds your hand in a vice-like grip and the latter holds your hand... till it lets go... The trouble with Wine is it's so patchy. I was playing GTA IV, with the new DXVK DX11➡ Vulkan translation layer the other day. Very impressive performance... Yet you can't even get an old game, like the Sims 2 to work... A lot of the problems Wine has are with bad coding practices in Windows games/ applications and heavy-handed DRM measures. If you want to redirect wine output to a file it's something like (BASH shorthand): Code: /home/frank/usr/bin/wine start /unix "/home/frank/.wine/drive_c/Program Files (x86)/EA GAMES/Die Sims 2/TSBin/Sims2.exe" &>~/wine_sims2_log.txt or for other shells, long-hand form: Code: /home/frank/usr/bin/wine start /unix "/home/frank/.wine/drive_c/Program Files (x86)/EA GAMES/Die Sims 2/TSBin/Sims2.exe" 1>~/wine_sims2_log.txt 2>&1 Essentially this means: "redirect the stdout (1) stream to the log file, then redirect the stderr (2) stream to the same target as the stdout stream". If you then want to paste this log file in the forum, or a Pastebin-type site, you can put it in your Desktop Environment clipboard buffer thusly: Code: cat ~/wine_sims2_log.txt | xclip -i -selection clipboard Assuming you have the xclip utility installed. There are also command line tools that will directly paste to a specified pastebin-type site. Bob
|
|
| |
|
|
|
freewind
|
Posted: Wed May 23, 2018 7:58 am |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
I believe in you... I also have tried it with VirtualBox without success. The VM is packing a virtual driver over the graphics card. This will work with dxdiag and fulfilled the 2d + 3d tests. But the game isn't realize the cards specs. Log-File is 1.7 GB raw as wine_sims2_log1.7z on http://ge.tt/3gJwZtp2 with 309 KB Hope you can find something helpful. Thanks Frank
|
|
| |
|
|
|
freewind
|
Posted: Mon May 28, 2018 12:24 pm |
|
|
| Level 2 |
|
|
|
Joined: Mon Apr 09, 2018 9:04 am
Posts: 28
|
|
Is that the saddest truth in fact?
> Yet you can't even get an old game, like the Sims 2 to work...
|
|
| |
|
|
|
citrusalex
|
Posted: Sat Oct 27, 2018 7:27 pm |
|
|
| Newbie |
 |
|
|
Joined: Fri Jun 01, 2018 5:04 am
Posts: 3
|
You should try this Lutris installer I made for Sims 2, it should work with new graphics drivers: https://lutris.net/games/the-sims-2/And if you still exeprience that issue when characters explode and get all garbled up like on your screenshot, you need to open in-game debug console and type in "boolProp useShaders true"
|
|
| |
|
|
|
