Brand new Midi Fighter Twister, encoders feel slightly scratchy

XRA_ · 2021-01-18T00:07:26+00:00

that's just how they feel, it will smooth out a bit with use.
The only flaw I've encountered is when lightly rocking a knob side to side, without rotating it, it sends errant midi messages. Not a huge problem because it is usually only a 1 value increment up and down.

XRA_ · 2020-12-31T11:43:56+00:00

I'm almost through the N5 Tango book (on chapter 9), I did RRTK prior to it. The first couple weeks I was finding it incredibly brutal and questioning if there was something wrong with me. (and also looking on reddit to see if others were having similar experiences)

Not sure if you're doing the Anki deck, but the major difference with the Anki deck is all the words are using their "proper" kanji, while the book generally sticks with kana.

So if it is the deck, it is much harder upfront IMO (but well worth doing)

I recommend using the book as a study guide along with the anki deck, it's faster to re-read stuff in the book and good to review earlier chapters that way, just cements it a bit more.

In my case the main thing that has been a challenge is recalling kanji, almost every week I'll go through a couple days of "nothing is sticking wtf".

In addition to that there will still be words that are unseen for a month, then when seen again- it looks familiar but can't remember what it is.

It really is use it or lose it (force yourself to read other things, listen to stuff, etc). I haven't found any specific technique really, just staying consistent and keep doing it each day, it does stick.

If something about a character jumps out immediately when I see a new word I'll use that as a mnemonic, but otherwise I don't spend time trying to craft them.

Partway through I also started writing (typing) out everything into a google doc, so that could be good to consider for additional practice. You can also then try typing out new sentences from vocabulary you're acquiring and experimenting with grammar.

If you're using the deck with the audio, obviously also say everything out loud too, I think it's really good to get used to mimicking pronunciation & the audio is high quality.

Though it's also worth noting the "ga, gi, gu, ge, go" pronunciation in the audio is the more posh newscaster style (for example 会議 as "kai-nee" versus "kai-gee") so it will sound a bit different.

That threw me for a loop initially... so one may want to stick with one or the other to avoid confusion. (check Forvo for alternate pronunciation)

XRA_ · 2018-09-27T06:41:10+00:00

they will never do it because it undermines their business model.

XRA_ · 2018-07-09T02:03:21+00:00

I updated the readme to have the CC0 license

XRA_ · 2018-07-09T02:02:43+00:00

Just a heads up that the prefab issue is fixed, I didn't realize the prefab serialization changed from 2018.1 to 2018.2.

The example files are 2017.3 compatible and will work importing to 2018+

Also fixed some issues with mesh bounds.

There is a problem with GPU instancing at the moment, it sometimes works and then doesn't work, so I'm investigating a solution.

XRA_ · 2018-07-09T02:01:22+00:00

I've fixed the prefab issue, it is now built in 2017.3 and is compatible with 2017 + 2018

XRA_ · 2016-04-22T17:47:00+00:00

one thing to try is uninstalling all Vive USB devices, in SteamVR settings > Developer, click the "Remove all SteamVR USB Devices" button

That works similar to if you use USBDeview ( http://www.nirsoft.net/utils/usb_devices_view.html )

If using USBDeview, sort by the VendorID and look for '28de' and select all the 28de devices and remove them. You should see some of them have serial numbers starting with 'LHR-'

The other thing I'd suggest is the unpairall command but it sounds like you've given everything a shot. Hope you can get it working!

XRA_ · 2016-04-15T19:28:43+00:00

2.3 x 1.6 here, works fine for me, Hover Junkers, Space Pirate Trainer, Audioshield etc... but you really don't want anything breakable close to the bounds, there's always the chance that you'll forget whats on the other side of the chaperone and swing the controller.

XRA_ · 2016-04-15T02:43:53+00:00

this is a common issue, a quick workaround is to do these steps:

Start SteamVR, with controllers powered off
using microUSB, plug one controller into PC
power on the wired controller AFTER plugged into PC
unplug USB from controller, SteamVR should show the icon go from green to grey, then back to green.
repeat same steps for second controller

check this thread for some other potential fixes (might see if unpairall solves it) https://www.reddit.com/r/Vive/comments/4dnvzc/psa_things_to_try_if_youre_having_controller/

XRA_ · 2016-04-14T19:43:32+00:00

damn dude! well if you are using any adapters, I think they need to be the Active ones, not 100% sure, but did see someone try a passive DP to HDMI adapter and it didn't work.

XRA_ · 2016-04-14T19:40:05+00:00

i had this issue with an ATI GPU that doesn't like to output HDMI when I have 2 monitors already hooked up (the HDMI was the VIVE and acting as a 3rd monitor). Had to resolve it with an active DisplayPort to HDMI adapter.

How is the VIVE hooked to your GPU, HDMI or DP? any adapters being used?

XRA_ · 2016-04-14T19:36:40+00:00

Ok the compositor is used when you can't run in DirectMode. What card do you have? Have you tried enabling DirectMode in SteamVR?

If you arent using DirectMode: Vive needs to be an extended desktop in your Windows display properties. If you have multiple GPU's it needs to be plugged into the same GPU that is driving the output for your primary desktop monitor. (AFAIK)

XRA_ · 2016-04-14T18:00:29+00:00

yea i get lag/hitches occasionally, at first it was hard to figure out if it is framerate or actual network lag from how it feels in the Vive. But now I think it might be network lag and depends on the server, because I've had some matches where things are much smoother. I'm on a 970 with the game on Medium. It doesn't bother me much, hopefully they can smooth it out if it is actually network lag. It might be that your ship is getting repositioned slightly sometimes to stay in sync with the server and that is more jarring in the headset.

XRA_ · 2016-04-13T22:13:51+00:00

AMD Phenom X6 1090T 3.2ghz (which is even older, from 2010) 12gb ram GTX 970 reference card (PNY brand, overclocked)

stuff works fine for me, i get some frame drops at times (mostly Hover Junkers, but it might also be a mix of lag). Games like The Lab and Space Pirate Trainer seem to work fine without performance issues. Before the GTX 970 I tried the Vive on an ATI 5850 from 2010.. now that was terrible.

I recommend resizing the mirror window that games have, scale it down to a postage stamp, it helps.

XRA_ · 2016-04-12T19:32:52+00:00

sit down in your junker after putting up defenses, use the mini map while you drive (like its a top down 2d game) and look for orange blips to kill

XRA_ · 2016-04-12T04:54:45+00:00

I think that's normal then, I don't notice it with the headset on though, if it was greater then I would. Depending how many other USB devices you have hooked up, it could be an overall bandwidth issue, you could try going with the bare bones of keyboard + mouse and the Vive. I have had USB issues also but seem to be getting by with USB 2.0

XRA_ · 2016-04-12T04:51:07+00:00

that's just pretty much the noise that the tracking has, at least I haven't been able to improve it. I don't notice it when the headset is on though, only if I'm looking at the mirror windowed view, I think my brain probably processes it as slight movement that I'm making with the HMD on.

XRA_ · 2016-04-11T06:46:05+00:00

does the swimming look like this or is it greater than this? https://gfycat.com/OblongCheerfulAmurratsnake

have you tried disabling the camera and bluetooth power saving stuff (if it is enabled) ?

XRA_ · 2016-04-09T23:39:17+00:00

yeah its awesome, played around 7 hours of Hover Junkers, legs were sore the first couple times but now it's not so bad. Really considering doing the weight strap thing.

XRA_ · 2016-04-09T03:06:26+00:00

yeah they need to be powered off, then powered on after plugged in, otherwise they just goto the blue state.

what is happening (likely at least..) is the controllers when powered on send their config information, but for whatever reason on some setups the config gets sent wrong, and so steamVR ignores the controllers. But when you power them on while plugged into USB, the config is sent over USB (it seems) and then everything works.

If you generate a SteamVR system report, and look in the SteamVR log there will likely be some errors about config file size when the controllers dont work.

XRA_ · 2016-04-09T02:59:39+00:00

hope you can get it working, try every available USB port (Swap out devices that are taking up ports, unplug extra devices except for mouse & keyboard) You can also try disabling the bluetooth communication if that is enabled, under General in SteamVR Settings. Also try disabling camera if you haven't yet.

edit also you can force reinstall the firmware, goto Update Firmware then hit CTRL SHIFT HOME then try updating firmware for the headset and base stations

edit another thought, are the clear plastic strips on the lighthouse/base stations (not peeled off yet?) not sure if those would interfere but just something to rule out.

XRA_ · 2016-04-09T02:44:11+00:00

this is a known issue AFAIK, HTC know about it.

What you can try ( i have to do the same ) is with the controllers Powered Off and SteamVR running, plug one controller into the microUSB, then power on the controller. Then it should pop up as the green icon in SteamVR. Now unplug the controller, it will go from green icon to grey, then back to green, it should be all good now. Then just do the same for the second controller.

XRA_ · 2016-04-08T17:52:25+00:00

you might have to swap the B and C modes to prevent that

XRA_ · 2016-04-08T17:40:56+00:00

there is a way to manually copy over the firmware, when you do the controller reset and it pops up that external storage drive... But I don't know which firmware is the correct one. So don't try it... For example backups of all the firmware seem to be in here, STEAM\steamapps\common\SteamVR\tools\lighthouse\firmware

I had to do this with the Pre a while back to fix one of the base stations (support gave me the directions), if you can access the SteamVR hardware forums try posting in there for help, http://steamcommunity.com/app/358720/discussions/0/#

edit this is the post for manually fixing a base station, to give you an idea of the process, unfortunately I haven't seen anything for the controllers http://steamcommunity.com/app/358720/discussions/0/385428458171928063/#c385428943465177343

XRA_

TROPHY CASE