Godot is not starting, I have two video cards, and two monitors, any suggestions?

LanceJZ

It seems that Godot does not like dual video cards. I'm using two R7s. When I had just one, it worked fine. Now I have two, and they are running in parallel and it is not getting past the DOS window that says, Detected monitors: 2 after the three EXEC PATHP??: Is there a setting I need to change? I searched the forum, but I did not find any useful information. I used General Chat because I could not find a category that fit.

Megalomaniak

Are you running godot in a windowed mode(probably yes)? I haven't really looked into it recently but it used to be that windowed applications couldn't use more than 1 gpu to render it, only applications rendered into their own fullscreen frame buffer could make use of sli/crossfire systems. Anyway's in your videocard drivers utility/app see if in the application specific settings you can't disable crossfire for godot.

Kiori

This fits the general chat, for all intents and purposes. I haven't seen anyone try this setup yet. And I'm not sure if you are talking about 'godot' the editor or 'godot' a game exported, IF it is what megalomaniak said, check this.

LanceJZ

Sorry I'll give more info. Windows 10 64bit, two R7 200 series default-window. The only change I made to the system was adding another card. Other video games such as Fallout 4 work great. I already tried changing every setting there is, it is a no go, that is why I posted. Sorry, turning off crossfire was the first thing I tried. It does not matter if it is a Godot exported game, or the editor, neither work. One more note, Godot causes the Radeon Settings manager to crash if it is run with it open. Here is my settings: Graphics Card Manufacturer - Powered by AMD Graphics Chipset - AMD Radeon R7 Graphics + R7 200 Dual Graphics Device ID - 6610 Vendor ID - 1002 SubSystem ID - 3011 SubSystem Vendor ID - 1462 Revision ID - 00 Bus Type - PCI Express 3.0 Current Bus Settings - PCI Express 3.0 x4 BIOS Version - 015.046.000.006 BIOS Part Number - xxx-xxx-xxx BIOS Date - 2014/07/07 01:36 Memory Size - 2048 MB Memory Type - DDR3 Memory Clock - 900 MHz Core Clock - 1100 MHz Total Memory Bandwidth - 28 GByte/s 2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0001

Kiori

LanceJZ said:

It does not matter if it is a Godot exported game, or the editor, neither work.

One more note, Godot causes the Radeon Settings manager to crash if it is run with it open.

</blockquote> To me this would sound like a bug. How can the engine 'cause' the settings manager to crash? I think this will need some looking into, my recommendation is that you post this on github as a bug report.

Megalomaniak

Have you tried running godot from the cli? The command line output might give some more useful info. I.E. Errors. @Kiori: I agree issue tracker is the right place but we might as well try helping LanceJZ dig up a bit more info first. :)

Kiori

@Megalomaniak yes of course. And the cli move is a good idea, anything that yields more information will help. One of the problems is only so many ppl have that specific setup. If you know anyone with 2 AMD's ask them to test it also. So we can verify if it's model specific or not. I also have another idea, download a version of ubuntu 16.04 create a bootable usb with the img,(pendrivelinux is one tool that does this, there are many) And try booting into ubuntu('trying' ubuntu, not installing). Not sure how familiar you are with this. If successful, try to download and run godot on linux. The latest Ubuntu forces the AMD OSS drivers on users, which i believe has no support for crossfire, so if the OS manages to render it's self fine, with your setup, it will be interesting to see what gives. :smiley: Having linux bootable devices around is always good anyways. You might have to do edit your bios options(boot order) to help it choose the usb over the hdd though.

LanceJZ

Well, Godot was not the only thing that would not work after all. Visual Studio 2015 would not open, same with 3DS Max. These apps also caused the Settings manager to crash if I had it open at the time. Photoshop works fine though. Funny that every Steam video game I tried works great at high FPS. I ended up unplugging the card. Thank you everyone for all the suggestions. I'm going to replace my AMD cards with a GTX OC 950, sure it cost more than the two cards, but I'm pretty sure it will work. I'm so done with Xfire.

Megalomaniak

You said that exported games had issues with the xfire setup so I do hope you will report to issue tracker because this is relevant to all of us, really. Well any of us who intend to target the PC platform.

yoann

Yep, i've found too that Godot editor makes AMD graphics drivers crash when Dual Graphics is enabled into the Catalyst control center. OS : Windows 10 pro 64bits CPU : AMD APU A8 7600 with  integrated Radeon R7 GPU : Integrated R7 + pcie Radeon R7 240 When Dual GRaphics option is disabled into Catalyst, Godot editor works fines. Since Wiondows 10 shows me a notification about the "AMD graphics driver that did not reply anymore", i guess it must be a bug on AMD side.

Megalomaniak

Have you reported this on the godot issue tracker and/or with AMD? Both are things that should be done I'm inclined to say, for the good of all of us, really. ;)

yoann

Not yet. I wanted to investigate a little bit more before ... but maybe will i open an issue on godot github. I have updated the drivers to the latest on my WIndows 10 machine. It replaced Catalyst by Crimson, and renamed "Dual Graphics" to "CrossFire", but other than that, it did not solve the issue with Godot. So I tried to set a custom profile for Godot that would disable Crossfire just for it, but it did not work as expected, Godot still made AMD driver crashing. There is also an AMD notification message related to "Wattman" that needed to be reset or something each time after the driver crashed. Will investigate more later.

yoann

Opened a issue in github here : https://github.com/godotengine/godot/issues/6502

Megalomaniak

Especially if the godot dev's agree that it's worth doing so consider also contacting amd support, since you're the person with that specific HW setup so you are the most fit to test out any potential/specific solutions they might be able to come up with. :) Also, note that at this point the thing to test is exported full-screen games/runtimes.

yoann

I tried full-screen exported games, and it crash too.

Kiori

About AMD, they've been dishing out crappy drivers for the past ten years, i think it's an ati tradition really. In the linux world the situation is so drastic everyone uses nvidia pretty much. When i first saw the post i thought -> "driver problem". But who knows right, maybe it wasn't entirely their fault this time. :weary: Buying AMD hardware can be exciting.

Megalomaniak

Yeah, excitingly I just ordered a Sapphire RX470 Nitro+ 8GB and now am waiting frantically checking to see if theres any progress on the package delivery. Aaaargh just bring it already!

Kiori

@yoann I saw your entries on github, so it seems it was a driver issue after all. Surprising. :neutral: Thumbs up for AMD.

Megalomaniak

Yup, excellent work, hope the check for crossfire goes in, because not every user, especially the gamers will necessarily figure this out for themselves and they shouldn't have to.

yoann

well, even if the patch i proposed is not merged into godot, and even if AMD fix their drivers before we publish our games or before godot 2.2 is released, we now know there is a way to detect when the driver crash (and change godot into a zombie process) during opengl initialisation of godot, and that we can compile our own release version of godot for windows with this patch included in case future version of AMD drivers contain a regression. (which seems to have occured a few time already) (wow that was a looooooong sentence.)