Is this normal then for V12? I'm amazed.

So nobody else has this problem??????????

I just tried it in VP12 and got the same results as you, except you said if you select a file with the mouse, then the arrow keys work for navigation. When I select a file with the mouse, the arrow keys don't change anything. The same file continues to be selected.
So for me, the arrow keys don't work at all in Explorer and the enter key does not put the event on the timeline. (I also tried in VP11 and the arrow keys and enter key work properly.)

Since we are getting slightly different results, I wonder if there is a setting for this. I looked at Preferences and didn't see anything relevant.

The most likely scenario is that SVP v12 inherited all of v11's unfixed bugs, then added an entirely new crop of its own to the mix. Sony should have never released v12 until all of the v11 bugs were fixed. In the world of software development it's rare to find a newer release of an existing program that isn't built on top of the existing versions source code ... bugs and all.

I was starting to think I was going bonkers. MOST folks here must be clear of this problem judging by the lack of replies? Strange how I've got 2 installs - Vista and Wi8, both using different drivers for graphics, and I've got his annoying problem on both!

Me, too. As i recall, ctrl-alt-PgDn took me to the end of the project in Vegas 11, and none of the navigation keys seem to work in Vegas 12. i was a beta tester, and did not feel 12 was ready for release, but when the upgrade was on sale for $99, i went for it. i guess i will have to fiddle with the keyboard macros or something.

"MOST folks here must be clear of this problem judging by the lack of replies?

I've been reading this thread but didn't reply because I've never used the Vegas Explorer. Now, while I'm bored and waiting for the Grammies to start, I tried the navigation in Vegas 9.0e, 10.0e, 11-701 and 12-486. On my machines, it is only Vegas 12 that fails to load the media to the timeline when the enter key is pressed.

"The most likely scenario is that SVP v12 inherited all of v11's unfixed bugs, then added an entirely new crop of its own to the mix."

While I have great respect for Gary James, I think he is wrong in this case. The coders who worked on Vegas Pro 12 were perfectly capable of creating this bug without inheriting it from version 11, since 11 seems to work as Vegas traditionally has.

Now, I'm going to restore my system back to its pristine state after tinkering with Internal settings until I forgot all that I did.

Here's what happens here VP12(486):
- can confirm Arrows don't work at all in the Explorer Tree View, but do seem to work as usual in the Files side.
- pressing Enter to drop a selected file (as selected above with arrows) on the timeline fails.
- other keyboard shortcuts appear to work.

cmallam....me too.

So is this a bug worth reporting? And...how do I do that? never done it before.

Yes it is worth reporting!

Goto My Support (which is listed under My Account at the top of this webpage), log in and find the link to 'Ask a Question" .... or goto https://www.custcenter.com/app/ask .... you need to fill in a lot of stuff, and can fully describe your problem, including attaching files... also a good idea to include a link to this forum topic. Be very clear this UPDATE caused the problem(s).

Their 'first response' will be to uninstall/reinstall or something similar to waste your time; don't fall for that one, just persist and insist the problem be escalated up the line to someone who understands the issue.

Ok, have submitted a report. You can't get much 'cleaner' than an install to a sparkly new OS with nothing else but DVDA installed on it. :-)

Got a reply back from SCS. Suggested to delete all of the thumbnails in the media pool folder under local apps. Did this, but problem remains.

Arthur,
it seems that suggestion is tech support's Special this week. See the 'Split screen view is red' thread.

Yes, I'd already seen that one. Was worth a shot anyway. It's looking like my workflow will be to do the rough edit in an earlier version, then transfer to V12. Really wouldn't have thought this would be too hard to fix...but then I'm not a programmer.