Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[krcm1981]

The new version has fixed the issue I was having with the OpenGL/star field error. Thank you so much, was dying without my outerra fix.

[PRiME]

I couldn't help but notice that Outerra is caching all that is in the Packages directory, could there be a commandline function for disabling caching of packages assets, so that someone can edit the mtl/script or even model/texture files and simply replace the model in-engine without having to restart Outerra.

This would help ALLOT for us modelers/scripters who are constantly learning things by feel. Having to reload Outerra after the slightest adjustment of package files is quite annoying. Setting this directory as 'ALWAYS refresh/reload data' would make things ALLOT easier!

[bomber]

I've wondered sometimes after my 100th reload in under 3 hours if anyone at the 'other end' notices...

Edit.... What am I saying. I do all my testing on flightgear as its easier to access the jsbsim property tree.

[Levi]

I completely agree with you PRiME! Though, you can reload the .js script with ALT+R if you edit the file externally, I always do it this way.

I've recently discovered that the FDM on aircraft can be reloaded as well without restarting the engine, by simply respawning the aircraft. Still not very practical, but I guess it's better than restarting Outerra.

Atm, the materials are the biggest pain for me, lots of restarts 'till I'm happy with the results...

[PRiME]

ALT+R will be handy, however disabling the caching of the packages directory and forcing engine to load the assets for each new vehicle instance will pretty much make all other workarounds redundant. Would seem to be the easiest solution IMO

[cameni]

Angrypig's working on support for package reloading right now. Instances only refer to package assets and their own instance data, it's not that package is cached and copied to each instance, so we need to reload whole packages or their modified assets. There's some problem with that at the moment, but we need to resolve it so that a material editor can be made in-game.

[Levi]

Awesome! Can't wait to have an in-game material editor. That will be very nice, as well as the support for in-package geometry instancing.

[zzz]

Angrypig's working on support for package reloading right now. Instances only refer to package assets and their own instance data, it's not that package is cached and copied to each instance, so we need to reload whole packages or their modified assets. There's some problem with that at the moment, but we need to resolve it so that a material editor can be made in-game.

Is that why spawning the same model more than once causes them to share the same variables? i.e. when I spawn 2 identical cars and use an action button to do something like lower a window the other car's window gets lowered by the same amount

[cameni]

Partly, but that's because the script is buggy. Global variables in the script are shared among all instances (you may want to have that for constants, engine parameters etc). Instance specific variables have to be declared as instance members, i.e. this.windowpos = ...

[zzz]

Thanks. That'll help.

[konaone]

Mmmm ... .. sorry, but I still see some objects (Python Pago ural) with colors pink and purple textures ...... I also had a drop in fps ........ 30/19. .... did I miss something?

[PytonPago]

Mmmm ... .. sorry, but I still see some objects (Python Pago ural) with colors pink and purple textures ......

I havent updated the model whyte mipmap textures ... ill do it during the weekend ...

[konaone]

Aaaahhh !! I thought it was up to Outerra, sorry

[zzz]

So what will the next update focus on?

[cameni]

Nearest: likely a bugfix release first, then extended controls system.