Jump to content

SilverOne

Members
  • Posts

    75
  • Joined

  • Last visited

Posts posted by SilverOne

  1. So wrong...

     

    There is no way DCS with this heavy barricaded engine can compete with FSX or X-plane which are all about 3rd party addons. Just look at the PMDG, A2A, VRS, Flightsimlabs... they produced more realistic aircrafts than ED will ever do.

     

    I flew to Krasnodar many times in MSFS, working flawless and actually, addon scenery (freeware) has more details than DCS one, and all navaids work.

     

     

    MSFS Krasnodar:

    img23978_2.jpg

     

     

    VS

     

     

    DCS Krasnodar:

    capture.jpg

     

    Actually, DCS world is fictional, every single airport is wrongly positioned, rwy headings are wrong, ATC and navaid freqs. are all wrong, Novorossiysk does not exist in RL anymore, Gelendzik is more airfield than airport, there is no parallel taxiway in RL...

     

    My point is that ED should concentrate resources on combat simulation only like they do right now.

     

    not to mention vatsim... man that was just epic. :thumbup:

  2. here you go:

    https://rapidshare.com/files/1967866694/facetracknoir.zip

    Thank you very much!

     

     

     

    I can't fin camera settings... Where are they?

     

    under the options on "tracker source" the reason why i'm warning about this is because i customized them to fit my environment.

     

     

     

    Great post.

     

    As you say its the stationary or near stationary wobble that is the main issue with FTNoIR if that could be addressed it would be a big step forward because pause/unpause doesn't cut it.

     

    What you can do to help though is loose the zoom axis (or increase its deadzone) for FTNoIR and map that elsewhere.

     

    TrackIR doesn't really have the wobble problem, though its not perfect either it can lose tracking from time to time (solved by a re-center Hotas mapped button).

     

    Yes that's kinda what i did, but i kept the zoom active just in case. i take it you bought a track ir?

  3. Flying? where?. This is not X-Plane of Flight Simulator, it's a combat simulator. It's a strange commercial movement, at least for me.

     

    Meh i look forward to blasting it out of the skies with an ER?

     

     

    lock on, or FC2, was sort of "balanced" in it's own way, red vs blue. There were the 27's and the f15's.

    This provided the community, us, some choosing headroom, and online pitting these planes agains't another was fantastic. Sort of like Starcraft, both had very different flying styles but kinda balanced. Neither plane had an advantage, but you had to learn how to fly it.

     

    I can't see this fitting in and help but think this is gonna grow a rather small community even more apart.

  4. Awesome post SilverOne. These are the kind of step-by-step guides we need.

     

    Is anyone using FaceTrackNoir v1.6 with BS2? The software is tracking, and in BS2 control options it is showing a headtracker. But I'm getting no response when in game.

     

    hmhmh, does it work with v1.5? are you sure tirviews.dll is enabled?

     

    I don't have BS2. also, i run with dummy track ir .exe off in the tirviews.dll settings.

     

    also do "tune axis" and see if it's actually working.

  5. After fiddling with this thing for hours, i finally have it setup up just perfect.

     

    Alright, so after carefully conducted research, i came to the conclusion that the best camera out there for this kind of stuff is the PS3 eye camera. So i bought it. Surprisingly it's actually one of the cheapest alternatives out there, costing me 15 bucks from ebay shipped, in other words, mere 10% of the whole price of a track ir 5.

     

    It's capable of some impressive 120fps, however, you'll only get up to 60fps on your pc, but don't worry, that's actually allot more than what you seem to need.

     

    As an extra, it comes with a 4 microphone array system.

     

    So, as expected, it's not exactly plug to play but isn't that hard either, all you gotta do is go here and download the Cl Eye Platform Driver. After that, just install it and connect it to your pc.

     

    In order to enable 60fps, you must create a cleye.config file inside the main facetracknoir folder and insert the following code inside, just copy paste it.

     

    you can also get the file here : https://rapidshare.com/files/1967866694/facetracknoir.zip

     

    <?xml version="1.0" encoding="UTF-8"?>
    <cleye>
    <item name="mode" value="advanced" />
    </cleye>

     

    you can use a simple text editor such as notepad, when saving, make sure to select "Save as Type: All files" below the file name, and that the name ends in .config

     

    So now it's time to install facetracknoir for FC2:

     

    to do this, go to the developers website here, click downloads, and download the V30, the v150 update, and v160 full version.

     

    The v130 is type installer so you'll wanna install this one first, then drag the v150 update files to the installation folder.

     

    After this is done, you'll wanna rename the installation folder to anything else except the original name. it should be inside here: C:Program Files (x86)Abbequerque Inc

     

    Install v160, and replace NPCclient.dll, and trackIR.exe from the OLD 1.5 version, into the 1.6 version, overwriting them, but FIRST MAKE A COPY OF THE ORIGINAL FILES ^^

     

    The reason why we're doing this is because version 1.6 is much more stable (less wobbly) than 1.5. And of course, it won't work without those specific files.

     

    Alternatively you may install only the v1.6 version and get the necessary files from here: https://rapidshare.com/files/1967866694/facetracknoir.zip

    i've included my own config, but take a look at the camera settings under "tracker source" on settings.

     

     

     

    Next you'll wanna download track ir fixer, you can get it here, however for compatibilities purposes, or in other words for it to work, you'll wanna download the older version TrackIRFixer v1.2.0.18 instead, now, grab this file and place it in /lockon/bin/x86/stable, open with administrator rights and run it. If it gives you a success message followed by an error, don't worry, it worked. Sorry for being stretchy on details but i did this 3 days ago.

     

     

     

    You'll also need TIRviews.dll, this a proprietary file from track irs developers. You'll wanna go to their website and download the trackir5 driver, install it, and find the TIRviews.dll on the trackir installation folder, drag this file into the main facetracknoir folder.

     

     

     

    Alright so it's time to open up facetrackn ir and configure it. When you open facetracknoir it immeadetely starts working so on tracker source you'll wanna hit "STOP". Next go to GAME PROTOCOL, and choose fake trackir, then open the little setting boxes below and enable TIRVIEWS.

     

     

    Punch START on facetracknoir, open up the game, go to options, control, AXIS(where you setup your joystick x and y axis), make sure track ir is showing up there. it has its own column , like a joystick.

     

    if it shows up, congratulations, it's working!

     

    You'll wanna consult the developers website for the manual, this will help you understand and fine tune your facetracknoir. you can do it here.

     

    Others have posted their settings, i'll post mine, you may get different results based on lighting and your setup itself.

    screenshot003gz.jpg

     

     

    I came to the conclusion that the wobbling won't really go away unless you set really high smoothness , which creates enormous lag. Here's a more responsive setup i'm currently using, you should probably only try running this on v1.6, lag is barely noticeable. You can probably even lower the VMIN value a little bit more. Please keep in mind this will depend on your camera, your face, the lightning around the room.. etc

     

    you can get this configuration from here, don't forget to take a look at the camera settings under "Tracker Source": https://rapidshare.com/files/1967866694/facetracknoir.zip

     

    screenshot009wx.jpg

     

    screenshot002vv.jpg

     

    screenshot001wa.jpg

     

     

    Both Smoothing and EWMA MIN are very sensitive and should be carefully fine tuned, they make your vision allot smoother at the cost of outstanding delay. The other two options aren't as sensitive, at least with my ps3eye. As a dogfighter (that's how i roll) i kinda need complete vision of the cockpit so this might be a little too much sensitive for you :D, however, my setup allows for really small reaction times, providing you with a near free lag experience. Anyway use my values as a guide, but eventually you might want to make your own. Also, after adjusting camera settings, such as brightness and RGB values, it seems to be more precise. You can do this from the "tracker source" tab under settings

     

    you will also need to create a keyboard shortcut key to center the camera, to do this just hit options and select keyboard shortcuts. Basically this resets everything to zero , so you're basically saying "this is how i look centered in all axis" or , looking forward.

     

    Also, keep in mind, when staring , say slightly to the right, it'll still wooble a bit, or should i say move around. it's slightly annoying, but for the price i really can't complain. and it really isn't that bad, this is also why i set up the deadzones.

     

     

     

     

    You've probably noticed that each time you load up the sim and enter your pit you're too "zoomed in". You've probably been "zooming out" the whole time. Well, sorry to disappoint but, this won't work anymore. You can probably move your head forward a bit and calibrate that as "standart" or "all axis 0s" and then move it back. This might sound like a great idea at first, until you notice this very slight constant zoom in and out.

     

    Thus In order to fix this, we must make that "standard" view a little more zoomed out, to do this you'll have to edit the view.lua file. Don't worry, i promise it'll be simple and not scary. Don't forget to make a backup of the file first!

     

    you can find this file at: LockOn Flaming Cliffs 2ConfigView, open view.lua with notepad.

     

    In line 145, or, around half way in the file, you'll find the folowing:

    If you can't find it, just copy some random text from here and go to "edit - find" or use CTRL F.

    -- Camera view angle limits {view angle min, view angle max}.
    CameraViewAngleLimits = {}
    CameraViewAngleLimits[PlaneIndex.iSu_27] = {30.0, [color="Red"]175.0[/color]}
    CameraViewAngleLimits[PlaneIndex.iSu_33] = {30.0, 117.0}
    CameraViewAngleLimits[PlaneIndex.iSu_25] = {30.0, 117.0}
    CameraViewAngleLimits[PlaneIndex.iSu_39] = {30.0, 121.0}
    CameraViewAngleLimits[PlaneIndex.iMiG_29] = {30.0, 112.0}
    CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {30.0, 112.0}
    CameraViewAngleLimits[PlaneIndex.iA_10] = {30.0, 97.0}
    CameraViewAngleLimits[PlaneIndex.iF_15] = {30.0, 110.0}
    CameraViewAngleLimits[PlaneIndex.iKA_50] = {30.0, 115.0}
    

     

    Depending on the plane, ion my case the Su-27, you'll wanna change the View angle max, the second variable in the line, i marked it in red for you. I personally like 175, but i didn't really fiddle with it. After you've made your changes just save the file. If anything goes wrong, just restore the backup you made.

    This wobble, or movement, isn't noticeable when you're zooming in or out, but when you're still it's very frustrating; takes the "feel" away from your aircraft.

     

     

     

     

    here's a video for your viewing pleasure, recorded with the smoother setup. Sorry for the shakiness, i was holding my iphone:

     

     

    and also Here's my setup, by the way, my x52pro is usually placed where the keyboard and trackpad are:

     

    img0023zw.jpg

     

    in my experience, the camera works best below the monitor, i keep it close to myself and take advantage of the ps3 eye microphone.

     

     

    i hope this small post helps you, i wanna thank the original poster RipKirby, janisx(from sourceforge.net) who apparently dedicated 10 days of his life to get this working. you can see his much shorter instructions here, and most importantly, the developers who put so much time and effort into the development of facetracknoir; you should probably consider making a small donation to them.

     

    If for any reason i have missed some steps please let me know! And if this helped you please rate me + on the lower left on this topic [+- button]

    • Like 2
  6. This file has 1000 lines of code :/

     

    you don't happen to know which one it is?

     

    here's the file for you :

     

    http://pastebin.com/6sAR9u9i

     

    ^^

     

    from the view.lua file i get :

     

    iSu_27 = 1,

    iSu_33 = 2,

    iSu_25 = 3,

    iSu_39 = 4, -- Su-39 or Su-25T

    iMiG_29 = 5,

    iMiG_29K = 6,

    iA_10 = 7,

    iF_15 = 8,

    iKA_50 = 9,

    iMirage = 10,

    iMiG_23 = 11,

    iSU_17M4 = 12,

    iIL_78 = 13,

    iAV_8B = 14,

    iA_50 = 15,

    iC_17 = 16,

    iC_130 = 17,

    iF_4E = 18,

    iF_5E = 19,

    iF_16A = 20,

    iF_16 = 21,

    iFA_18 = 22,

    iFA_18C = 23,

    iKC_10 = 24,

    iMiG_27 = 25,

    iSu_39 = 26,

    iSu_30 = 27,

    iTORNADO_IDS = 28,

    iF_2 = 29,

    iYak_40 = 30,

    }

     

    i take it's one? geesh i guess i should have started at the top.

     

    EDIT: actually what i want is the FOV, field or view aka zoom. but can't seem to find the right one :D

     

    i've changed all the values from "1" but with no sucess :(

    --------------

     

    final edit lol, i got it working... turns out its in the "CAMERA view angle limits" in view.lua... i thought these would have no affect because they were limits... owell i was clearly wrong

     

    thank you for your help.

  7. Ahh! I think I got it now - you want to modify your eye-position in the cockpit ....

    Another problem (Maybe I'm too helpful sometimes...)

     

    I have no working FC2 install...and I use the values from DCS-A10.. - point.

     

    Look out fot the "SnapViewsDefault.lua" in

    \Config\View\

     

    our problem:

     

    This are the parameters you have to edit and what they are doing:

    You have to edit the values starting in line 1055 to change the default start-up view below .

    \Eagle Dynamics\DCS Black Shark 2\Config\View\SnapViewsDefault.lua

    The values can be positive or negative!

    Snap[11][13] = {} -- Default cockpit view
    Snap[11][13]["y_trans"]   = -0.041336805555555564    -- move viewpoint Up/Down
    Snap[11][13]["x_trans"] = 0.36 -- move viewpoint Forward/Backward
    Snap[11][13]["hAngle"] = 0 -- Tilt viewpoint Left/Right
    Snap[11][13]["viewAngle"] = 75.0  -- FOV aka Zoom
    Snap[11][13]["vAngle"] = -25 -- Tilt viewpoint Up/Down
    Snap[11][13]["rollAngle"] = 0  -- Roll viewpoint Left/Right
    Snap[11][13]["z_trans"] = 0  -- move viewpoint Left/Right 

    you want probably Lower:

    Snap[11][13]["x_trans"] = 0.36 -- move viewpoint Forward/Backward

     

    -- maybe this will help.

    Happy fiddling! - and - to play save:

    Make a backup before you fiddle! ;)

     

     

    aah awesome, i knew there had to be a way to do it ;) i'll fiddle with it after dinner and report back!

     

    oh also i rated you +... this forum for some reason keeps defaulting to russian under chrome... i've given up on it , so if i made a mistake let me know!

    • Like 1
  8. Don't know where to do this...

     

    One solution (If you don't zoom around )

    is to find your value and (BTW its calculated in degrees)

    and make a line like this: CameraViewAngleLimits[su_27] = {120.0, 120.0}

     

    so the zoom limit is set in stone.

     

    ...

     

    or - didn't I get your request at all?! - wondering...

     

    Edit:

    and BTW : I don't use FT no IR... so pictures describing what you want to change would be very helpful. - another idea is to tweak the axis of the Face Tracker you are using in the axis command section in game of DCS.

     

    Thank you for your response,

     

    Alright, so face track, unlike track ir isn't very stable. It constantly wobbles, "moves", around even when your head is still. For example, if i activate the zoom function, and i am perfectly still, my head will be moving back and forth constantly, even though i'm not moving.

     

    when i load the game, the default zoom is too close to the instruments. So i just pull my head foward, calibrate face track - which is like saying hey, this is where everything is 0. and then pull my head back, effectively zooming out.

    Again this presents the problem that the view is unstable, it keeps zooming in and out, even though i am not moving.

     

    so, in order to retain the zoom ability, i want to load my cockpit zoomed out.

     

     

    Why don't i just deactivate zoom in facetracknoir? because i can set in a dead zone for zoom, and it'll only zoom in if i go beyond this dead zone, effectively eliminating the permanent wobble in the cockpit.

     

    so this is the default "0" zoom in lock on.

    screenshot20120120at112.jpg

     

     

    This is what i want it to be:

    screenshot20120120at112.jpg

     

    please ignore the slight vertical movement, and focus on the zoom :P

  9. Navigate your mouse to a file called "View.lua"

    in <installation folder>\Config\View.

     

    Than open it with a editor (I recommend Notepad++)

     

    and higher the second value of the plane you want to edit to something like 160.0 to be able to zoom further out.

     

    line #110:

     

    Thank you for your response,

     

    i did find that variable, however what i want isn't to change the limit, but instead, change the standard value, that is, when you load the cockpit i want it to be less zoomed in by default, so that when i move my head it moves from that value.

     

    lets say the default zoom value, when you open the cockpit is 50. I want it to open at 30.

     

     

    the default view is just too zoomed in, and using facetracknoir results in constant movement "inside" "out".

     

    Best Regards.

  10. Not at this time, but if and when you would run out of activations entirely you can contact support for a refill.

    Dear EtherealN

     

    Thank you for your response,

     

    that will most likely not be necessary.

     

    again thank you for your help.

     

    Best Regards

    Humberto Carvalho

  11. Hello!

     

    Yesterday i attempted to install Flaming Cliffs 2 on my macbook pro. In order to save time, i booted windows bootcamp partition through parallels, installed and activated my product successfully. i even loaded a quick flight just to have a look.

     

    Happy it was working, i booted windows and attempted to play. Unfortunately due to activating lock on through parallels, there was a vast difference of drivers and virtual "hardware". The security agent refused to run lock on and asked me to validate again.

     

    I attempted to validate my installation only to have the validator crash, and, every attempt that followed stopped short of a " validation corruption" wasting quite a bit of my remaining activations.

     

    so far i haven't been able to activate since then.

     

    Best Regards

  12. It is far from unusable in it's unmodded state. What they talk about here won't be a problem for 90% of users, i dare say.

     

    For my part, i can do AAR easily now, which is probably the most precise i ever need to fly, so i'm good.

     

    Yeah shure, but for 400 $ these problems shouldn't exist, i've always been very picky about stick jumps, even in dogfights, sorry, but when you need a little bit more of a pull you can't have your stick jump arround or you die.

×
×
  • Create New...