[REL] Fm_NewInteriors v1.0...

[Aces]

Hi folks,

Try this, it's the combined sh3.sdl from Lifeboats&Debris v4, FM's New Interior and HanSolo's Animated sub pens. JSGME compat, install AFTER these mods.

I'm at work and found it on my portable hard disk drive.

http://www.filefront.com/15738405/Co...NI+SubPens.rar

Thanks to all these mod authors for their great work.

Any problems let me know, I have the file at home as well just incase it shopuld differ but I'm 99.9% sure that this one is the one I'm using.

Best Regards

Aces

[JohnnyBlaze]

This mod looks great!

I think I have a small problem. When ever I click the floor of the sub it throws me to the engine room.

And I would also like to enable the free camera movement in the control room by default. What values should I edit in the cameras.dat to achieve this?

Sorry if this has been asked before. Couldnt find the answer.

Thanks

-Johnny

[JCWolf]

Originally Posted by JohnnyBlaze

This mod looks great!

I think I have a small problem. When ever I click the floor of the sub it throws me to the engine room.

And I would also like to enable the free camera movement in the control room by default. What values should I edit in the cameras.dat to achieve this?

Sorry if this has been asked before. Couldnt find the answer.

Thanks

-Johnny

Do Not use the old FM floor click, Free cam Is back to the stock keys
that are Shift + F2.

[Reece]

I know I keep saying this but for new readers please be aware that changing the boot.ini file with the command switches /3GB /USERVA=xxxx may cause problems, I found that while doing this and patching the sh3.exe file SHIII itself worked great! BUT the changes made to the boot.ini file caused major problems to other applications, games etc, mostly stuttering and lockups, I tested this thoroughly, so be aware just in case you find some other application not working properly it could be this. Some people seem to have no problems while other have a lot, don't know why, my system is XP Pro with SP3, 4Gb ram AMD CPU with ATI GPU.

[Anvart]

Originally Posted by Reece

I know I keep saying this but for new readers please be aware that changing the boot.ini file with the command switches /3GB /USERVA=xxxx may cause problems, I found that while doing this and patching the sh3.exe file SHIII itself worked great! BUT the changes made to the boot.ini file caused major problems to other applications, games etc, mostly stuttering and lockups, I tested this thoroughly, so be aware just in case you find some other application not working properly it could be this. Some people seem to have no problems while other have a lot, don't know why, my system is XP Pro with SP3, 4Gb ram AMD CPU with ATI GPU.

I have WinXP Pro SP3 32-bit, 3 GB RAM (better compromise for this), ATI GPU, Intel CPU, ASUS mobo, pagefile.sys not less than 4096 MB... and have no problems... i use it more then 3 years (may be 5)...
I use (try) many programs 3D art, 2D art, CAD, games and so on...
... and if i write value "/3GB /USERVA=xxxx" correctly i have no problems...
i always wrote switcher manualy in boot.ini...
...
Except discussed problem (switcher, patcher of *.exe & *.dlll) there is still an adjustment of OS (System Cache as example and so on)... only set of all parametres (switcher, patcher and adjustment of OS) will yield necessary result...

P.S.
There is no sense to discuss on this theme... Everyone should try independently...

[Captain Nemo]

Originally Posted by Reece

I know I keep saying this but for new readers please be aware that changing the boot.ini file with the command switches /3GB /USERVA=xxxx may cause problems, I found that while doing this and patching the sh3.exe file SHIII itself worked great! BUT the changes made to the boot.ini file caused major problems to other applications, games etc, mostly stuttering and lockups, I tested this thoroughly, so be aware just in case you find some other application not working properly it could be this. Some people seem to have no problems while other have a lot, don't know why, my system is XP Pro with SP3, 4Gb ram AMD CPU with ATI GPU.

From what I have read Reece is correct. I'm no computer expert but from what I have read the switch has nothing to do with how much RAM you have installed, for example you could use the switch on a machine with only 1GB of physical RAM installed. It's all to do with virtual memory which XP 32 bit can have a maximum of 4GB. On a standard setup XP allocates up to 2GB of VM to applications and up to 2 GB to the OS. The 3GB switch gives 3GB to applications and only 1GB to the OS. So theoretically, if some hardware on your machine wants to push the OS side of things beyond that 1GB, problems will arise. Also, some applications don't like the idea of more than 2GB of VM so issues with those may arise. On the other hand if your OS and drivers can live happily within that 1GB then you should be problem free. I suppose the workaround is to have the option at boot up to select the 3GB switch if your going to play SH3 (assuming your video drivers can live within 1GB with the OS) or to go with a standard boot up if you are using hardware or software that is affected by the switch.

Nemo

[Damo]

I applied the .exe 4GB patch from the LSH team and selected my /3GB boot .ini at startup and I've actually managed to load a new patrol of my existing career without any crashes. I'm currently making my way down the Kiel Canal without any issues except I did notice a wee bit of stuttering on first load in the harbour, this soon subsided though. FPS from engine room facing command room is no less than 36fps.

I'm not counting all my chickens yet as I'm going to continue the patrol and then try a few mid ocean saves, I still have a fear that I'll suffer the kernel.dll error upon reloading attempts. I know my system is pretty stable as I've never experienced any CTD's from the 3D, only on loading.

XP 32bit (/3GB, USERVA=2600 boot.ini for SH3 sessions only)
Athlon 64 x2 5200+ O/C @ 3.1ghz
2x 1GB Crucial Ballistix 800mhz RAM.
Asus M2a-VM Motherboard
Nvidia GeForce 9500GT (512mb) (Temporary solution after last card went pop)
Using Nhancer and Gamebooster, loaded patrol directly after reboot to minimize memory usage.

If I experience any more crashes, I'll post, if not, I'll be too busy....

[Reece]

Originally Posted by Captain Nemo

From what I have read Reece is correct. I'm no computer expert but from what I have read the switch has nothing to do with how much RAM you have installed, for example you could use the switch on a machine with only 1GB of physical RAM installed. It's all to do with virtual memory which XP 32 bit can have a maximum of 4GB. On a standard setup XP allocates up to 2GB of VM to applications and up to 2 GB to the OS. The 3GB switch gives 3GB to applications and only 1GB to the OS. So theoretically, if some hardware on your machine wants to push the OS side of things beyond that 1GB, problems will arise. Also, some applications don't like the idea of more than 2GB of VM so issues with those may arise. On the other hand if your OS and drivers can live happily within that 1GB then you should be problem free. I suppose the workaround is to have the option at boot up to select the 3GB switch if your going to play SH3 (assuming your video drivers can live within 1GB with the OS) or to go with a standard boot up if you are using hardware or software that is affected by the switch.

Nemo

For more information:

XP 32 can only use a memory address space of 4GB. It then "RESERVES" addresses in that table for loading every little bit and piece in your computer (Devices and so on like a SATA controller... They all need an "address RANGE" to exist in so that the Os can communicate with it) leaving 3.25GB (3402084 in task manager) of RAM free for the system. XP loads up and uses some of that. Typically after XP loads into memory you will have about 2.9GB free. If you have 4GB physically installed that is.

The more RAM on the video card, the less you have free to the OS is the concept because the OS needs to reserve the address space for the RAM on the video card. I have a 512Mb card and I have XP SP3 reporting 3.25GB free. Theory is that if it were 1GB card I would have less reported available to the Os because the addresses for that 1GB will need to be reserved.

If you have a 2GB PC with a 1GB Card and a 32bit XP install. You likely have very little left for the FSX app to run in.

http://www.dansdata.com/askdan00015.htm

"a note about the /3GB, /4GT and /PAE Windows boot.ini switches, too, because they often come up when people are talking about 4Gb-plus Windows PCs. They are all useless to you. You do not want them. /3GB and /4GT are config settings for different versions of Windows that tell the operating system to change the partitioning of the 4Gb 32-bit address space so that applications can use 3Gb and the OS kernel only 1Gb, as opposed to the standard 2Gb-each arrangement. They don't help at all with the 3Gb barrier, and most applications don't even notice them, so desktop users lose kernel memory space (and system performance) for no actual gain at all. The /PAE boot.ini switch, on NT-descended Windows flavours, activates the Physical Address Extension mode that's existed in every PC CPU since the Pentium Pro. PAE can also be enabled by the /NoExecute entry in boot.ini, which turns on support for the NX bit which you probably also don't actually want.

[Desga]

...To all people ...do you know the way to eliminate the food ??
I open the NSS_Uboat7_CR.dat with s3editor and I see this..






I edited with red line the object that I think i must eliminate are those correct?

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

is it possible that with "Conning Tower Hatch open" installed you see inside the door is open but closed from the outside ?

[Castout]

Umm the exe fix fixed the CTD when using this mod it seems

[Damo]

Originally Posted by Castout

Umm the exe fix fixed the CTD when using this mod it seems

It has for me, just loaded a mid patrol save and it's A-OK. I'm running some pretty heavy mods too so I'm well happy. Just waiting for the sound fix now (deleted the .sdl file), and I'd like the floor click to engine room removed, just leaving Shift-E for engine room access along with Shift F2 freecam. I understand the dive angles will screw things up with the original OH 3.09 freecam if you travel too far back or forward while in a dive or surfacing, throwing you through the floor or ceiling, right? Having the floor click just makes things cumbersome.

Is there a way I can deactivate it myself? I have S3D.

[JohnnyBlaze]

Originally Posted by JCWolf

Free cam Is back to the stock keys
that are Shift + F2.

Hi JCWolf!

Yes I am aware that the freecam is back to the stock keys. And that's my problem here. Dont want to press those keys everytime I want to move around in the sub.
What I would like to know is what adjustments I have to make in the cameras.dat to achieve an automatic freecam movement that would always stay in the freecam movement?

I hope I'm making myself clear enough

Originally Posted by JCWolf

Do Not use the old FM floor click,

Are you saying that it cannot be fixed?
I guess I have to be more careful with my trigger happy finger

Thanks

-Johnny

[flakmonkey]

You can add freemove to any camera you wish, just add a freemove node via s3d to the camera in question in cameras.dat (just look at any existing free moving camera`s node structure to see how its done).
I would however recommend disabling the camera sway since youd just end up with the same free move camera bug that affected the beta version.


+found any easter eggs yet???

[Damo]

@ Johnny

I think the extended length of the 3d interior makes the use of the destabilized freecam untenable, in that as you dive and surface, the camera position pivots on the central point (the point in the control room by the CT ladder. Therefore, if you initiate a dive and you're at the extreme ends of the interior, it will pivot the boat and push you either through the floor or ceiling, which has been known to cause crashes.

It was fine when using just the OH 3.09 as the interior wasn't as long and the dive angles could be contained to keep you inside the boundaries of the 3d world (interior), but to have the same effect in this mod, you'd have to reduce the dive angles to an almost unnoticeable point. Even if you did manage to edit in a freecam yourself, you'd not be able to dive or surface without being situated in a central position (in the CR) or you'd be pushed out of the interior into the blackness beyond, maybe causing a crash, at best freezing your game.

I doubt this will be solved.

[JohnnyBlaze]

Thanks guys for the info

Okay I will attempt to add a new node to the cameras.dat. Allthought my experience with S3D is limited so far to only fixing the periscope alignments, but I'll see what I can do.

Thanks for the heads up tho.
I will try and stay in the CR when at deep angles.

@Flakmonkey
Sorry only tested the mod once so no easter eggs yet to come by

-Johnny