Idk if it's a bug but if you export to share a vehicle, when the other ppl open the mod on editor, it loses the names of subobjets

thanks

Update: I did not like the tire overheating during racing and tried to do more research about tire sizes used on rally cars. Unfortunately, I did not find if there were some more suitable tire sizes than the stock ones. However, looking through the tire sizes showed that I made a mistake in the stock sizes.

To fix this, I have used the size of the 180 HR 15 Michelin XAS tires and fitted them to all wheels. These were used on 1965-1973 models and are the only original DS/ID tire sizes, which can be defined in the LFS editor (the original DS/ID saloons had smaller tires in the back but today it is recommended to use the same size for all wheels, which is also more suitable for racing).

The mod is a little more stable now and is visually better proportioned, when compared to photos of real cars. The tire overheating is slightly better, but still there.

alright, finaly got the model finished and ready to work on in lfs editor.

probebly will comeback to work on facelift version of this car and also m tech version at some point.

Thanks for the report.

Are they actual mirrored triangles? I've deliberately made it so that mirrored triangles don't report the same error twice.

Other than that, I can't say much without looking at a copy of the model in my editor. If you'd like, you can cut away most of your model, leaving just enough to show the apparent error and attach it here so I can look at it.

Not much done, really. except a lot was done, mostly being mapping corrections and making sure its triangulated properly in the editor, while I was at it I fixed the scale to match the real counterpart as best as possible, not a 1:1 scale but on a very acceptable level...

A couple of pics from today's work, yes while scaling it down I ran into a couple of issues, so the shape got a bit wobbly. ofc that's gonna be addressed in the next update

That's fixed in D21. Thanks for the report.

FIX: Editor ray check did not work on selected subobject if show subobs NO
Info about triangle / point errors is not repeated for mirrored subobjects

Reporting this again as it might be a bug?

For some reason I still can't update the editor. Black screen using the given LFS Editor.exe.

Old 7c editor exe works fine even with the updated 7d20 data and bin files but the start screen still says 7c and I don't have the new features described.

Also just tried with a fresh LFS Editor install and had the same outcome.

No anti-virus blocking the app, won't change the outcome when ran as administrator. Win10 here.

Cheers!

Quote from ivancsx :

For me, it's same crucial just like how we hide-unhide tris and points, so when we working on specific subobject, we can hide the other subobject that overlapping our view to recent subobject that we working on

Quote from Flame CZE :

Something like a "single subobject mode" which would only show triangles and points of the currently selected subobject would be nice.

Quote from Snoop.DriftEra :

Yeah. Would be great. I dream of a list with sububject names (as we have in maps or cutouts, for example) and have a button to the side of it that hides/unhides.

The single subobject mode is now available in Editor test Patch D20.

It works quite simply: if "show subobs" is set to NO it will still display the selected subobject. You can select a different subobject either by clicking in the new list of named subobjects or by switching "show subobs" to YES again, select the other object then "show subobs" NO.

https://www.lfs.net/forum/thread/102626

Minor updates in D20:

ESC or SHIFT+X from Modeller do not give warning of changes if entered from Vehicle Editor
You can hide subobjects other than the selected one: show subobs NO (with subobject selected)

Quote from Scawen :

I wonder if ESC should be instant exit without question

Few times by mistake I have lost all of the changes I made because I thought I'm in Edit Mode (Modeler) where the changes are saved automatically and usually I just ignore the message, but this time I was in vehicle editor and got confused since the message is the same.

If changes are saved automatically no need of warning. If I want to export my model as .sre, I would without reminders.
Would be nice if there is a warning message when exiting the LFS Editor window by the X.

I'm not sure how or why I made this change but maybe I was trying to make something consistent with something else. Maybe it was related to the reinstatement of SHIFT+X to exit, which I did every single time without fail, and only hid all the triangles which was so annoying (because X was the Hide key).

Now that H is the Hide key, and SHIFT+X works again, I did think there could be a danger of people pressing SHIFT+X, intending to hide points or triangles, but exit the modeller instead, so losing their modeller state including undo buffer and current selection.

I wonder if ESC should be instant exit without question (if modeller started from vehicle editor) but SHIFT+X should continue to ask for confirmation. It seems a bit odd but maybe it makes sense.

Quote from Drifteris :

So i was using an older version of editor something like 7C before, wasn't doing anything recently so was no need to update, but now downloaded D19

I don't know how people make their mods, i open vehicle editor, select my mod and it loads. Click E to go into modeler and do mapping, coloring, building, etc. Back in 7C, after doing some mapping i would press ESC and it would instantly go back to vehicle editor so i could check the lights, subobjects placement, etc.

Now it asks me if you want to quit the editor because there are some unsaved changes. As far as i know it automatically saves the changes done in modeler when you quit into vehicle editor, even in this D19. So why this extra Yes/No window? Now it only confuses me and i might quit the actual vehicle editor.

I get this pop-up too and it is a bit inconvenient. What I usually do is switch to Modeller, do some editing, then switch back to Vehicle Editor and vice versa. Having the dialog pop up every time can get a bit annoying, as I don't need to save the standalone model at all.

Maybe the unsaved changes dialog should not be shown if you enter the Modeller from Vehicle Editor?

more progress : made front and rear lights, front grill, interior base, side mirror... will do config in lfs editor for front headlights.

Thanks for the feedback

The bumper and front grill can now be skinnable separately (I don't recommend writing any words on these parts, I recommend only using them to paint

The front part of the rear compartment is now merged together with the side part

The licence plates are a weird thing, because in the lfs editor it's ok, when I go to the game it gets weird XD

So i was using an older version of editor something like 7C before, wasn't doing anything recently so was no need to update, but now downloaded D19

I don't know how people make their mods, i open vehicle editor, select my mod and it loads. Click E to go into modeler and do mapping, coloring, building, etc. Back in 7C, after doing some mapping i would press ESC and it would instantly go back to vehicle editor so i could check the lights, subobjects placement, etc.

Now it asks me if you want to quit the editor because there are some unsaved changes. As far as i know it automatically saves the changes done in modeler when you quit into vehicle editor, even in this D19. So why this extra Yes/No window? Now it only confuses me and i might quit the actual vehicle editor.

Quote from Flame CZE :

By the way, what exactly don’t you like about the latest version of the editor?

Yes, that would be good to know.

The editor test patch (D19) has a lot of good updates: https://www.lfs.net/forum/thread/102626

if you are looking for news on these new tracks, go on 20th anniversary announcement. However referring back to map editing, maybe with the track editor in a couple of years there might be the possibility to create real life tracks, but without license like skin making. Real life licensed tracks are unlikely to be announced by the devs judging by how long it took to get one licensed track and how there aren't any further notices on the subject, that said it would be great to have them.

Editor test patch D11 should fix that:

Quote :

FIX: Editor crashed on creating a new car

By the way, what exactly don’t you like about the latest version of the editor?

Hello, I encountered a problem today with lfs editor that when i click to create new vehicle or something, it crashes and says in red ERROR: IPoints==NULL in ApplyDamageNodesGraphical. Also i noticed when opening vehicle in editor it says too, but not crashes. What can cause this and how to fix this, tried reinstalling lfs editor, tried restarting pc. Im using lfs editor 0.7d9 cause i didnt liked new version how it looks.

Here is screenshot: https://ibb.co/z5wF01Z

Last edited by EmkaLT, Mon 10 Apr 2023, 21:53.

Unfortunate this is not going to happen very soon.

This is the soonest possible in my eyes. Speculation.

At the moment is being worked on physics and graphics overhaul.

When this is finished (lets say mid 2024), then maybe there will be announced a track editor (perhaps to be included in the LFS Editor).
This could take ~ 1 year (judging by the release of the Modeller and Vehicle editor - LFS Editor).

And then the modding community could make such tracks in maybe a few months.

So, 2-3 years from now hopefully there will be some light on the matter by the devs.

EDIT: there will be some new tracks coming with the graphics update.

Last edited by Evolution_R, Mon 10 Apr 2023, 21:03.

Found two little issues when trying to use the built-in engine sound editor (in LFS) for mods:

1. When saving a modified sound, LFS does not prepend the car's prefix like it does for normal cars. Like "RAC_". When changing a sound for a mod, I would expect the skin-id or something as prefix.

2. LFS doesn't load the last used engine sound for mods. It always starts with the sound shipped with the mod. I tried saving a modified sound prefixed with the skinid & name, but LFS ignores it.

Quote from Scawen :

64 materials

Yeah, that gave me a hint. And model had something like 5 different glass texture pages and few other small ones with different material settings (fancy vshine, overlay, etc) so those really blew material count up.

That's a capture from 7D14. Switching to the problematic config would indeed make the editor crashes.

Right, I haven't actually tried the newer test patch as I managed to merge some textures and make progress (and it's very close to finish, kind of, maybe). So, no really need to panic now.

Much thanks


And sorry for not posting quite a while (yeah, seems like my head keeps crashing as hard as the editor did).

So when I'm in the wheel object selection in the editor, it allows me to edit the front wheel but not the rear wheel.


It only says "Front" in this menu and doesn't allow me to change it so is this the only option, or is there a

way that I can edit the rear wheel as well?

Last edited by ReframedX, Fri 7 Apr 2023, 01:18.

I've received another South City update from Eric so did a few track editor updates that were relevant at this point. In the process I updated a few features from the public editor, so here they are.


Editor Test Patch D19:

Hotkey for "hide/unhide (un)selected" changed from X to H (like blender)
- small H button at top left to hide/show message history (old H function)

Left click increments should now always be smaller than right click
- previously this was not consistent for all types of buttons
- as before, CTRL may do smaller steps, SHIFT may do larger steps
- this change should apply to distance, colour, angle and scale

Find button for error triangles or points now selects all as expected
- previously only selected the first point or triangle in the list

I'm working on it. Progress is not stalled.

I did spend a lot of time last month on test patch and editor updates, but that's not my focus now. I won't go into all the reasons why that happened, but there was an important update, then I saw the E-Challenge, saw something that could be improved there, thought of a few other useful improvements, one thing lead to another...

Not a problem, that's all good. The updates were significant and important.

The idea of the progress reports wasn't really "this is what I will do forever". It was an insight into the development process, and I went into extreme detail, maybe even too personal, so people could really understand what being a programmer is about.

Tyre physics doesn't go the way multithreading goes. For me, it's not really suitable for rapid progress reports. There's a lot of experimentation and testing, research and hard thinking.

However much you want the new version released, multiply that by 100 (rough estimate) and that's how much I want it released. The new version is what I work on and think about for many hours every day. All I can really say at this point is don't worry, I'm on it.