Ummm, are you sure!? I never used a single .3ds file when I created those scenes and didn't "glue" anything together
The "vertex groups" (I assume you mean smoothing groups) are as they are in LFS itself.
By the sounds of it, you want to start modelling the cars from scratch, if not, you'll end up with exactly the same as I did. Remember, we're dealing with low-poly models designed for a game, not 400,000 poly meshes split up into every little segment of car.
There's also multiple rendering tutorials already available for 3DS, including Grudd's original and Davo's video companion that.
Would have thought that'd be obvious by now... some people drive fast, some don't, some people like blue, some don't... some people have a life and friends..............................
You could have (and should have) stopped at 'women + 4x4'.. but I guess now it's patently obvious why these dumb bitches buy motors like that and are a real annoyance and danger to anyone else on the road for 99% of the time.
Nothing against women drivers in particular, but it seems the ones driving Chelsea Tractors(tm) are the worst breed of idiot.. almost make 17 year old boy r[a|i]cers look mature and sensible
Thanks for the report heson.. I haven't had much time to do any "fun stuff" for a while.. work is solid and then some.
I think the reason that it clears after you manage to close the error msg eventually is that the error is probably triggering while reading the replay list, so you'll get 1 msg per replay file.. that's my logical guess to that part anyway
My guess is that removing the SPR / MPR grid ini files would be enough to fix it if removing INI files appears to do so. Could you possibly test this for me please by just deleting those and see if it works again? If so, could you then make it crash and send me a copy of your MPR / SPR / MPR results INI files to [email protected] ? Maybe I'll be able to spot something in them. I Need to update the debug log as it's not very useful atm.
I'll try and get something fixed up at the weekend
Interior 1 at least needs to be loaded into the material slots more than once.. you should see both of them in the material list. IIRC, one of the slots handles the actual car interior, the other handles the lights / grilles etc, but both are on the same text.
As for the dash not showing up, that's normal. In LFS, that display is generated by code, not textures.. hence there's nothing there. Best you can really do for that if you don't want to texture it (not the easiest of tasks) is to assign a plain black material to those polys.
And neither create anything you can display publicly without huge embarrassment
Word is a word processor, not an HTML editor, although it can hack HTML files.
RuntPage will bloat everything and more than likely won't produce a site that'll render properly in web browsers, only IE
Dreamweaver is a better choice for beginners IMO as you can use the designer to begin with and then use the built-in code explorer to see what code was generated by you adding bits to the designer. I used DW3 IIRC way back in the day to learn the basics of HTML this way (ie: what tags did what).
Once you have that sorted, then there's nothing better than a plain ol' text editor.. my personal favourite is UEdit or NuSphere PHPEd for something more specialised for more advanced projects
It's because they're k00l and 1337! These are the kids who think "owning" (sorry, in 1337 speak: 'pwning' :rolleyes: ) has nothing to do with possession
Or more accurately, were born lacking 99% of their brain cells and now think they can be something by posting crap like this..... they're something, alright
Reminds me of days waaaaaaay back when I used to use AIM as an IM client and all the stupid kids threatening to 'ha><0r j00 fo01!'. Sad, so very very sad.
Please explain to me how this can be _anything close_ to being a 'virus' (which you so stupidly highlighted in bold too)? A virus simply has to do 1 single thing to be a virus... and that's self-replicate which I highly doubt this does.
Unfortunately, as nice as it is being able to export into the various formats, they're all handled by a 3rd party component (part of the grid). I do plan to get around to hacking these components into much better results (the HTML output is appalling.. how the company who wrote the grid can't be embarrassed by it is beyond me, looks like they used m$ runtpage as an HTML guide ). I'll look into this and either try and fix the export functions or rewrite the lot from scratch myself.. either way, I can confirm the bug and will look into this soon
Your issue is you seem to fail to have any control over your own grey matter whatsoever, like the typical FnF-mad-tyte-y0! wanabee "drifter".
You've posted shitloads of useless questions over the past few days all because you can't be arsed to search for yourself. I made rendering a skin possible within 5 mins if you want to be super lazy or just want to get to grips with the easy stuff first, but alas.. you want to be Einstein without studying and expect everyone else to give you the answers :rolleyes:.. well here's one, '2 words, 3 Fs'
I seriously have no problem, helping people if I can with 3D stuff, hell, I've spent enough hours doing so so far.. but I won't help people who aren't prepared to help themselves.
No one here became an expert at rendering overnight.. why don't you take time to actually learn what you're doing rather than asking everyone to wipe your arse for you?
I guess your nickname pretty much says it all as to why and people wonder why I stereotype
Thanks for the comments lads.. nice to see it may get some use for various tasks
fel: I haven't added the info yet for the multiple LFS versions to the help file, but incase you or anyone wonders in the mean time, 'LFS.exe' found in the 'Root Path' dir will be assumed for all replays that don't have a specific exe listed.. this seemed to be the most logical method for the best flexibility.
The version in the Prefs window _must_ match the version reported in the replay lists, it's also case-sensitive.. but I'll change the case-sensitivity requirement for the next build simply for convenience.
fly: yes and no
If you expand an MPR replay to view the results, make sure that replay is still selected (and the only one selected) and you can go through the main Export function and tick the 'only selected records' checkbox. This'll export the line from the main MPR grid that's selected and the results of that replay... that's the 'yes' answer (see attachment for an example)
The 'no' answer is that you can't (yet? I'll have a look though) just export the results. That said, the extra info displayed in the main MPR listing might be useful anyway, such as the date, whether there was wind enabled etc.
There's still a few more features planned, such as lap / split comparisons. The code's started for that but not got too far yet. I've also asked Scawen if he can change the SPR header to report the LFS username for both HLVC and non-HLVC replays. This'll allow me to enable the 'calculate only my replays' option in the Prefs to display results in the trends charts just for you, rather than combined for all drivers in all replays.. hoping this'll be added to patch X5 whenever that may come
Open to further suggestions too. If it's reasonable, replay related and I can code it I'll consider any suggestions
The demo version of Brazil limits output size. Do a search on the net for 'BIGrender'. If you have issues using it, do a search for the same on http://dsrc.digiserv.net/forum/ as speedykev posted a basic guide on how to use it there a long time ago
This'll be exactly where it shows in the tutorial screenshot You'll need to scroll the list of options down until you see the Output rollout.. click n the word 'Output' to expand the section and make the adjustments.
As for your other query about the headlights, sounds like you've only assigned one of the interior materials.. for most cars, you'll find that *Interior1 is listed twice.. you need to load the texture into both slots.. one of the material slots will take care of the actual interior, the other will take care of the lights and any accessories (such as radiator grilles etc).
I've just performed a test as mentioned in my last post and confirm that HLVC valid laps would appear to have the correct LFS username stored in the SPR header as the 'username' data... for non-HLVC replays however, this seems to assume the in-game player name, which is already stored as 'playername' elsewhere in the header.
Could this possibly be "fixed" to report the username for both HLVC and non-HLVC replays?