Jump to content

JoeyJoJoJunior

Members
  • Posts

    191
  • Joined

  • Last visited

Posts posted by JoeyJoJoJunior

  1. I don't like the idea of compressed PCVR over a cable. I'd accept the loss for a robust wireless solution, but not a cable. Don't like the FB stuff either. I have an account, but I don't want it linked to anything. I just use it for messenger basically, and all my info on there is fake.

  2. It seems to be 1gb less than you have.. I have 11 I'm nearly always at 10, when I had 8 I was nearly always at 7

     

    Unused memory is wasted memory. You'll see the same if you pay attention to Windows memory and usage and go from 16GB to 32GB. With the same usage pattern, you will see a rise in memory usage because the OS will simply keep things around in memory longer. When we have maps that take 20+ GB, you can see how the theoretical limit for how much ram you "need" is very high if you never want to swap things in and out of memory.

  3. I think my cpu will be a bottleneck. I’ve an i7 6700k, running at 4ghz with 32gb DDR 2400mhz. I believe I do have an 850watt psu, but it is a pretty cheap one. A full system upgrade is long overdue.

     

    I’ve been ready to pounce for ages, but the manufacturers seem to be dragging their heels forever. AMD, with the Big Navi, and new Ryzen, and nVidia with their 30xx series. I, and many others, have been reluctant to bite now with all of this stuff ready to drop at any moment.

     

    You can OC your 6700k to 4.6 easily. Then you're only about 400 Mhz away from the single core performance of a top of the line Intel CPU considering IPC hasn't really increased since Skylake. I don't see any compelling reason to upgrade from my 6700k for that reason.

  4. One odd thing I noticed is the draw distance doesn't seem to scale the same as for the other maps. Medium in Syria is like Low for Caucasus. Could see the buildings growing in front of me just a few hundred feet away. Also the tree slider doesn't do anything. After moving up to high I got similar performance to Persian Gulf. Able to maintain 40 fps except when near the ground near densely populated areas.

  5. Okay, I ... I don't think I'm going to ever touch that Repair tool ever again. I can't, I've got pictures of family, of vacations, and home videos from VHS...I can't risk all that by using a DCS tool, what the heck!

     

    Dude, buy some cloud storage NOW. Even backing up to another hard drive is not good enough, like if you have a fire, for example, unless you store it at another physical location.

  6. So, what do we think are good settings here in terms of use/don’t use mod, mod antialiasing plus DCS MSAA mask or no mod AA etc.

    I can’t get my head around this! I remain very disappointed with the VR performance in this patch.

     

    No MSAA will always give better performance, so turn it off completely if you want best FPS. Bloom is a lighting effect: https://en.wikipedia.org/wiki/Bloom_(shader_effect)

     

    As it's an extra effect, turning it off can only help performance.

  7. MSAA mask is probably the same feature as in Kegetys' VR mod. It only performs MSAA on a circle in front of you whose radius is determined by the mask size. That way you don't bother applying anti-aliasing to the edges of your vision where you can't notice it anyways.

     

    edit: I haven't tried the new update yet, but if it's the same thing above it's easy to see for yourself. Set a small mask, like 0.3 or something, and if you look off-center, you should see how the aliasing gets visibly worse past a certain boundary.

  8. Wow, poll nearly unanimously says what we've all been saying: sell the throttle separately! I'm sure you make a fine joystick but many have already invested a lot in their existing sticks. Whereas I don't think anyone else makes such a throttle anywhere near your price point. And VKB is supposedly coming out with something this year (although cheaper) so now would be the time to beat them to the punch.

  9. Can you brake using two brakes? example in the landing? how work?

     

    Yes, but you don't get true axis control. If you hold the brake button and the rudders are neutral, the virtual axis will slowly increase in input, which gives you a kind of pseudo-axis: longer you hold the button, the greater the brake strength. Then if you move the rudders while holding the button, you get a true axis for each individual brake.

  10. Thanks for the kind words.

     

    If I understand you correctly there are two main modes: Hold & Toggle. I think it would be more intuitive if there was an option to switch between those modes.

    I'd prefer to keep it as is because I personally use both modes during flight. When I want to fly with loose cyclic for an extended period of time I use toggle. For quick trim changes, I use Hold. If you want to disable one of the options, just set the button to 32. This should work until someone tries to use the software with a 32 button joystick. :megalol:

     

    But I have still one question: what is the second drop-down-box (left next to the "SimFFB"-text) for?

    It selects which Joystick POV hat is used for progressive trimming. This is useful for people who have modded a different grip onto their joystick. If you are using the original grip for your joystick, just keep it set to that.

     

     

    1. the assigned "init dinput" key doesn't save correctly into the config, so it's always "RightControl" when simFFB starts
    2. simFFB sometimes quits without any error after selecting the menu item "Options"/"Init DirectInput"

    And I have also some feature requests:

    (1) Hmm, I've never noticed this. I just did some testing and it only seems to happen with the last six possible keys (from Numlock to RightControl). Can you confirm that if you select hotkey F7, it saves properly? I'll have to take a look and see what's causing it.

    (2) I cannot reproduce this personally :( How often does it happen? I'll see if I can add some error checking code to the Init function.

     

    1. it would be great if you could add some additional key combination options for the "init dinput" hotkey (i. e. to allow the combination of LCtrl+LAlt+F)?
    2. can you add a confirmation after successful "Init DirectInput" (i. e. in a status-bar)?
    3. maybe you can add an icon to the application as well (I've created some examples, see attachment)?

     

    These should be do-able.

  11. Hello all,

     

    I'm the simFFB dev. Sorry, don't speak German, but hopefully I can help you understand what those boxes are.

     

    These are button assignments. They only work in the instant trimmer mode. The labels above indicate the function:

     

    Hold: Spring Force 2/Damper Force 2/Friction Force 2 are active when this button is held. If you set Spring Force 2 to zero, it acts like your typical trimmer in a helo: hold the button to remove spring force, move it to where you want, and when you let go the stick will stay where you last left it.

     

    Toggle: Similar to above but it toggles between the Spring Force/Damper Force/Friction Force 1 and 2. If you set Spring Force 2 to zero, it works like turning force trim on and off in a helo. Only difference is it does not re-center the stick when you toggle like in the Huey module. I added this option because I found it more convenient to trim without having to hold the button all the time.

     

    Center: This button will center the joystick.

     

    I'll add some documentation to the project page on this.

  12. Yeah, look at how much performance VR needs and why the majority of VR-Games usually opt for comic book graphics, confined spaces. See why the upcoming mother of all "Flight Simulators" built from scratch, does not incorporate VR in release... maybe some people need to check their expectations when venturing into unknown territories?

    The current state of the art tech allows for either the immersion of Virtual Reality ( "I am inside this Cockpit" ) OR the 4K full blown stunning realistic graphics on a 2D Screen. With the render distances and object details we have in DCS on the current graphics engine you can't have both.

    When you read through the roadmap, you notice, the plan to further optimize for VR and to replace/update the core graphics engine. But this will not happen overnight, and I am sure, there will always be a difference in performance between 2D and VR for a veeeery long time. So you need to adapt, or keep complaining. Only, complaining won't change anything...

     

    This argument falls apart when there is another combat flight sim with MUCH better VR performance. Also, MSFS didn't have VR at the outset because the developers seemed to have no clue how important it is to simmers. They looked at VR adoption rates, and extrapolated, which was wrong! The evidence for this is when they were first asked about it, one of the devs laughed and said "maybe later". Then after the chorus of "No VR, no buy" it suddenly became a priority. So it wasn't for technical reasons, but because they had underestimated the demand.

×
×
  • Create New...