Beiträge von Anachron13

@Enzojz : I don't understand what you where trying to say about the uv and the game (On peut parler français si tu préfères).

The uv map is still wrong in the preview windows with the last version (exact same). Btw the output windows has a warning about the FBX file being in a newer unsupported version.

Added a screenshot when you can see that the uv seems to be applied without logic, with texture applied with a different scale to different pieces without logic. I have left the output in the screen if there is something that can help.

Edit again : I think you broke something when adding the texture preview, the texture where properly applied ig after converting the msh with the last version before you added texture (see my post n°35 and 37), but now it doesn't work at all, and the result is different from the preview (i only exported the body).

Hello @Enzojz,

The texture is indeed now properly flipped, but the uv coordinate are still wrong.

The last version is working for me. The textures are properly loaded, but the uvmap is messed up. The rotation in degree is also working.

Hi @Enzojz,

It seems indeed that default fbx exports from blender (all scale applied on the model and scale left to 1.00 in the export settings) come with a 100x scale as the result for some reason.

Good luck with the textures support

Ah yes i have read that, but the fact that the unit is different in the model transforms box than in the entry field misled me and i forgot, sorry

I finally got the logo to work. So while it's easier for blender users to use the blender plugin, thanks to you, we know have a solution for proper logo support that does not involve hex editor

@Enzojz : There seems to be an issue with manual rotation. As you can see from rotation behavior screenshots, i just added -90 in the X Roll Rotations transform, and for some reason i end with a weird angle (it become -5156.62 in the model transforms block).

The fbx file work fine now, but there is this small scale issue that i need to figure out (i only replaced the door .msh file)

The logo msh file with two uv doesn't seems to make the model viewer crash, but i can't see the logo right now (may be related to the scale issue ^^).

I will do some more tests.

Hello,

I tried to use your converter from a blender model without success so far. I exported into fbx format my model, but when i try to import it into the converter, it just crash :

Application : TpFMCWorkshop.exe
Version du Framework : v4.0.30319
Description : le processus a été arrêté en raison d'une exception non gérée.
Informations sur l'exception : System.IO.FileNotFoundException


Informations sur l'exception : Assimp.AssimpException
   à Assimp.Unmanaged.AssimpLibraryWindowsImplementation.NativeLoadLibrary(System.String)
   à Assimp.Unmanaged.AssimpLibraryImplementation.LoadAssimpLibrary(System.String)
   à Assimp.Unmanaged.AssimpLibrary.LoadLibrary()
   à Assimp.Unmanaged.AssimpLibrary.IsExtensionSupported(System.String)
   à TpfMC.Core+Input.read(System.String)
   à Microsoft.FSharp.Primitives.Basics.List.map[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.FSharp.Core.FSharpFunc`2<System.__Canon,System.__Canon>, Microsoft.FSharp.Collections.FSharpList`1<System.__Canon>)
   à TpfMC.MainWindowViewModel.LoadFiles(Microsoft.FSharp.Collections.FSharpList`1<System.String>)
   à <StartupCode$App>[email protected](System.Object)
   à TpfMC.RelayCommand.System-Windows-Input-ICommand-Execute(System.Object)
   à GalaSoft.MvvmLight.Command.EventToCommand.Invoke(System.Object)
   à System.Windows.Interactivity.TriggerBase.InvokeActions(System.Object)
   à System.Windows.Interactivity.EventTriggerBase.OnEvent(System.EventArgs)
   à System.Windows.Interactivity.EventTriggerBase.OnEventImpl(System.Object, System.EventArgs)
   à System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   à System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   à System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   à System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs)
   à System.Windows.Controls.Primitives.ButtonBase.OnClick()
   à System.Windows.Controls.Button.OnClick()
   à System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
   à System.Windows.UIElement.OnMouseLeftButtonUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   à System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   à System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   à System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   à System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   à System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
   à System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   à System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   à System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   à System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   à System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   à System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   à System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
   à System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean)
   à System.Windows.Input.InputManager.ProcessStagingArea()
   à System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
   à System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
   à System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
   à System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
   à System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   à MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   à MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   à System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   à MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   à MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   à System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   à System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   à System.Windows.Application.RunDispatcher(System.Object)
   à System.Windows.Application.RunInternal(System.Windows.Window)
   à System.Windows.Application.Run(System.Windows.Window)
   à MainApp.main(System.String[])

Nom de l’application défaillante TpFMCWorkshop.exe, version : 0.0.0.0, horodatage : 0x58c17106
Nom du module défaillant : KERNELBASE.dll, version : 10.0.14393.321, horodatage : 0x57f4c291
Code d’exception : 0xe0434352
Décalage d’erreur : 0x000da6f2
ID du processus défaillant : 0xaf4
Heure de début de l’application défaillante : 0x01d298ee8fe2bae0
Chemin d’accès de l’application défaillante : D:\perso\Transport Fever\TpFMCWorkshop.exe
Chemin d’accès du module défaillant: C:\WINDOWS\System32\KERNELBASE.dll
ID de rapport : da4c9dbc-0e93-4564-a199-9331913901d6
Nom complet du package défaillant : 
ID de l’application relative au package défaillant :

hi,

I will give it a try tomorrow and keep you posted with the results.

@Seamon : the name line of the soundset is commented (-- at the start of the line), it may be the reason?

Hi,

I would like to help as i'm also interested in proper logo support, but i'm not sure how to export to ASE format from blender. I will give it a look.

@dampf19 : what you are describing would make the use of any main lines train like the ICE useless from a gameplay perspective. While an ICE can do anything, there would be no point from a economic perspective to use it on short line where it can't go to it's full speed, and you will end up using only fast accelerating commuters trains. I mean why would i use a high speed train with a five time higher maintenance cost instead of a commuter when said high speed train can't even reach is max speed and will probably take as much time if not more than the rapid accelerating commuter to do the trip?

I think the issue here is that there is two type of players in this game, people like you and @fido who seems more interested in the "model railway" side of the game and don't care to use non optimal trains on a line as long as it look real, while other players (more like me) are more interested in the managing part of the game and optimizing lines but don't care about realistic acceleration. I'm not saying that one is more right than the other here.

The only way i see to have everyone happy would be to have some sort of option between "real" acceleration/braking values or "gameplay" values.

I don't think realistic values can work without taking into account the scale of the map. A TGV Atlantique take something like 12mn (i think around 40km iirc) to reach 300km/h, and *emergency* braking from 300 to 0 take 3.3km (~2mn). Even a regional train like the Z21500 take 10.5km / 4mn30 to reach is max speed (200km/h).
The problem with braking and acceleration is that while the stations are in 1:1 scale, the global scale of the map is not. Using realistic values without scale will basically make only commuters capable of high acceleration useable ig.

@Seamon : ok, je me demandais pourquoi tu avais mis 2022. Au grand désespoir des amoureux de ces machines, je pense que tu as été optimiste et que toutes les machines auront disparu cette année. Il ne reste aujourd'hui que 7 BB17000 en service (http://trainsso.pagesperso-orange.fr/BB17000.pdf), 23 BB25500 (http://trainsso.pagesperso-orange.fr/BB25500.pdf) et 3 pauvres BB8500 (http://trainsso.pagesperso-orange.fr/BB8500.pdf).

Hi @Seamon,

I read your script and you did quite an impressive work to analyze all this mods.
I noticed for the BB17000 that you wrote "-- Real: 1995 - 2007". It should be 1995-2017 (there is a few still in service - the author is actually driving them). Same for the BB25500 and BB8500.

If you want real value, the CC6500 from my mod has been retired since 2007. I left out the end of availability date because there is currently no other V200 capable high power engine of the SNCF for TpF (namely the BB26000).

You also made me notice that i forgot to copy past some seats raw in two model files of the Z21500, if the "real" number in your script is the number of seat passengers can use, it should be 68 for every mdl except the trailer (Z21500R.mdl). I will post an update on steam. Edit : update posted

Hello,

You can check the direction of the normal of a face by displaying the normals in edit mode (cf screenshot). The small blue lines represent in which direction is the normal of each faces.

If you have a normal in the wrong direction, just select the incorrect face(s), mesh > normals > flips normals.

Bonjour @Le cercle rouge,

Ton processeur est un AMD E1-6010 plutôt non? C'est un processeur entrée de gamme pour ultra portable qui doit vaguement arriver au niveau du minimum syndical requis pour blender, à savoir un cpu dual core 2Ghz (https://www.blender.org/download/requirements/). Je doute qu'ajouter de la mémoire puisse faire grand chose pour toi, surtout que j'imagine que vu que tu es sur un processeur ultraportable, tu n'as pas non plus de carte graphique dédiée?

Tu arrives à faire tourner TpF avec cette config ?

Concernant les droits, tu ne devrais pas avoir de soucis tant que tu ne comptes pas vendre ton mod pour ce qui concerne l'objet modélisé. Si par contre tu utilises des photos (pour les textures), sons, etc qui ne sont pas à toi, il faut voir avec les licences ou les auteurs des éléments en question.

Bonne après midi à toi.

Bonsoir @Le cercle rouge,

Bienvenue parmi nous!

En plus des infos que t'as donné @Romuseeuw, je t'invite à lire le guide (principalement écrit par @Vakan) dispo à cette adresse. N'hésite pas à poser tes question sur le sujet de Romu et aussi à nous faire part de tes projets, pour qu'on évite les doublons, déjà qu'on est relativement peu de moddeurs français

a+

Hi,

@SwissCH : you wanted to see France, here we are!

Thanks for the information, it will be easier for me now.
This is not trivial information to get, i didn't now about vertical transformation for exemple when i first tried this plugin, which led me to the erroneous conclusion it was not working properly with TpF after i spend a few hours of tries (i still have a bunch of screens of the funny results i got when the game was not crashing :)). It should probably be added somewhere is the lexicon DDS page.

Anyway, thanks for the answer and sorry for going a bit of topic