project suddenly only works on Win 8 not Win 7
by Dwarf King · in Torque 3D Professional · 07/23/2013 (1:47 pm) · 3 replies
Dear Torque developers,
I have been working on a project on my win 8 machine for some time and then I moved it to a USB key and transferred it to a Win 7 machine where it also have worked perfectly all the time. However this time I get the annoying error
It happens as soon as a .dts models texture is going to be created
So the cannot map error is seen instead of the creating missing material for texture message in the console.
Now it still works like a charm on the Win 8 machine???
Steps tried to fix the issue:
run cleanShaders
run DeleteCacheDts
run DeleteDSOs
run DeletePrefs
run GenerateProjects
In visual studio:
clean solution
build solution
It seems that somehow the texture file of the .dts model got corrupted during the transfer from the other machine.
Is there any smart way of protecting the texture file from going nuts during a transfer? Have any of you seen something like it before?
Best,
Dwarf King
I have been working on a project on my win 8 machine for some time and then I moved it to a USB key and transferred it to a Win 7 machine where it also have worked perfectly all the time. However this time I get the annoying error
[Material::mapMaterial] - Cannot map unnamed Materialas the game crashes on load whenever I run it in release mode or debug mode in Torsion and same result in Visual Studio 2010 express.
It happens as soon as a .dts models texture is going to be created
[[MaterialList::mapMaterials] Creating missing material for texture: art/shapes/actors/something/something]
So the cannot map error is seen instead of the creating missing material for texture message in the console.
Now it still works like a charm on the Win 8 machine???
Steps tried to fix the issue:
run cleanShaders
run DeleteCacheDts
run DeleteDSOs
run DeletePrefs
run GenerateProjects
In visual studio:
clean solution
build solution
It seems that somehow the texture file of the .dts model got corrupted during the transfer from the other machine.
Is there any smart way of protecting the texture file from going nuts during a transfer? Have any of you seen something like it before?
Best,
Dwarf King
About the author
GG really went down the drain in the end. What a shame. Hoped for more.
#2
Remember that Windows often does a background copy to make things look like they're progressing faster than they really are, so maybe not all of the files were copied. This is why I wanted you to run it directly from the USB drive (in case it was ejected before copying was complete).
07/24/2013 (7:30 am)
Run it from the USB on both the Windows 8 and Windows 7 machines. It sounds like a material definition got corrupted. We had this issue when I was working on the warehouse packs. There were shared mapto's in the original files, which cause problems if both packs were used at the same time. If the materials.cs file gets munged, then it can cause problems since the last item loaded is the one referenced.Remember that Windows often does a background copy to make things look like they're progressing faster than they really are, so maybe not all of the files were copied. This is why I wanted you to run it directly from the USB drive (in case it was ejected before copying was complete).
#3
Nasty?? I better look out for that then. I check the "directory/folder issue" and I have maintained the same structure so I guess no solution there either.
I am on that right now, but it did not work I get the same same error so I am currently trying another USB stick and then I will see what will happen then. At least I found that 2 textures are causing the crash on load( the console are our friend and guide in good and bad times ). It runs smoothly when they are removed.
Thanks for your replies :o)
Best,
Dwarf King
07/24/2013 (8:26 am)
Quote:Additionally, I noticed 'recently, since I have been doing a TON of scripting' that some script errors will hang the engine and not be reported in the console. This instance usually occurs during the 'loading datablocks' segment of level loading.
Nasty?? I better look out for that then. I check the "directory/folder issue" and I have maintained the same structure so I guess no solution there either.
Quote:Run it from the USB on both the Windows 8 and Windows 7 machines. It sounds like a material definition got corrupted. We had this issue when I was working on the warehouse packs. There were shared mapto's in the original files, which cause problems if both packs were used at the same time. If the materials.cs file gets munged, then it can cause problems since the last item loaded is the one referenced.
I am on that right now, but it did not work I get the same same error so I am currently trying another USB stick and then I will see what will happen then. At least I found that 2 textures are causing the crash on load( the console are our friend and guide in good and bad times ). It runs smoothly when they are removed.
Thanks for your replies :o)
Best,
Dwarf King
Associate Ron Kapaun
3tdstudios.com
Sounds like a directory/folder issue. When you transferred from the Win 8 project to the Win 7, did you maintain the exact same directory structure? Back in the day, (TGE days) the engine would have kicked out an error stating something like "you do not have the correct art resources to run this project" or something to the like. I know it can happen in T3D but, I noticed as well that often it just hangs. Just a thought.
Additionally, I noticed 'recently, since I have been doing a TON of scripting' that some script errors will hang the engine and not be reported in the console. This instance usually occurs during the 'loading datablocks' segment of level loading.
Ron