Jump to content

Free Death Camera


Recommended Posts

8 minutes ago, Koolguy11 said:

Does you have to be on patch 1.10?

This mod uses some RVAs which may be different in other versions of game. I got some of these directly from f4se's source code and others via cheat engine. If you want this to work under older versions you need to change those RVAs(most stored in ini) and rebuild the plugin.

Link to comment
7 minutes ago, gp160 said:

This mod uses some RVAs which may be different in other versions of game. I got some of these directly from f4se's source code and others via cheat engine. If you want this to work under older versions you need to change those RVAs(most stored in ini) and rebuild the plugin.

That's a shame. I have yet to update due to ~creation club~

Link to comment
10 hours ago, fanjo said:

I've installed this for skyrim as well and never been able to get it to work. It's like it gets deleted out of my files or something cause I can never find it after I start up the game.

Check your antivirus software.

Link to comment
  • 2 weeks later...
17 hours ago, firepaw74 said:

I'm trying to run this plugin but it gives following error at the start of the game: "There was a problem starting D:\...\Data\F4SE\Plugins\PostmortemTFC.dll,EntryPoint The specified module could not be found"

After that game starts as normal but your mod is not working.

Strange. It seems your rundll32 treats ,EntryPoint as a part of the file name. What is the command line of the rundll32 process?

Link to comment
49 minutes ago, firepaw74 said:

How to check that?

Run fo4 until that error notification appears, don't close it.

You can check that using taskmgr. In win10 for example, goto Process or Details tab and right click on the column headers. You can config which info items to display.

If you have powershell, run the following command using the Win+R dialog box.

    powershell -noexit -command wmiobject win32_process -Filter \"name='rundll32.exe' or name='Fallout4.exe'\"|select commandline

Link to comment
6 hours ago, gp160 said:

Run fo4 until that error notification appears, don't close it.

You can check that using taskmgr. In win10 for example, goto Process or Details tab and right click on the column headers. You can config which info items to display.

If you have powershell, run the following command using the Win+R dialog box.

    powershell -noexit -command wmiobject win32_process -Filter \"name='rundll32.exe' or name='Fallout4.exe'\"|select commandline

Ok, command line looks like that

"rundll32.exe" "D:\...\f4se\plugins\PostmortemTFC.dll,EntryPoint" "1740" "00007FF751300000"

Link to comment
12 hours ago, firepaw74 said:

Ok, command line looks like that

"rundll32.exe" "D:\...\f4se\plugins\PostmortemTFC.dll,EntryPoint" "1740" "00007FF751300000"

This is odd. The command line should be rundll32.exe "D:\...\f4se\plugins\PostmortemTFC.dll",EntryPoint 1740 00007FF751300000, whose construction is explicitly specified in the code. It looks like something is altering the command line used to create rundll32 process. Please try this to see if anything changes, and I would like to know your Windows version and whether you are using antivirus/mod organizer or not.

PostmortemTFC.7z

Link to comment
5 hours ago, gp160 said:

This is odd. The command line should be rundll32.exe "D:\...\f4se\plugins\PostmortemTFC.dll",EntryPoint 1740 00007FF751300000, whose construction is explicitly specified in the code. It looks like something is altering the command line used to create rundll32 process. Please try this to see if anything changes, and I would like to know your Windows version and whether you are using antivirus/mod organizer or not.

PostmortemTFC.7z

That version works like a charm! I'm using Windows 10 Pro x64 and latest ModOrganizer.

Link to comment
12 hours ago, firepaw74 said:

That version works like a charm! I'm using Windows 10 Pro x64 and latest ModOrganizer.

Well then. I guess the cause is ModOrganizer's virtual file system. Last time I checked, Microsoft's documentation doesn't mention any modification to command line like that. I'm going to move it to the main file.

Link to comment

Just dying in general, doesn't matter if I'm in an interior or exterior.

At first, I thought it was maybe cause I was zoomed in, but I stopped zooming in with weapons and that still happens.

Maybe it's because I'm using a different FOV? Let me experiment and get back to you.

Whatever it is, it's quite frequent. About a 50% rate of it happening.

 

EDIT: Happens when I'm in first person, but does not happen in third person.

Link to comment
On 2018/1/2 at 11:40 AM, Contagious Waffles said:

Just dying in general, doesn't matter if I'm in an interior or exterior.

At first, I thought it was maybe cause I was zoomed in, but I stopped zooming in with weapons and that still happens.

Maybe it's because I'm using a different FOV? Let me experiment and get back to you.

Whatever it is, it's quite frequent. About a 50% rate of it happening.

 

EDIT: Happens when I'm in first person, but does not happen in third person.

This is not happening to me. Does it recur if you goto first person then call player.kill? What camera mods are you using?

Link to comment

Hmmm, now that's interesting. 

Player.kill never triggers the bug. Only when dying 'normally' to explosions and guns.

The only mods that affect cameras are the No Blur, No DOF, Realtime Death mods.

I'll try knocking off mods one by one to see which ones are the cause.

 

EDIT: I think I got a good way to reproduce.

It happens 100% of the time when leaving the Pipboy menu.

You have to die while you're lowering it.

Link to comment
  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...