Any ideas. (win 10)
Jump to content
Posted 25 January 2017 - 05:35 PM
Looks like you are having GPU issues per a number of your recent postings. Perhaps you need to reign back your expectations given your current project and hardware?
Posted 25 January 2017 - 05:52 PM
NVIDIA GeForce GTX 1060 6GB
I7-6800K 3.4 GHz (6 cores)
And the project is a simple hotel room...
See attached screen shot for next problem, what could cause this? I have scaled my texture but upon rendering it reverts back...
Im really sorry to be a pain!
Posted 25 January 2017 - 06:47 PM
Regarding the mxm file association issue, can you enable the display of file extensions and then post back another screen capture showing the file in your directory?
Regarding the texture map issue, is this material being created by "Translate Shaded" (auto-translate) or by a referenced MXM?
Posted 25 January 2017 - 07:05 PM
Posted 26 January 2017 - 11:55 AM
Thanks Ben I will take a look at that and see if it effects anything... I cant see how that would cause the new MXM to be saved as a layout autosave file though.
Have you any thoughts regards to post number 3?
Posted 26 January 2017 - 06:37 PM
My suggestion was in response to post #3. (Please try to create separate topics for different issue in the future; it makes them a lot easier to keep track of.)
Posted 27 January 2017 - 04:48 PM
In response to the MXM file extension issue: It appears that the Windows version of the MXM Material Editor is not automatically adding the .mxm file extension. This will be fixed in a future release.
For now, when saving the material, manually add ".mxm" to the filename and it will work correctly. If you have existing MXMs without extensions, you should be able to restore them to proper operation by manually adding the extension ".mxm" to the filename.
0 members, 0 guests, 0 anonymous users