FreeTrack Forum
FreeTrack Forum > FreeTrack : Forum Francophone > FreeTrack, Website, Manuel, Forum : avis et suggestions > FreeTrack V2.1
didja | #1 04/10/2007 - 21h52 |
Off line Www |
Que pensez vous de cette nouvelle version ?
Rémy |
C6_LeBorgne | #2 05/10/2007 - 22h33 |
Class : Beta Tester Off line |
Un peu déboussolé au départ , mon profil ne réagissait pas comme dans la V2.0 , mais après quelques modifs ça roule .
La réduction automatique de freetrack est incontestablement un plus , et j' apprécie particulièrement la croix de centrage dans la vue Web cam . Les paramètre de celle ci sont bien sauvegardées et c' est beaucoup plus confortable comme cela j' ai noté cependant un bug , ( je rassure , rien de grave ) : Dans l'onglet "Keys" si j' utilise "5 ( PAVE NUM. )" , la touche est sauvegardée dans le profil en tant que"(" et correspond donc au "5" alphanumérique J' avais déjà indiqué ceci pour la V2.0 Dans le même fichier profil les mapping PAUSE et CENTER sont inversés ( j' explique : si dans Freetrack j'utilise * PAVE NUM pour la pause et 5 PAVE NUM pour le centrage dans le fichier profil PAUSE = 5 PAVE NUM et CENTER = * PAVE NUM ) Cela fonctionne cependant correctement. |
Kestrel | #3 06/10/2007 - 04h36 |
Off line |
The hotkey system doesn't recognize all keys because of the difference between directx and windows keys. It was meant for basic shift modified key combinations, but with the recent addition of the key output capability, it makes the lack of correct mapping more glaring. I also need to allow for mouse and joystick assignments. I'll probably make small changes and release them as public betas to avoid extensive delays like with v2.1.
The strings were reversed. :/ |
C6_LeBorgne | #4 06/10/2007 - 08h46 |
Class : Beta Tester Off line |
If i edit the .fgp with the correct label of the key ( 5 ( PAVE NUM.) it works perfectly .
The key is correct when i map it in Freetrack but seem's not recorded correctly . |
Kestrel | #5 06/10/2007 - 10h02 |
Off line |
I've found it's a known bug in a Delphi function ShortCutToText() which is used to save the key name. |
babasior | #6 08/10/2007 - 22h25 |
Off line Www |
@kestrel :
is there a freetrack.exe fix to solved that ? so i can build a new package if it's needed ...
Babasior.
FreeTrack Online / www.Free-Track.net |
C6_LeBorgne | #7 09/10/2007 - 12h29 |
Class : Beta Tester Off line |
J' éprouve des difficultées à regarder dans mes 3-9 heures , cela semble du à la sensibilitée des "nouvelles" courbes . Il est beaucoup plus dur d' arriver en bout de rotation que dans la V2.0 sans augmenter énormément la sensibilitée sur les axes correspondant ! Du coup plus on est éloigné du 0° ou du 180° plus ça gigotte .
Ca m' a fait pensé à un truc pour une éventuelle future version , serait t'il possible d' implémenter des points " d'accroche" que l' on pourait placer sur les axes de notre choix à un endroit de notre convenance pour stabiliser la vue sur une position particulière de la courbe . |
babasior | #8 09/10/2007 - 14h28 |
Off line Www |
les trois points actuelle par courbe ne te suffisent pas ?
peux-tu faire un graph pour que l'on comprenne mieux ce que tu veux faire ?
Edited by babasior on 09/10/2007 at 14h29.
Babasior.
FreeTrack Online / www.Free-Track.net |
Kestrel | #9 09/10/2007 - 15h07 |
Off line |
I'm rewriting the directinput code, not a small fix. @LeBorgne: I can't understand your last post using Google Translate. |
tristan68 | #10 09/10/2007 - 15h45 |
Off line |
@kestrel :
Leborgne's translated post : I have difficulties looking at 3 o'clock and 9 o'clock (90° left and right). It seems to come from the new curve sensitivity. It's much harder now than in 2.0 to get to full rotation without increasing axis sensitivity. If you increase axis sensitivity, and are far from 0° or 180°, you experience stutter (translator note : can i say : buffeting ???? ). Could you include magnet points in next version, so we can easily stabilize our view at some user defined locations on the curve ? cya. |
babasior | #11 11/10/2007 - 22h39 |
Off line Www |
@kestrel :
Any news about hotkey fix ? is C6_Leborgne question will be a good feature for next freetrack version ?
Babasior.
FreeTrack Online / www.Free-Track.net |
Kestrel | #12 12/10/2007 - 04h22 |
Off line |
It is not a fix, it requires doing key input completely differently, which means bugs, bugs and more bugs. @Leborgne Increase smoothing and averaging to improve stability. Try to avoid using an aggressively non-linear response curve for yaw and pitch which increases sensitivity at the extremes. You could try a very high level of smoothing for stability and increase dynamic smoothing reduction to ensure that it is still responsive. Make you led blob/point appear bigger in the camera frame by adjusting exposure and threshold. Change your led position so that it moves more in the camera frame when you move your head. Use a higher resolution. Last but not least, hold your head more rigidly. Your idea is interesting, I have no idea how to do it though, especially while trying to maintain continuous non-digital motion. Using localized smoothing would make it laggy (no better than just using smoothing) and the only other way is to use different response curves, but they're controlled by Bernstein polynomials that won't allow for localized flat spots. |
FreeTrack Forum > FreeTrack : Forum Francophone > FreeTrack, Website, Manuel, Forum : avis et suggestions > FreeTrack V2.1
> Stats
1 user(s) connected during the last 10 minutes (0 member(s) and 1 guest(s)).
Powered by Connectix Boards 0.8.4 © 2005-2024 (8 queries, 0.033 sec)