Dragon Age: Origins Ultimate Edition (47810)

[MrWissenschaft]

Hello there,

I was wondering if anyone knew of any workarounds to get Dragon Age: Origins working with Steam Play or if not what information is need from me in order to log the issues I am having etc.

It doesn't seem to happen during the game itself, seems to occur during character creation only. Textures may appear as just black, the hair on head and face may not load at all or the character creation menus will appear as just black also.

One last thing is when this happens, even after getting through all of those problems, once getting through character creation and playing the game, the game will crash to desktop.

Please let me know if there is anything you need of me, including any logs etc. (info on how to attain the specific logs would be super helpful too)

Thanks guys

[MrWissenschaft]

https://gist.github.com/MrWissenschaft/19d7a73c997a2af6998bf240f6a70dfc

[nstgc]

For what its worth, I just tested that. Are you using Proton 3.7.4 or 3.7.3? Perhaps that it?

[MrWissenschaft]

I've tried 3.7.3 and 3.7.4, it didn't seem to happen when changing settings to "low", could that be it do you reckon?

[nstgc]

I doubt it. Save for MSAA, everything is maxed out on my system (for me MSAA>4 is wasted electricity). Your systems is much stronger than mine (CPU 3 gens newer and a 1080 ti vs 950).

[nstgc]

@MrWissenschaft What graphics drivers are you using? Ubuntu tends to have old stuff, so perhaps that's it? For what its worth, this game is working perfectly for me. In fact, I can't remember it ever playing this smoothly.

[stratus-ss]

I have CTD with Dragon Age Origins Ultimate Edition after starting a new game. The Warden Intro video plays but then immediately CTD.

System info gist: https://gist.github.com/stratus-ss/73e90ae7dcc42caf324190ea36e979cc

The log ended up being 39M and too big to fit in a gist so I attempted to remove duplicate lines and capture unique lines but there may be information missing

Log gist: https://gist.github.com/stratus-ss/f2d32908e1b61a33c4ec51f3178cc02b

[nstgc]

@stratus-ss Would it be helpful if we compared installed packages? I'm also on Arch, but it works better than I remember it running on Windows, and I have about 12GB of mods installed (mostly script heavy stuff) which is about twice what I was using before.

[MrWissenschaft]

Hello, I am on Ubuntu 18.04 LTS, with the PPA drivers installed, currently on nvidia driver version 396.54. I just can't work out why it's working perfectly for some people but not very well at all for some others. Could try a fresh arch install on my other SSD and give that a crack, but that seems like a whole lot of effort.

Any recommendations at all chaps?

[nstgc]

I can't tell for certain if I'm seeing a regression in proton 3.7.5, or if I hadn't played long enough, but its no longer working perfectly. I'm getting the occasional CTD, random black textures, and all-black cut scenes. So far, nothing that can't be solved by restarting.

I'll probably got log outputs tomorrow.

[MrWissenschaft]

That's so strange because 3.7.5 is working fine for me now! I'll keep you guys updated if the problem reappears.

Yes I will output logs also should it happen again.

[stratus-ss]

I now get a CTD immediately upon getting to the character creation screen

New gist: https://gist.github.com/stratus-ss/5b5d45940f78db6fe9d6f1ea96743fa2

[nstgc]

I'm not seeing CTDs (saving regularly prevents them if the issue is memory), but I have identified that the UE DLC isn't working. I'm not sure what the issue, but mods work. I'd say that the issue is in the program that sets up the addins, but I started fresh on Windows 7 and copied the resulting My Documents/Bioware/Dragon Age directory into place on Arch.

[omicron-b]

I am playing a standard version of this game + Awakening DLC and PROTON_USE_WINED3D11=1 must be used to fix graphical issues, can you try that for Ultimate?

Also I came up with a fix for DLCs here: #1144 (comment)
Obviously the steps are a bit more complicated for multiple DLCs, I guess you will need to add multiple XML blocks, one for each DLC, copy everything between and including <AddInItem UID= and </AddInItem> from each manifest.xml and leaving only </AddInsList> as a last line.

[tr37ion]

Well, I didn't set anything special. I just found out disabling Framebuffer Effects in-game Video settings brings back nice textures. Everything else is set to max.

[kisak-valve]

Dragon Age: Origins Ultimate (47810)

Issue transferred from #1665.
@tr37ion posted on 2018-10-01T22:49:00:

Compatibility Report

• Name of the game with compatibility issues: Dragon Age: Origins Ultimate
• Steam AppID of the game: 47810

System Information

• GPU: GTX1070
• Driver/LLVM version: Nvidia 410.57
• Kernel version: 4.18.10-arch1-1-ARCH
• Proton version: 3.7-6

I confirm:

• [✔] that I haven't found an existing compatibility report for this game.
• [✔] that I have checked whether there are updates for my system available.

Symptoms

1. Textures are low resolution (see Dragon Age: Origins Ultimate Edition (47810) #749) and shaders are broken if Frambuffer Effects is activated
2. If switching to Desktop and back (Plasma 5.13.5) the mouse and keyboard input is broken.

I added this general report cause the other one #749is very specific and this one adds the mouse/keyboard issue, too.

[shoober420]

Whitelist Request

• Name of the game to be whitelisted: Dragon Age: Origins - Ultimate Edition
• Steam AppID of the game: https://steamdb.info/app/47810/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.59
• Distro version: Arch
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 4.11-12

Works great out of the box, even better with "PROTON_USE_D9VK=1".

[kisak-valve]

Hello, is anyone seeing an issue with this game and Proton 4.11 that would block it from being whitelisted?

[nstgc]

@kisak-valve I have not tested this recently, but with previous versions I had issues with the DLC not registering properly. I'll try and test this this weekend.

[nstgc]

It's been a while since I played DA:O due to DLC not working, so a lot might have changed between now and then. Which is my lead-in to "it crashes when I load a save". That is to say "it's regressed" however looking at this closer I'm wondering if the save is corrupted. I also had to kill a couple running processes to get it to stop.

I validated the game data, but all files are clean.

Crash log
System info

I'm not sure exactly what is going on here. By manually choosing pretty much any other save, the game loads properly and appears to run well from a performance stand point. I did not check to make sure that DLC locations were on the map. I was mostly interested in diagnosing the crash. I'll check that later.

[kisak-valve]

Tracking note: Missing decoder: Advanced Streaming Format (ASF) (video/x-ms-asf) in the log should be resolved before whitelisting this game.

[STiAT]

Dragon Age: Origins Ultimate (47810)

Compatibility Report

• Name of the game with compatibility issues: Dragon Age: Origins Ultimate
• Steam AppID of the game: 47810

System Information

• GPU: GTX 3070Ti
• Driver/LLVM version: LLVM 12.0.1, Nvidia proprietary 470.63.01
• Kernel version: 4.5.14.7-198.current
• Proton version: Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

• Game crashes on ALT+TAB if started fullscreen (or switched to fullscreen lateron)

Options passed to the game:

• DXVK_LOG_LEVEL=debug DXVK_LOG_PATH=/home/schurl PROTON_LOG=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%

DAOrigins_d3d9.log
steam-47810.log

[agolp]

Bug report: cannot launch the game.

The game launcher starts fine, with sound, but when I press "Play" or "Configure", it crashes shortly after displaying a GUI that disappears too quickly to read with a divide by zero error in the log files.

Launch options:
DXVK_LOG_LEVEL=debug DXVK_LOG_PATH=/tmp PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_LOG=1 %command%

My hardware is the following:

• AMD 5950x
• Nvidia 3090 (with the official nvidia drivers)
• 128 Gb of RAM.

I have forced the use of Proton Experimental and unchecked both the Steam Overlay and Desktop Game Theatre. I tried every Proton version in the list, with the same result. I have two monitors, and I tried disabling one and reducing the resolution and disabling any scaling, with no luck. I've also tried both Wayland and Xorg (the attached log files are from a Xorg session).

I've successfully run Proton games before on the same hardware and software configuration.

Please find attached the relevant log files and my system information:

steam-47810.log
2021-10-29_003105_appid-47810_crash.log
system_information.txt

[ahjolinna]

I have same exact same issue as @agolp (but I'm using experimental-bleeding-edge and the GE7-18) here is my log: steam-47810.log

---

my system specs:

             .;ldkO0000Okdl;.                ahjolinna@localhost
         .;d00xl:^''''''^:ok00d;.            OS: openSUSE 20220611
       .d00l'                'o00d.          Kernel: x86_64 Linux 5.18.2-1-default
     .d0K^'  Okxoc;:,.          ^O0d.        Uptime: 20h 52m
    .OVVAK0kOKKKKKKKKKKOxo:,      lKO.       Packages: 2750
   ,0VVAKKKKKKKKKKKKK0P^,,,^dx:    ;00,      Shell: bash bash 5.1.16
  .OVVAKKKKKKKKKKKKKk'.oOPPb.'0k.   cKO.     Resolution: 3840x2160
  :KVAKKKKKKKKKKKKKK: kKx..dd lKd   'OK:     DE: KDE 5.95.0 / Plasma 5.25.80
  lKlKKKKKKKKKOx0KKKd ^0KKKO' kKKc   lKl     WM: KWin_Wayland
  lKlKKKKKKKKKK;.;oOKx,..^..;kKKK0.  lKl     GTK Theme: Breeze-dark [GTK2/3]
  :KAlKKKKKKKKK0o;...^cdxxOK0O/^^'  .0K:     Icon Theme: Papirus
   kKAVKKKKKKKKKKKK0x;,,......,;od  lKP      Disk: 15T / 21T (73%)
   '0KAVKKKKKKKKKKKKKKKKKK00KKOo^  c00'      CPU: AMD Ryzen 7 5700G with Radeon Graphics @ 16x 4.3GHz
    'kKAVOxddxkOO00000Okxoc;''   .dKV'       GPU: NVIDIA GeForce RTX 3060 Ti (Driver v515.43.04)
      l0Ko.                    .c00l'        RAM: 5322MiB / 15771MiB
       'l0Kk:.              .;xK0l'         
          'lkK0xc;:,,,,:;odO0kl'            
              '^:ldxkkkkxdl:^'  

[kisak-valve]

Hello @ahjolinna, your log disagrees with you. In your case, these look likes some lines of interest:

err:module:import_dll Library PhysXLoader.dll (which is needed by L"Z:\\home\\ahjolinna\\.local\\share\\Steam\\steamapps\\common\\Dragon Age Ultimate Edition\\bin_ship\\NxCharacter.dll") not found
err:module:import_dll Library NxCharacter.dll (which is needed by L"Z:\\home\\ahjolinna\\.local\\share\\Steam\\steamapps\\common\\Dragon Age Ultimate Edition\\bin_ship\\DAOrigins.exe") not found
trace:loaddll:build_module Loaded L"Z:\\home\\ahjolinna\\.local\\share\\Steam\\steamapps\\common\\Dragon Age Ultimate Edition\\bin_ship\\NxCooking.dll" at 02420000: native
err:module:import_dll Library PhysXLoader.dll (which is needed by L"Z:\\home\\ahjolinna\\.local\\share\\Steam\\steamapps\\common\\Dragon Age Ultimate Edition\\bin_ship\\DAOrigins.exe") not found

There's no mention of PhysX-related trouble in the older log.

Maybe something abnormal happened with [...]/redist/PhysX_9.09.0408_SystemSoftware.exe and the game's first run setup?

[ahjolinna]

@kisak-valve well it seems game works fine with proton 6.3-8 (as is mentioned in protondb website) it did some setup (pkgs installation) that experimental didn't, here its logs steam-47810.log

now when I tried to play with experimental again after 6.3 it seems to work just fine, it seems the problem is that experimental (and 7.x) doesn't install the needed pkgs anymore for the game to work like 6.3 did

here is experimentals logs for fun : steam-47810.log

[rski]

I'm surprised the game works for everyone else from the get go, it took me a bit (PROTON_LOG=1 %command% in launch options is a neat trick I learned in the process), but I had to run

WINEARCH=win32 protontricks 47810 msxml3
WINEARCH=win32 protontricks 47810 physx

to get it to run; physx because NxCharacter.dll and another physx dll were missing, and msxml3 because the physx installation failed otherwise.
Without these the launcher started but the game did not, with no errors anywhere. This was on nixos 22.11pre418157.104e8082de1 (Raccoon) and proton 6.3

[Blisto91]

Alt-tab crash should now be fixed in dxvk upstream.
Will arrive in bleeding edge shorty and regular experimental whenever they pull in the changes.

Edit: It's in regular experimental now

[cakeisamadeupdrug]

I have the disk version but I've been having the same issue as you guys with Steam and agonising with this for a few days, but then I happened to go into bin_ship and opened daorigins.exe directly with Wine and it just worked. Turns out the launcher has known issues on all platforms. Have you tried bypassing it entirely?

[kisak-valve]

Dragon Age: Origins configuration utility can't handle large core counts

Issue transferred from #6417.
@literal-0x4e posted on 2022-12-27T13:37:22:

The configuration utility in Dragon Age: Origins - Ultimate Edition (47810) crashes on machines with too many^[1] CPU cores with an error like this:
wine: Unhandled division by zero at address 00470631 (thread 016c), starting debugger...
which looks like simply a legacy code issue of not foreseeing high core counts in the future

While this would otherwise be harmless, as the game itself can adjust all the settings the configuration utility can, this becomes a problem because the game launcher insists of running the configuration utility if no config file is yet written, refusing to launch the game until there is one. This results in a kind of a accidental denial of service, as while the game itself runs fine with many cores, the configuration utility gets launched instead, to write the config file, which it cannot do due to crashing – a sort of a chicken and egg situation.

Workaround: disabling some cores in BIOS if possible, until a configuration file is written by the utility OR copying over a config file allows to launch the game.

[1] I experience this on Ryzen 9 5950X, which is 16c/32t CPU, but it works fine if I disable half of the cores. Also works fine on a Ryzen 7 5700G, which is 8c/16t. The configuration utility reports each thread as a physical core, so the thread count is what really matters. Therefore, the threshold of how many cores-actually-threads it can handle at most must be somewhere within the range of 16-31 threads or "cores".

[kisak-valve]

Hello @literal-0x4e, give #5927 a read.