Cutting Power On Shifts

@Diamondback has the shift logic changed to where the parameter ( "shiftEfficiency":1.00, ) is ignored in 0.15?

For example a 1500 HP engine transmission is cutting power to ~300 hp on every shift. on older versions with that parameter set to 1.00. it used to power through every shift.

 

Interesting. Wonder what could be causing it.

 

I noticed some weird shake in all cars with manual transmission after 0.14 update. It happens when you clutch kick and spin the wheels, also all the needles on the gauge cluster start shaking while spinning the wheels. For me it's really annoying and wish they can fix it. I'm on version 0.13.0.5 and I won't update to 0.15 until it's fixed.

 

I noticed this after 0.14 too. Was kind of surprised the cars did that, especially when they had a solid axle. Turns out, it's just wheel/axle hop which adds even more realism

 

I have noticed it a few times in first gear but as for at speed I tend to bang shift it so full throttle and then slam it into gear and I dont notice the drop as much for me, or I do notice it and ignore it

 

--- Post updated ---

I know what is wheel hop and I know how car speedometer works.
The problem is the whole car starts shaking like crazy which is not realistic at all. Try putting a NOS in RWD manual car, for example ETK-K series and you will see what I mean

 

@Diamondback

This is what i'm talking about



See 1>2>3 is perfectly fine 3>4 is like the transmission is short shifting and then its "confused" so it cuts power. and then it flares.

It started with 0.14

"shiftEfficiency" is set to 1 and it still does this. Sometimes its worse. There is nothing set in the transmission jbeam that will tell it to cut power on shifts.

(Don't mind the crap driving)

In older versions of the game it used to "bang" through every gear and shift perfectly with no flares.

Now it seems, some kind of torque management is enabled.

 

Remember that shifting is torque converter rpm, however calculate optimal shift point uses engine rpm (while actual shifting uses torque converter rpm, which often makes issue with not to shift but banging against limiter), there were other interesting bits too as shift logic is kinda mix of engine and torque converter rpm based.

I just quickly looked video and it looks like if upshift and downshift would be too close to each other, pay attention to TC rpm before and after the shift and probably shift down needs to be bit lower rpm now, I guess you have optimal shift point calculation disabled, that can cause lot of issues with narrow rpm range as it is not using TC rpm, but is using engine rpm, so it can shift at wrong time, then TC rpm drops so low that shift logic downshifts, but optimal shift point upshifts after that.

One change I have seen also is that now TC lockup opens during the shift in stock vehicles, which again can be bit problematic for having solid good shifts.

Not sure if any of that helps you to find what is causing the issue, though.

 

@fufsgfen

Ah yes, converter unlocking during shifts.. Good call totally forgot about that.

Confirmed with my lockup switch in locked position.

@Diamondback is there a parameter that can be entered in to jbeam that allows the converter to stay locked during a shift like older versions of beam?