Meant to be Seen

CyberVillain wrote:I do not want to run around with my weapon up high all the time (My arm gets tired).

CyberVillain wrote:Checked your video quickly, cant see that you rest the "weapon" at any time in that video?

With rest I mean like letting it hang in the sling like a real soldier would do

CyberVillain wrote:come to think about it, maybe there is no point in having tracking on the gun in a mouse controllerd game, I will try tonight just to use the gun as a trigger for shooting and let the headtracker do the work of aiming (The head follows the gun anyway).

In games like Half life 2 VR were the gun is moving seperate from the head its more point to have actual gun tracking

NeoTokyo_Nori wrote:

CyberVillain wrote:come to think about it, maybe there is no point in having tracking on the gun in a mouse controllerd game, I will try tonight just to use the gun as a trigger for shooting and let the headtracker do the work of aiming (The head follows the gun anyway).

In games like Half life 2 VR were the gun is moving seperate from the head its more point to have actual gun tracking

While it is of course possible to have the headtracker do the work of aiming, I think you will find out that it becomes an uncomfortable experience to have to aim with your head, especially when accuracy is important. Our heads and neck can make "broad" movements easily, but I think trying to make constant fine adjustments will give you a stiff neck in a short time and also "Bird head" syndrome

I have been using the method of turning on and off mouse control by the gun for a while,
and I think it works fairly decently for now, rather than try to get the hardware/software to be perfect all the time. As far as separate head, body, gun movements, I guess we will have to wait for fps games that are made for VR

CyberVillain wrote:Most games that support gamepads do not have stepless speed only full speed when the axis leave the deadzone. :/
But yeah for the games that really have stepless control that should work

konstantin_lozev wrote:Hi Neo, fully agree with you on this. I have had this weird feeling of shooting with my nose in some of the Dive demos. Does not bring too much immersion, tbh... That's why it's important to test with differennt sensitivity and threshold settings lag free.
Edit: tested without the DIY HMD on (video latency still high) only with the two IMUs (the tablet and wiimote) the threshold idea of activating the iron sights while the two are aligned. The yaw drift between the two over time invalidates that approach

CyberVillain wrote:New version out! MIDI and some other stuff

CyberVillain wrote:New release with vjoy fix this time ALso migrated file hosting to Github releases.

"System.Collection.Generic.IEnumerable\1<!!0> Microsoft.Scripting.Utils.ReflectionUtils.GetCustomAttributes(System.Reflection.Assembly, Boolean)"

CyberVillain wrote:I updated the python engine for 1.8 probably has todo with that, but it did work on the machines that I tested (win7 x64 and w8 x64).
Will look into it

I have missed that they have Force feedback support, but what good does that do when its a virtual stick?

edit: aha, you want to send the signal somewere else offcourse.

CyberVillain wrote:Do you know where the docs are for FFB? Didnt find anything on vjoy page (Just looked quick since Im at work). I guess there most be a API for getting FFB data and antoher API to send it to a real joystick?

edit: Hmm, or sending it to the real joystick should offcourse be the joystick plugin, it does not support FFB so thats has to be fixed too

CyberVillain wrote:What is the software with the smallest footprint to test force feedback with? A game demo, some kind of utility etc?

BOLL wrote:Just got into FreePIE and Python It's fun! But, as mentioned above I also have problem with keyboard.setKeyDown(), I'll explain

Looping over setKey works for emulating WSAD with a stick (running xbox360 controller), but looping over it for things like the start button makes menus jump up and down frantically.

This is when I looked to use setKeyDown so I can just simulate holding a key, but. If I keep setKeyDown in the loop it acts as setKey and presses the key every cycle.
If I add a global state it only presses the key once, then it doesn't hold it down. In notepad it only becomes the one character it never starts repeating. So to me it seems like it's acting exactly like setKey o.O Hmm?

I can post code if you want to, but would have to slim it down a bit probably

Edit: Uhoh, discovered the start button on an Xbox360 pad spams in notepad (and games) but not the back button, apparently the different buttons act differently o____O huh... weird. Easily fixed with a function though.

Code: Select all

def singlePress(control, key, state):
	global b
	if( control and not b[state] ):
		keyboard.setKey(key, 1)
		b[state] = 1
	elif( not control ):
		b[state] = 0

Sure are some quirks to this, haha.

        public void setKey(Key key, bool down)
        {
            if (down)
                plugin.KeyDown((int) key);
            else
                plugin.KeyUp((int) key);
        } 

        public void KeyDown(int code)
        {

            if (!MyKeyDown[code])
            {
                //System.Console.Out.WriteLine("keydown");
                MyKeyDown[code] = true;
                int scancode = ScanCodeMap[code]; // convert the keycode for SendInput

                var input = new MouseKeyIO.INPUT[1];
                input[0].type = MouseKeyIO.INPUT_KEYBOARD;
                if (ExtendedKeyMap[code])
                    input[0].ki = KeyInput((ushort)scancode, MouseKeyIO.KEYEVENTF_EXTENDEDKEY);
                else
                    input[0].ki = KeyInput((ushort)scancode, 0);

                MouseKeyIO.SendInput(1, input, Marshal.SizeOf(input[0].GetType()));

            }
        }

DrDim wrote:Hi there! I have a small request!

There was a page on the wiki that contained a reference for basically "everything" FreePIE. That used to be very helpful for creating scripts.
For some reason I can't find that page anymore. Maybe it got pulled from the wiki, because it was outdated? Anyway I pledge for a new "dump" of all FreePIE inputs for reference.

CyberVillain wrote:

DrDim wrote:Hi there! I have a small request!

There was a page on the wiki that contained a reference for basically "everything" FreePIE. That used to be very helpful for creating scripts.
For some reason I can't find that page anymore. Maybe it got pulled from the wiki, because it was outdated? Anyway I pledge for a new "dump" of all FreePIE inputs for reference.

Yes, I forgot to check that code into GIT thats why, need to rewrite it, until then, press ctrl+space in the editor in FreePIE and the same reference will be presented

CyberVillain wrote:So it looks like KeyDown is allready doing what you are doign from script?