grumdark

Forum Replies Created

Viewing 15 posts - 136 through 150 (of 171 total)
  • Author
    Posts
  • in reply to: Bug and problems with games in vorpx #87964
    grumdark
    Participant

    Ok Ralf,I understand that,but the problem of UI/GUI is only one of several problems.

    Anyway, when I write (UI scale / depth)is just an example,I refer to the HUD is not visibly represented in dk2.
    If to achieve this,use an alternative method such as at the entry tweak optimizer u other,I also served well.(This is just an example…)

    Also I made sure to appoint in the aforementioned games,titles that are operating today in oculus dk1/dk2(with visible hud)with other current or former 3d driver.
    As this is the forum vorpx and not that of other drivers, at first I prefer not to be naming them, what I mean is that you can change the HUD safely (except possibly two or three titles mentioned)
    I checked,but prefer to use vorpx for other extra features.

    Edge peek mode is a good choice for a specific time,but when a player has to observe a minimap for example, this is not the most appropriate, whenever possible change this.

    Cinema virtual mode, I think so too, when no other option or choice, use thus less permissive games and also for third person games, but as I say, the games name most are games where and check before it possible (except two or three).
    For me, the good part of the 3d drivers is to enjoy some titles in first person view,in virtual reality,at least those that are possible,as I have mentioned.
    Cinema virtual mode,It is only a complement to my.

    Apart from this, problems with Metro Last Light dx9,fallout 3/nv,and shadows in Far Cry 3…are separate issues,which could also see that there are solutions to this day working,but I can not implement my own hands vorpx in all cases.
    For my limited knowledge, and parts of vorpx where I have no access.

    The part that I do not like, is the knowledge that vorpx is the best tool, better than many people think, but not having a functional profiles or securities in cases where this if possible.(for vr mode)
    Forcing just have to use another driver … for just a few simple changes.
    please,sorry my english.

    in reply to: GtaV – Rift init failed? #87953
    grumdark
    Participant

    GTA 5:
    ¿Will this testing using a pirated copy of GTA 5?
    I have understood that it is a common fault with GTA5 in downloaded versions.
    Original steam version works correctly for me.

    Far cry 4:
    I do not work properly,3d z buffer does not work properly for me in this case.

    in reply to: Edge Peek Not Functioning #87930
    grumdark
    Participant

    You can check and change associated key to this function in the settings vorpx,external menu:
    Ingame key binding section, second option, edge peek,(press desired key)
    remember to save the changes :)

    Elder scroll online,advice extra:I take this opportunity to recommend that:
    Preset sweetfx near perfection 2.0, is injected through radeon pro 1.5 or 1.4 for Windows 8/8.1…This preset get a lot more beautiful game!
    Greetings.

    in reply to: Battlefield 4 #87903
    grumdark
    Participant

    I use a very similar configuration,also often use options flawless widescreen program,to improve some games.

    Add before step 1,apply corresponding entry Battlefield 4 in optimizer game setting in vorpx(external config)this fixes HUD during the campaign to represent correctly.
    Enable black smear:On
    I would also add another second point,NEVER APPLY MSAA filter in 3d z buffer,because it causes the loss of 3d z-modes.

    in reply to: Outlast won’t start #87737
    grumdark
    Participant

    I think the first mistake dk1 possibly get right now … dk1 has too many shortcomings.
    Apart from this,direct mode oculus … never works with dk1,not even to for games /demos native,so it appeared later on dk2.
    Similarly to date,all 3d driver vorpx or other existing,only work in extended mode. (clone for dk1)To this day or some exception.

    I remember that there is a version vorpx more suitable for use with dk1…but you may have to contact support.

    grumdark
    Participant

    CylonSurfer,thank you very much for this mod.
    I’m testing it right now (in singleplayer mode) and it works quite well.
    In addition to solving visible minimap, you have made it possible to read subtitles, and this was very important for the language in my country and others languajes. Simply fantastic.

    For me, singleplayer is now fully playable thanks to you.
    I wish I had a chance to 3D geometry (soon future) … this would be perfect for me;) sorry my english :P
    Greetings and 100% grateful.

    grumdark
    Participant

    You should contact vorpx in support |at| vorpx com so they can provide support for this issue.

    in reply to: Metro 2033 crash at start #87651
    grumdark
    Participant

    FOV maximum value allowed by the game (Metro 2033) is 90.
    One point more, you could reset the value.

    If that was not enough to 90, you can increase a little in geometry,using the option 3d fov enhancement+Adjust the zoom joined this avoiding looking edges.

    Example:
    This could be possible with the optimizer vorpx games (external configuration)
    But if it fails for some reason …
    C:\Users\”your user”\AppData\Local\4A Games\Metro 2033
    Open user.cfg modify Sick_fov:90
    r_api:0 (force dx9)save changes.

    Menu vorpx ingame:
    3d reconstruction:Geometry
    3d fov enhancement:0.30 (not much more,”may” produce glitch in some games)
    Separation (3d strength):2.90
    Fix chromatic aberration:ON.
    Fix black smear:ON.
    Aspect ratio correction:Pixel 1:1
    Image zoom:0.79
    2d fov enhancement:0.00

    This is for normal version,redux geometry does not work.
    regards.

    in reply to: Outlast – Everythings way to big #87630
    grumdark
    Participant

    This is my configuration,It could serve as a possible help.
    English is not my native language, sorry.

    Crysis 1:
    Crysis 1,uses a different model for hands/weapon and you can not scale its size for now.In some games, weapon fov(or similar)can help to be(scalable with separation 3d) after,in menu vorpx, but it is not the case of crysis.

    I use this setting to crysis:
    Apply optimizer vorpx entry.
    Force dx9.
    Make 1920×1080 resolution, window mode off, motion blur off
    Low shadows and any other possible graphic options(recommend for better performance)

    Open console ingame(push key º)and enter:
    con_restricted = 0
    cl_fov 90
    You can enter more fov from play,but not recommended for my,cause fisheye effect.
    However,we introduce a little more in the ingame menu fov vorpx,(3d fov enhancement)for several reasons.

    vorpx ingame menu,page 1:
    Cinema virtual mode:Off
    3d reconstruction:Geometry (required force dx9 in this game for now)
    3d fov enhancement: 0.45 (help with more fov,and better fov support in the interior vehicles)
    Separation (3d strength):1.30 (this changed world scale,I always prefer to do so after the fov adjustment,and zoom)
    Camera height modifier:1.90 to me (change camera height,help with aiming,height depending player,useful with positional tracking on)
    Focal offsett:0.03

    page 2:
    Fix chromatic aberration:On
    Fix black smear:ON
    Game ui / scale:0.42 (scale and resize HUD and menus in geometry)
    Game ui / depth:0.85
    Aspect ratio correction:Pixel 1:1
    Image zoom:0.85
    2d fov enhancement:0.00
    vignette scale:1.00

    page 3:
    optional positional tracking:On/off
    Save changes.

    Possible issues: large hands and arms.
    Only possible “help” at the moment,
    console, r_DrawNearFov 50 or less, notably hides the length of the weapon,in normal aiming.
    weapon not correct scale, but more hidden inside the camera.
    Sorry my english.
    Regards.

    in reply to: Outlast – Everythings way to big #87625
    grumdark
    Participant

    If it’s any help, my settings to outlast with vorpx is this:
    Documents \ My Games \ Outlast \ OLGame \ Config
    Open file OLGame.ini change this values:
    DefaultFOV: 120.0
    RunningFov: 120.0
    CamcorderNVMaxFov: 120.0 (vorpx unchanged this automatically in optimizer)
    CamcorderMaxFov: 120.0 (vorpx unchanged this automatically in optimizer)
    Close and save changes.
    It is important because these tweaks,vorpx unchanged all this from the optimizer.

    Open OLEngine.ini
    Change all bSmoothFrameRate: at FALSE
    vorpx not change all these automatically in the optimizer,and produce loss of fps.

    menu vorpx ingame,page 1:
    Virtual cinema mode:Off
    3d reconstruction:Geometry
    Separation-(3d strength):1.40 (this modify world scale,need fov game 120 and fovcam 120,for this correct complement)
    3d fov enhancement:0.00
    Focal offset:0.04

    page 2:
    Fix chromatic aberration:On
    Fix black smear:On (this correct blacksmear in display,very important in outlast)
    Aspect ratio correction:Pixel 1:1
    Image zoom:0.77-0.78 aprox.
    2d fov:0.00

    page 3:
    positional tracking (optional):On/OFF
    I recommend graduating sensitivity aspect direct in the game(mouse sensibility) for best motion tracking.
    because too low in vorpx tracking sensitivity can cause latency ;)
    sorry my english.
    Regards.

    in reply to: Trojan found in vorpConfig.exe #81766
    grumdark
    Participant

    I happened the same thing yesterday.
    Windows defender, repeatedly broke the vorpx program, and after several relocations.
    After disabling antivirus and clean reinstallation of vorpx today seems to work “well”,.
    at least for now.
    Now, I’m not sure my antivirus enabled, for fear of breaking it again.

    in reply to: Metro 2033 not displaying on oculus #81556
    grumdark
    Participant

    I made a test and works well,with fov 90 v + 0.30-3d enhancement fov (geometry) + zoom setting.
    I just missed the option hud scale, but very playable after some settings.

    in reply to: Head tracking stutter in edge peek or virtual cinema #81022
    grumdark
    Participant

    Probably the modification of parameters of the game, for example
    Smooth Frame – in false, and other tweak + vSync adaptative
    ¿Could this solve or improve the experience in the virtual room just as it does standard vr?

    in reply to: Fallout: New Vegas – pip boy issue #80900
    grumdark
    Participant

    ok,I have information here, possibly useful…

    Apparently the mod enhanced camera, could solve any of these problems.

    In a external forum user ghettocat2007 says:
    You need to make a small change to the NVSE_EnhancedCamera ini file (located in Data, NVSE, Plugins,)
    You will see the below
    Can be set to a high value (e.g. 15.0) to disable zooming in during dialog
    Unlike the fDlgFocus setting in Fallout.ini, this does not affect VATS
    fDlgFocusOverride=1.0
    Change the value to 16.0
    ta da no more zooming

    PD:The message seems to be a fallout new vegas addressed,but I think it was a good idea to test.

    sorry my English,greetings.

    in reply to: I reinstalled windovs as I enter the code? #80857
    grumdark
    Participant

    No, no need to buy new code…
    You need to send a mail to get new key.

Viewing 15 posts - 136 through 150 (of 171 total)

Spread the word. Share this post!