Smarty error when generating a new project [solved]

#1

*** FMOD PATH NOT VALID

Is your FMOD path valid?

If you don't have FMOD correctly installed and you generate a project that includes FMOD you will get this error, and it might cause failures in the script that lead to the final death error.

#2 I tought that was an entirely unrelated error as I didn't selected to include FMOD as a module in the Project Manager. However, I installed the old FMOD API and created a new project to test things out. I'm still getting an error:

Welcome to projectGenerator 0.9
Copyright (c) 2012 GarageGames, LLC
Released under a MIT license.


   CWD = Z:EnginesTorqueTorque3D-3.5.1ToolsprojectGenerator
   - Loading Smarty...

   - Loading config file Z:EnginesTorqueTorque3D-3.5.1My ProjectsNewTestbuildFilesconfigproject.conf
   - Setting platform to: win32
   - begin project: lmng={73D9048F-55AA-4EF6-BF33-3A811DC47FCE}
      - end project lmng
   - begin project: lpng={63D63B58-3DB8-4844-9648-C5AA04B4C1BC}
      - end project lpng
   - begin project: lungif={5C9BE928-8510-451E-B866-5C2ECF3E592F}
      - end project lungif

   - begin project: zlib={3FFDBB50-6E27-4E66-B1EC-750663C9D784}
      - end project zlib
   - begin project: ljpeg={E2A746EC-8AD3-4D45-AFBB-5A81F705E9BE}
      - end project ljpeg
   - begin project: tinyxml={470600AC-F51E-4F4E-9406-3B517BF112AC}
      - end project tinyxml
   - begin project: opcode={C0B7BA09-E125-412E-86B0-2D89DB971CAB}
      - end project opcode
   - begin project: squish={3FFDBB50-6E27-4E66-B1EC-750663C9D799}
      - end project squish
   - begin project: collada_dom={25D580F1-2A2C-48EB-89C6-B54CAF4BDC4E}
      - end project collada_dom

   - begin project: pcre={910A3F94-E18D-4CB9-87DC-382C75F6B941}
      - end project pcre
   - begin project: convexDecomp={4EF87A4E-16ED-4E64-BF04-841B2675AEE0}
      - end project convexDecomp
   - begin project: libvorbis={F8240290-BA36-4696-967F-C2611CEE501A}
      - end project libvorbis
   - begin project: libogg={719523DB-7C6B-416B-B68D-B2579477239B}
      - end project libogg
   - begin project: libtheora={B0B6B74B-2045-43B0-85BF-A24BF2D25155}
      - end project libtheora
   - begin project: NewTest DLL={C0FCDFF9-E125-412E-87BC-2D89DB971CAB}


   - Loading project code configuration from Z:EnginesTorqueTorque3D-3.5.1My ProjectsNewTest/buildFiles/config/projectCode.conf

      - end project NewTest DLL
   - begin project: NewTest={CDECDFF9-E125-523F-87BC-2D89DB971CAB}
      - end project NewTest
   - Processing project 'lmng'...

      o Writing project file projects/lmng.vcproj


Fatal error: Smarty error: [in vc2k8_lib_proj.tpl line 268]: syntax error: unrecognized tag 'assign' (Smarty_Compiler.class.php, line 591) in Z:EnginesTorqueTorque3D-3.5.1ToolsprojectGeneratorsmartySmarty.class.php on line 1095

#3 Yeah I always get the FMOD path error for some reason. But I've never seen that Smarty error before. Are you using Git? If so, do you have the same error in the development branch? I think we merged some changes to do with the project generator.

#4 The error above is from the Zip-archive containing the pre-compiled version of 3.5.1 including the Project Manager. But I'm also getting the same error on a fresh git clone of the development branch.

#5 Never see this problem.

CWD = Z:EnginesTorqueTorque3D-3.5.1ToolsprojectGenerator

This it's weird path, it's correct on your console log?

OS?

#6 There are slashes in there, the forum software just filter them out. Here's a pastebin of the output: pastebin.com/GeXcrqkr

(Updated the link as I managed to truncate the text.)

I'm running Windows 7 Professional, although in a VirtualBox instance.

#7 Huh. That is odd. I'll see if I can reproduce it this evening. To be honest, I never use the zipped archive - I just check it out from GitHub.

#8 Hmm. Right out of the box, created a new project using the project manager, changed to the project's directory, ran generateProjects.bat and it ran fine. Looks like you found a weird one!

#9 Hmm indeed. I downloaded the zip and unpacked it locally instead of using the version on the mapped shared drive (Z:) and it worked!

But still, that is just plain weird behavior.

#10 Mapped drives - on Windows the path can be weird with mapped drives. I was writing a program to copy files to mapped drives and if the mapping isn't to the the top level of the share Windows does't want to deal with it and "can't find some or all of the path". Perhaps the interpreter isn't set up to handle that - it's a little convoluted and you have to manually load a specific Windows library to get it working.