-  Mon Jul 02, 2007 7:12 pm
					 #235537
						        
										
										
					
					
							(sorry fo the caps)
i will explain why with just 2 examples :
1) everytime i import an mxm i am forced to reapply uvmap again. With the old plugin it retains the uvmp of the Lw material editor. The progammer should something about that.. i think imported mxm should retain uvmap of lw material editor for the chosen material ;
2) if i import an mxm with has bad map path ( as all the donloaded mxm of the site) i am not able to give the right path from within Lw as i am not able to open the mx matyerial editor.
this 2 point slow very much the workflow in my opinion
					
										
					  																i will explain why with just 2 examples :
1) everytime i import an mxm i am forced to reapply uvmap again. With the old plugin it retains the uvmp of the Lw material editor. The progammer should something about that.. i think imported mxm should retain uvmap of lw material editor for the chosen material ;
2) if i import an mxm with has bad map path ( as all the donloaded mxm of the site) i am not able to give the right path from within Lw as i am not able to open the mx matyerial editor.
this 2 point slow very much the workflow in my opinion
						 Last edited by giacob on Mon Jul 02, 2007 9:21 pm, edited 1 time in total.
						 						 
						
										  										 
					 
					 win xp 32- e6600 - lw plugin
vista 64 - i7 2,67 ghz - 8gb ram
					  					                vista 64 - i7 2,67 ghz - 8gb ram


