0.33 will be delayed

What if they made it as an Ibishu, a successor of the 200BX ?

 

Hi, I have a particular question regarding one old T3D functionality which I use in my wip-map. It's about starting and stopping TSTATIC animations at a given keyframeposition like in this *.cs file:

Code:

function GarageDoorDae::onLoad(%this)
{
   %this.addSequence("ambient", "door_open", "11", "60", "1", "0");
   %this.setSequenceCyclic("door_open", "0");
   %this.addSequence("ambient", "door_close", "51", "200", "1", "0");
   %this.setSequenceCyclic("door_close", "0");
   %this.setSequenceCyclic("ambient", "0");
}

singleton TSShapeConstructor(GarageDoorDae)
{
    baseShape = "./GarageDoor.dae";
};

In a trigger it can be used like that:

Code:

local function triggerTest(data)
 local obj = scenetree.findObject("GarageDoor01")
 if obj then
    if data.event == 'enter' then
        obj:playAnim('door_open', false)
    elseif data.event == 'exit' then
        obj:playAnim('door_close', false)
    end
 end
end
return triggerTest

Will this functionality be stripped out soon? Is there a lua/json equivalent to achieve the same? I already equipped a couple of my garages with this functionality and really would like to keep it.

See end of the video:

 

That would also interest me very much. Do we have to expect changes?

 

Doesn't really make any sense. The Prasu is a GT while the 200bx is a stylish commuter/budget sports car.

 

I don't know if it has been said: are there any plans to update some of the neglected cars?

 

Will it be "back to normal" after the v0.33 release? I mean, will the progress for potential v0.34 feaures be faster?

 

smart... i like it
--- Post updated ---

isnt the 200BX like 1994 or something? if im wrong dont tell me i dont pay attention to when the cars were made

 

Yeah, it was from 1990-94.

 

How's it going?

 

1) Do you plan to extinguish the physics of smoke as in the Assetto Corsa?
2) What opportunities will the transition to Vulkan rendering open up?

 

The 200BX was made between 1990 - 1994 and the Supra we're talking start at 1993 so it wouldn't be impossible they made it as a successor, or another class for the same brand.

 

I think so, the main reason 0.33 will be "late" is because they are cleaning up the background so they can add more stuff easier (and possibly faster).

 

^I’m assuming it’s sort of like cleaning your room; Makes finding some stuff easier but the bulk of your bills//homework/projects still take the same time

Question for the devs: Any plans on a “On the Horizon” post or does it currently seem like something that could be at risk of overpromising?

 

And when you anger a gaming community only bad things happen. Just look at Stormworks! They announced plans and its one of the Jankiest games this side of the planet and the biggest barrel of toxic sludge this side of chernobyl. I don't think the BeamNG community would turn into the sludge pit from hell too, but you never know.

So yeah, its probably better to keep uncertain long term plans hidden...

BUT if you guys have plans that is being worked on and is going well, a roadmap would be very welcome. Heck even a general long-term direction pointing would be greatly appreciated.

 

I love you

 

Ok, so basically when you guys release your moms basic as-all-get-out minivan, it features a completely new, or heavily revised system... And to make the new stuff, you basically throw stuff at the wall and see what sticks... Yeah makes sense why you can't just say "here's what were doing, you can expect it this winter".

(Also, I really hope that "certain feature" isn't multiplayer... [I have a feeling it is though ])

 

What did multiplayer ever do to you to warrant a sad face at the possible mention of it possibly being added in a possible future update to an early-access game?

 

Alternate perspective. Instead of making promises through a roadmap with things that may or not be feasable, rather reduce the potential fallout by only spotlighting what you are currently working on. Maybe pick something for the beginning that is very likely to go into the game and give it a deep technical dive with frequent updates to it. Lets take take something more complex for this example, lets say a weather system. Describe how the dev team is thinking about implementing it, with which kind of pros and cons the different implementations would come with, what could and what could not be expected from this feature. The implications of it on other parts of the game, what modders may can do with it, the quirks it may has etc. etc, etc. From start to end.

Idea behind this is that you get into talks with the technical enthusiats of your community. They will share their thoughts about it to you, to others, make content from it, shine light on its possibilities and will very well be able to not just understand why it may not make it, but also potentially bring up ideas that may solve your problems. The community is a huge mixed ball of people and letting them become a part of the development process could connect the both.

Big win win in my eyes. Atleast i see the potential for it to succeed within BeamNG's community.

Its just like what this here is rn, you explain why a roadmap is unfeasable, i pickup on it confirm it, may add extra reason to it or like in this case dont, then present an alternate route on how the community gets what they want while you in return could build from the feedback too. Or in other words, the company gets the chance to showcase their things, the community gets the chance to feedback it. If you dont, like it is rn, it just leaves a gab of expectations and frustrations because certain features are highly expected to be in the game by this point, you can take up on it and explain the why and they will with the help of the technical side of the community understand it and again even potentially rise a solution to the problems