ATTENTION: Skipping vehicle because the filename

Discussion in 'Modding' started by Pales, Jun 10, 2024.

  1. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    I'm currently familiarizing myself with modding again and I've hit a bit of a snag that I hope someone here can help me with. I've been working on adding a new car to Dev Mode, but for some reason, it’s not showing up properly in the Spinner Studio or in the game itself. Instead of the car model, all I see is a yellow box.

    After viewing the contents of the trace file, this is the only thing that I see which appears to be preventing the model from loading:

    0.87s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_05.veh matches an existing vehicle
    0.87s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_05b.veh matches an existing vehicle
    0.87s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_07.veh matches an existing vehicle
    0.87s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_07b.veh matches an existing vehicle

    However, this line is being generated for the entirety of my car collection within Dev Mode which makes no sense at all, because they're all unique folder names and cars. I am trying to understand where this conflict is coming from, because it is even impacting the skip barber - which is default dev content (as seen above).

    I have previously not had any issues with car models loading into Dev Mode but for whatever reason, I am really struggling with this one. How do I identify what 'matches an existing vehicle' means?
     
  2. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    After digging deeper into the logs, it looks like this may actually be the underlying cause and not the issue first listed. The reason why I have come to that conclusion is that after I removed my mod and re-run the trace, the same errors were appearing. So I appear to have been fixated on the wrong error!

    Here is the updated error:

    21.93s vehgfx.cpp 6874: VehGraphics::RenameLiveryMaterials
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wccarbody_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wccarbody_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wccarbody not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcspinner_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcspinner_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcspinner not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcwindow_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcwindow_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcwindow not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcwindshieldin_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcwindshieldin_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcwindshieldin not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcwindshieldout_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcwindshieldout_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcwindshieldout not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcwindowsin_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcwindowsin_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcwindowsin not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcwindowsout_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcwindowsout_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcwindowsout not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcrims_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcrims_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcrims not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcswheel_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcswheel_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcswheel not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcdriver_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcdriver_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcdriver not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcarms_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcarms_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcarms not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcwing_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcwing_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcwing not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wchelmet_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wchelmet_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wchelmet not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcpitbody_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcpitbody_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcpitbody not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcpithelmet_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcpithelmet_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcpithelmet not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wclollipop_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wclollipop_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wclollipop not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcrefueler_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcrefueler_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcrefueler not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra0_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra0_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra0 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra1_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra1_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra1 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra2_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra2_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra2 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra3_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra3_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra3 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra4_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra4_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra4 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra5_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra5_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra5 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra6_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra6_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra6 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra7_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra7_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra7 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra8_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra8_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra8 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcextra9_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcextra9_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcextra9 not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName pitbox_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName pitbox_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName pitbox not found
    21.93s vehgfx.cpp 6884: VehGraphics::RenameLiveryMaterials replacementName wcsponsor_000
    21.93s vehgfx.cpp 6895: VehGraphics::RenameLiveryMaterials replacementName wcsponsor_000 not found
    21.93s vehgfx.cpp 6906: VehGraphics::RenameLiveryMaterials matName wcsponsor not found
     
  3. Chris Lesperance

    Chris Lesperance Registered

    Joined:
    Nov 29, 2012
    Messages:
    1,311
    Likes Received:
    2,091
    This part, it appears that in your Mod Dev, you have two .veh with the same name. .VEH names will need to be unique. What will happen is that it might not show up in the list. If you change the name to be unique, both cars will show.

    I was just recently doing some work on both the CART 1985 and CART 1990 mods. I had two cars named Foyt_Indy_14.veh, so they were no showing in the list. Changing one to Foyt90_Indy_14.veh, everything showed up.

    Second part: That is normal. That car may have some WC materials. The log is just saying that there were no specific WC textures for those cars and it will load the default textures.

    Hope that helps :)
     
    DanRZ likes this.
  4. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    Hi Chris,

    Thank you for your message, it is very much appreciated. Regarding the .veh files, I have checked every individual mod and they're all named differently, and this is what is confusing me. For example:

    0.81s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_05.veh matches an existing vehicle
    0.81s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_05b.veh matches an existing vehicle
    0.81s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_07.veh matches an existing vehicle
    0.81s setup.cpp 2709: ATTENTION: Skipping vehicle because the filename skipbarber_07b.veh matches an existing vehicle

    If I go into \rFactor 2\ModDev\Vehicles\SkipBarber\teams, I only see these 3 .veh files listed above, I do not have any duplicates and in my eyes, they are all considered to be unique.

    Also, thanks for reaching out to me regarding my secondary post. If that is not the underlying cause of the car not showing, then I am really at a loss on why it is not displaying in the spinner studio or in-game. Would you perhaps have a moment to check my log file and see if you can decipher the possible cause? I have been trying to diagnose this for 4 hours and feel like I am overlooking something very simple.

    For referencing - the car that is not displaying the model in-game is the URD_PX_Darche

    https://filebin.net/wcm27nt0n6rw5ppg/trace_2024_06_10_21_21_12-15.txt
     
    Last edited: Jun 10, 2024
  5. Chris Lesperance

    Chris Lesperance Registered

    Joined:
    Nov 29, 2012
    Messages:
    1,311
    Likes Received:
    2,091
    Is your mod .veh named skipbarber_05.veh, skipbarber_05b.veh, skipbarber_07.veh or skipbarber_07b.veh? I would search from \rFactor 2\ModDev\Vehicles to see if there are duplicates

    If you are getting the URD_PX_Darche in Mod Dev, there could be a few things.

    1. Make sure the folder path matches what is listed in the .gen of the car.
    2. Mod Dev does not like loose "Main" files in a .mas. Extract the .gen, .sfx, .hdv, .ini etc and have them loose in the main car folder.
     
  6. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    12,483
    Likes Received:
    6,656
    @Pales I can't see your trace because it's on filebin. You can attach it to your post here directly, no need to upload it somewhere else.

    As you said, the .veh message happens to the skip barber too, so I wouldn't worry about those messages. Even if they were an issue, it seems that would stop you being able to even select the car, when your issue is the car being a yellow box (probably a .gen issue, I guess). Your trace might indicate what file(s) it's having trouble opening/referencing.
     
  7. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    Hi Lazza,

    Apologies, I was not aware. Please see attached. Any guidance would be much appreciated.
     

    Attached Files:

  8. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    Sadly, I see no duplicates at all. And this is just for skipbarber as well, I also have this happening for the URD_PX_Darche and the pace car. The skip barber I haven't made any modifications whatsoever to, and the same also applies to the pace car. It is really odd. I have gone through each of the folders separately and looked at all of the structures and they're all unique.

    Regarding the loose main files, I have referenced the original .MAS file and went through each file individually, and it is all within the main folder and all the other files in the corresponding sub folders as well. I feel like walking into a wall at this stage trying to figure out where it is going wrong! :p
     
  9. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    Examples

    I have included 3 screenshots to showcase.

    - Example (an example of my folder structure and subfolders)
    - GenFileExample (an example of the gen file that is associated with the URD_Darche)
    - URDDarchTeams (example of the 3 .veh files all with unique names and no duplicates)
     

    Attached Files:

  10. redapg

    redapg Registered

    Joined:
    Jan 16, 2012
    Messages:
    4,207
    Likes Received:
    3,044
    At first: ignore the ATTENTION: Skipping vehicle becau...... Lines

    And that a yellow Temp Car appears in the Garage or no Car in the Spinner, is caused by not found Files (gmt, Textures).
    Check, if all Search Pathes to the Folders of the extracted *.mas Files are correct.
    And if the Car uses Material JSON Files, extract them into a Folder too and Link the Folder as
    MaterialPath=...., like you do it with SearchPath=.
    And you can remove the Entry SearchPath=URD_PX_Darche and as the Link to the URD_DarchePX1_shaders.mas, you can use
    the Entry
    MASFile=URD_DarchePX1_shaders.mas.
    It will be found, because you already have the SearchPath=<VEHDIR>URD_PX_Darche, in that the mas File is (should be) located .
    If you can not get it showing up in Game, feel free to contact me in the usual Way. :)
     
  11. redapg

    redapg Registered

    Joined:
    Jan 16, 2012
    Messages:
    4,207
    Likes Received:
    3,044
    Me again.
    Yesterday i couldn't open your Screenshots, but now i can and have seen that the Pathes in the shown Gen File doesn't match your Folder Structure.
    I can not see the Name of the main Folder, but you have to use the proper Folder Names and Structure in the Gen File.
    Example:
    In the Gen File you use the Search Path:
    SearchPath=<VEHDIR>URD_PX_Darche\mas
    But that Folder doesn't exist
    With your Folder Structure and if the Folder URD_PX_Darche is the main Folder in the Vehicles Folder, you have to use Pathes like
    SearchPath=<VEHDIR>
    SearchPath=<VEHDIR>URD_PX_Darche
    SearchPath=<VEHDIR>URD_PX_Darche\URD_DarchePX1
    SearchPath=<VEHDIR>URD_PX_Darche\URD_DarchePX1_lights
    SearchPath=<VEHDIR>URD_PX_Darche\URD_DarchePX1_shaders
    ....
    .....
     
  12. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    Hi Chris,

    Thank you for your message. I cannot believe I overlooked something so simple, I am so frustrated with myself! The naming schemes looked so similar. Clearly I need to get some glasses as well! :p

    I'm also really surprised that this car works in the base game, because I have not made any amendments to the naming scheme, it is all entirely default, so I would expect it to crash because of the gen references but in the real game, it works just fine. Do you know why that is? Anyway, I am happy to say that after those amendments, it is now appearing in dev mode.
     
  13. redapg

    redapg Registered

    Joined:
    Jan 16, 2012
    Messages:
    4,207
    Likes Received:
    3,044
    Hello Pales,
    the Answer is: in the main Game, simply the whole Content of all *.mas Files of a Component gets used, so that you don't need to have Search Paths at all. :)
     
  14. Pales

    Pales Registered

    Joined:
    May 9, 2017
    Messages:
    437
    Likes Received:
    431
    Thanks for your help! :)
     
    redapg likes this.

Share This Page