Somehow I can't get the empeg to automatically restore the last visual when powering it up in DC mode. As the subject states, I'm running beta 11 with hijack 221. I've enabled both the 'restore dc/car visuals' and the 'restore visuals (v2beta11)' options in the hijack menu. This is what happens:

1. I'm running the empeg in DC mode looking at funnelweb.
2. I pull the empeg out of the docking bay, then put it back in.
3. The empeg boots, the player starts and displays 'info: track'

If I understand correctly, hijack should simulate a press of the lower button at this point, making the player display the last visual. Unfortunately, nothing like that happens ;-) If I press the button myself, the player will go back to the last visual as expected.

Now... did I miss something? I've read a lot about problems with beta11 regarding this feature but thought a workaround was implemented in hijack some versions ago.

Hijack doesn't simulate a long downpress. It does something a little more complicated. But it should still work.

Try this. Go to the player's MAIN MENU and HAND-SELECT info:Track. Then hand-select info:Transient.

Now try the power pull.

Did it work this time? If so, let us know, and then Loren can add that to the FAQ.

You're not the boss of me!

Hey, I said "can", not "must" or "will".

Gasp, is this some form of friendly turf stepping pissing war in disguise? Battle between FAQ writers. Gasp!

Calvin

I don't think so. Loren's in much better shape than I am. He could probably kick my ass.

Hahah. It's all in Jest... but I'll take you in a snowboard chicken fight! =D

Unfortunately, it didn't work. After selecting 'info: track', then 'info: transient' and rebooting, it will still stay in 'info: track' mode. Is there anything else I can try?

Did you turn off the "Show Visual Names When Switching" feature? Mark just recently let slip the arguably critical piece of information that this is required in order for the feature to work.

Also, is your player experiencing this bug or this bug perhaps? Or have you done anything else nonstandard to the player or in the Hijack kernel that might make it get confused about its home/car position?

Actually, the visuals naming thingie is not needed for the Restore DC/Car Visuals function. It's only needed for the v2beta11 bugfix option.

Can anyone else here reproduce this person's problem?

Thanks

Nope, my player has no problem recognizing wether it's in the car or at home. I'm also aware of the 'growing config.ini' bug and the workaround.

Hmmm.. this sucks. I can't be the only person on the planet having this problem or can I? ;-)

Restore Visuals has never worked for me in the car, but I've only had Hijack a few days and it doesn't bother me enough to figure it out. Player 2.0b11, display visual_names = 0.

Snowboarding holding chickens and flailing away at each other?
Training chickens to snowboard?

The mind boggles...but please video the battle and post here

You're not the only one. I am having this problem as well. I have verified that my player believes it is in the car and that HiJack has the proper settings. Any more ideas?

>Restore Visuals has never worked for me in the car

It was broken for about 15-20 releases (the early 200's) until somebody told me about it. Works fine now in the latest releases.

-ml

Works fine now in the latest releases.

Are you sure? v232 isn't working again. It was working about 4-5 days ago, and I stay pretty current with the releases.

I have show visual names checked, restore dc/car visuals enabled and restore visuals (v2beta11) enabled.

Tom

>Are you sure? v232 isn't working again.

100% positive. Works flawlessly here.

How about some more information?

What kind of info would be useful to you? Mine is doing it as well.

Well, if I had enough information to set my player up exactly the same as your player, then in theory the "bug" should happen here as well. Then I would be able to observe it in more detail, and figure out why it happens that way.

So.. assume I just received a shiney new player. What settings must I effect to reproduce the problem? What power supply, in car, or in home? Exactly which visual? Which info mode? Exactly what sequence of actions/operations must be performed (eg. push a certain button, wait xx seconds, unplug the AC-adaptor, wait xx seconds, plug it back in, and observe xxxxxx..).

Come on guys.. I might be a kernel guru, but my clairvoyance powers are limited here.

-ml

Sorry, I thought it would be obvious since it was broken just a few releases earlier.

Nothing to report now, v233 is working for me. No config.ini or hijack settings have been changed either.

Tom