Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Transparent Textures Eras DX9-64bit

A topic by zaldronthesage created Aug 18, 2019 Views: 252 Replies: 6
Viewing posts 1 to 7

Hey there!


I just stumbled upon this game engine and the Eras mod and I have to say I am quite inpressed at the feat you have pulled off in the creation of this game. A quick question though: When I get in the game all of the characters are transparent in addition to the buildings. Maybe there is a setting to correct this or something I need to install as a prerequisite? Any information would be great. I am running windows 10 with a 1080ti GPU.

That is strange.  Can you send me a screenshot and also the system.log file?  Also, is that 1080ti a GeForce card?

Email is chezjfrey at hotmail dot com and you can attach files, or you can upload to some file share site and give me a link.

(1 edit)

Also, you may want to install the Redist June 2010 DirectX 9.0c even though Windows 10 is not listed as supported.  I found some info online that can sometimes lead to problems with the newer GeForce on Win10 and it needs explicit install.  The media is included in Maelstrom (directx_Jun2010_redist.exe) and the engine is using 9.0c specifically and I've tested on Win10 and it works, but I cannot say specifically with GeForce because I don't have that card; but generally the game works on the Win10 machines I've tried with generic Intel graphics.

Okay, let me try to install that and see if there is anything I can tweak on my end. Thank you for your help so far!

(1 edit)

So I figured out what was doing it. If you are in the settings launcher, and you select Antialiasing on any level, you get missing textures. With it off it looks fine. All other options are on high and I am running in 2k resolution.

I have sent an email to you with the attached screen shot.

Got this same issue. Or at least I think I do.




Straight out of an horror movie... But yeah, turning off anti aliasing fixes it for me too. I thought it was the fault of MFAA at first but apparently turning that off in the NVIDIA control panel doesn't make a difference.