Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem


I will test it asap :-)
Just hope not too hard to learn :D
Will be editor added to mac os x and linux editions when they will finally be launched?
Seriously? Guys, you should be ashamed of putting something like this into known issues :D Default key binding for in-game screenshot is key F4 and this freeze is caused by taking and saving a screenshot :D
Windows (since Vista at least) heavily frowns upon placing user files inside program directory. That directory is normally write protected, though I think Steam may actually mess with that (or just uses Windows' compatibility stuff). However, since people can install Trine wherever they want, and we don't want overly long path names, different location is easiest. The reason for 50 character limit is that editor limits max file + path name length to 200 chars. Windows has a limit of about 250 (you can code around it, but then e.g. explorer fails to access the overly long paths).
No.
-JLarja
---------------------------
Unhandled exception
---------------------------
Exception code: 0xc0000005
Address: 0x000007F80DAF7B8C in KERNELBASE.dll:000007F80DAF7000
Related modules: ntdll.dll KERNELBASE.dll clr.dll
Minidump:
C:\Program Files (x86)\Steam\SteamApps\common\trine\_enchanted_edition_\log\editor.exe_48c0f6cd.dmp
Stack trace:
+RtlRaiseException (line 0)
+RaiseException (line 0)
+DllGetClassObjectInternal (line 0)
+DllGetClassObjectInternal (line 0)
+DllGetClassObjectInternal (line 0)
Press CTRL+C to copy this message
Thanks for the report, we'll look into this.
EDIT: Fixed locally now, fix will be in next editor update (release date&time still not decided for next build).
aka Editor BETA update (Steam Windows only)
Editor
* Fixed crash when trying to add new resources. NOTE: New resource adding still isn't supported
* Fixed crash issue when using Category window
* Fixed audio event name autocomplete (audio event lists were missing)
* Fixed LUA crash error which occured when using editor
* Added missing resources (lots of types had only X "missing" model)
GUI
* Fixed missing King Skeleton GUI icon
NOTE: This patch might break existing MODs
Is new resources import support planned? Editor probably will not be very popular without this feature...
Same question here(about the resources)...
We'll probably have to see after proper editor release. If there's huge interest, then we are, of course, more likely to divert some developers to editor development.
-JLarja
Hi,
Help->about is a separate version numbering from the game itself which we haven't really used. It now shows 1.0 for Trine 2 since it's older editor/engine and 2.0 for Trine Enchanted Edition.
Our changelog informs the actual game version and build number. You can find this from game's main menu or opening main menu level in editor and playing it in editor.
If you have automatic game updates on, you should have the update downloaded already.
Like JLarja said, we are going to release the editor soon and see how much it will generate intrest.
Trine 2 editor uses e.g. our own formats for model and animation data so we would have to also release exporters and those are only available for LightWave since we use to use it internally.
Trine Enchanted Edition editor and future games uses FBX format which is more generic but we have some customization for that too.
In short: let's see how the release goes and how well the editor is received! :)
Thank you for your feedback!
I'm sorry to hear that. We will investigate this, thanks for the report.
Since you are running on Windows XP, I suspect the problem is with the XP support in our game.