Search Results for 'The Thing'

[dirtythekid]

I have found a way to disable shadows if anyone is interested.

Load your text editor (I use Notepad++) and open the file
%localappdata%\techland\cojgunslinger\out\Settings\Video.scr
and edit the following settings:

Shadows(“Low”)
ShadowMapSize(1)
SpotShadowMapSize(1)

This will shrink the shadows to nothing, effectively disabling them. You can also add this line to modify the FOV:

ForcedHorzFov(110)

After you’re done editing the settings to your liking, right click the file in Windows Explorer, go to Properties, and check the Read-only box so the game doesn’t restore it’s default values. I’m not sure if it does this or not, but it’s usually a good practice. I don’t know of a way to disable the fancy border effect in the game, but this should be a good starting point to make it playable.

[Ralf]

Still OK in the campaign, but not in multiplayer. Odd, thanks for the heads-up. I’ll take a closer look next week.

Luckily there is a simple workaround for now: playing with a gamepad, only thing that doesn’t work is using a mouse. Apparently in multiplayer the game now dislikes two mice being used at the same time (the real one and the simulated head tracking mouse). With a gamepad it’s as silky smooth as ever.

[Ralf]

I’ll take a look at it. Head tracking is mouse emulation based though in BF1, so there isn’t really anything that could break. One thing you could check is whether raw input is enabled in the game’s options. The DirectVR optimizer is supposed to take care of that normally.

[Ralf]

Short update: if all goes well you can expect a fully featured profile shortly after release. Spent yesterday’s beta time refining the profile and memory scanner settings, so it’s *almost* finished. Unfortunatly no more beta, the finishing touches have to wait until after relase.

Fingers crossed that there won’t be a day one patch that breaks everything.

[Mesenzio]

Thank you again. In the end I use VorpX mostly with dgvoodoo, so it’s great to have someone looking into that.

However, I probably didn’t get (or forgot) something. The problem with d3d9.dll is for games that are natively in DirectX9 only? If I am playing a, let’s say, DirectX 7 game, all this does not apply.

[Ralf]

Please make sure that the “Do not optimize game settings” option in the config app is not checked.

Unless you checked this box, vorpX should configure everything automatically.

[Xain]

Just checked my macros, everything works. Some people said something about it not working correctly when copied from here so I’ma see if putting it in this code tag will do anything differently. I’ll also put down more useful macros I use for more immersion.

NOTE: IF IT DOES NOT WORK. Copy the following lines of code to notepad and make sure everything is on one line with no forced line breaks. Run over into a new line is all right but there is a chance this website is formatting it weird and making it not work in WoW.
Code to make the FoV wider, to turn if off replace -150 with 0 and 150 with 0.
/run WorldFrame:SetPoint("TOPLEFT", 0, -150) WorldFrame:SetPoint("BOTTOMRIGHT", 0, 150)

Turns off floating text for healing done to target, to turn it back on replace 0 with 1
/console floatingCombatTextCombatHealing 0

Turns off floating text for damage done to target, to turn it back on replace 0 with 1
/console floatingCombatTextCombatDamage 0

Turns on the action camera, to turn it back off replace full with off
/console ActionCam full

[Ralf]

Usually I don’t really talk about what is going on development wise, but this is worth mentioning:

Some of you may have been wondering why the f*** there aren’t any recent Frostbite engine games (almost all newer EA titles) with Geometry 3D. Well, the simple and not exactly flattering reason is that for a long time I couldn’t come up with a G3D implementation for a rarely used Direct3D 11.1 feature this engine uses extensively. At least not without completely destroying performance.

Until today.

Not only does it work beautifully now, it’s also faster than I could have hoped for. Overall less than 50% G3D performance impact without rendering to a headset, so probably only a little bit more than 50% eventually.

So far only one game has been tested (Mass Effect: Andromeda), but if nothing unforeseen happens, this finally should allow G3D for most newer Frostbite games including Battlefield 4 and newer, SW: Battlefront, Dragon Age: Inquisition etc. Stay tuned.

[RJK_]

I think a have the gunslinger on stock so i can have a look at it, for now you can open your shader page (STRG+END) and step through the different shaders, leave the top left shader option to “hide”. Once you came across hat shader (shadows will disappear completely) , make this shader “active” and try different settings. Change from normal to shadow ect. If nothing helps just disable it (“dont render”). This way you will have no shadows at all, but in some cases thats the only way to handle this.

[RJK_]

If you do not hexedit the games exe and rename the dll vorpX will hook into the game without the DX9 wrapper and probably without 3D. Though the description above is only needed for some rare games that explicitely look for dlls in the windows folders (example: Spellforce 1)

For a normal shader 1.x DX9 game (that looks into the game folder) you only need to follow these 3 steps:

– Put d3d9.dll into game folder and configure DGVoodoo2 as usual
– Rename d3d9.dll to v3d9.dll
– Hexedit games exe , change each “d3d9.dll” of the exe into “v3d9.dll”

When you see both, the DGVoodoo2 logo in the right bottom corner and the vorpX logo in the middle, you will know that everything has properly been setup.

I assume in a later VorpX version the d3d9.dll search will may be removed when using DGVoodoo2, so the workaround becomes otious.

[Alyosya]

Does anyone know if this still works in BfA? Nothing happens when I enter the code in the chatbox in WoW

[Ralf]

Nothing below is final. The game’s release version might or might not work.

That said, in today’s beta session everything worked more or less as it should ideally, which means G3D, DirectVR head tracking and FOV. Still quite a bit of work to do, but provided they don’t decide to disallow hooking into the game in the end, the final profile will be similar to Fallout 4 feature wise. The DirectVR memory scanner may be considered cheating though, only time will tell how they handle that. So to be on the safe side, deactivate it.

Requires a fast machine + reduced graphics detail for G3D, medium detail for a GTX 1080Ti seems OK. The game world is quite a bit more detailed than Fallout 4 and thus more demanding. Z3D looks good, so mid-range GPUs will work too.

If all goes well, an official profile will be made available at or shortly after release.

Just in case someone overlooked it above: :)

Nothing above is final. The game’s release version might or might not work.

[onetoo]

Last I tried, Witcher 3 has a terrible first person implementation. It’s tied to the 3rd person camera, so you can’t turn smoothly with all the camera tricks. Idk if things changed, but the mod devs didn’t seem to have any solutions when I spoke to them several months back. I haven’t seen any recent updates over at nexusmods.

[Adil3tr]

I’m using Kapersky but turning it off doesn’t change anything.

[Ralf]

Never heard of anything like this, sorry. Try to run the games windowed then, maybe that makes a difference. Just a guess, of course, can’t really recommend anything more specific.