Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - plug_nickel

Pages: [1] 2
General Discussion / Re: BeaverX in prepar3dv4
« on: June 07, 2017, 07:34:53 AM »
Patience is always good advice, especially when operating platform(s) change from (x86) to x64.

One of the first things I started to checkout was possible cross contamination between v3 (x86) and v4 x64 and I didn't find anything suspect. The calls made by Process Lasso show that the Registry hive structure is fully segregated as is Users\AppData/Local and Roaming. So far, I haven't found any interaction between v3_v4, but who knows? Only lots of re-installs and time will tell.

I was remiss in previous post by not stating that I have the AS Beaver X placed in v4 root folder and not as an addon. ProgramData file structure between v3 and v4 is very extensive. It's not going to be as easy "slicing up" (-v3) v4 into three separate structures as v3 was, but "what the hey", I'm a masochist.

(-v3) oops! and a couple of spell checks

General Discussion / Re: BeaverX in prepar3dv4
« on: June 06, 2017, 10:54:22 PM »
Well like a dumba$$ I went and got P3Dv4. Been very, very slowly testing my main "go-to's", the AS Beaver X being one of them.

It's working here; using the replacement cab and stock paints. Sometimes I have to flush the shader cache more than once to get an aircraft to work. I'd suggest flushing the cache and letting it rebuild. I also suggest no autogen vegetation (huge frame-rate hit) and try textures @ 2048x2048. x64 sim platforms "like" higher texture resolution.

From what I've seen so far, this version has the potential to run very, very smoothly literally right out of the box. Mind you, I'm using my old testing system:

                           EVGA 680i sli
                           Core 2 Duo X6800 o/c @ 3.809
                           8gb DDR800
                           W7 x64 ULT original release candidate rolled up to May 2017.

I'm currently running v4 box stock, no addons to aid in troubleshooting. I have swapped in a GTX 1050 ti card I use as a dedicated Physx card because it's got 4gb vram.


DX10 and Prepar3D Discussions / Re: Tongass Fjords - FYI
« on: May 31, 2017, 11:22:18 PM »
Man are you guys are fast or what!!!! I just might have to bite the bullet on v4 once FTX Central 3 is updated and tested to copy files correctly.


You can use Notepad++ and the plugins from Sourceforge to compare character or form discrepancies between text files and it's free.


DX10 and Prepar3D Discussions / Tongass Fjords - FYI
« on: May 28, 2017, 03:00:41 PM »



It just seems to be getting better and better. I for one will not be spending any money on V4 until it's fully fleshed out including compatibility issues.

General Discussion / Re: FTX Central3
« on: November 12, 2016, 03:39:46 PM »
Well, I'm one who has several custom installs of Orbx that are not in the P3Dv3 root folder and I must say, FTX Central v3 has been exasperating to say the least.

1) FTX Central v3 and OrbxDirect are centrally tied to the registry now and will be from here on out.

2) No matter what sim you're currently running, if your install of Orbx is fully stable, transferring your FSS licenses to OrbxDirect will not affect your current install in any manner.

2.1) Updating any of the scenery files or library through FTX Central v3 has screwed around the scenery.cfg file order. This is a known  bug and is being addressed. Sadly, customers have registered new complaints regarding the latest FTX Central v3 update of itself.

3) After transferring your FSS licenses, you don't have to re-download anything or reinstall anything for your current Orbx scenery to work. It will be simply activated when logging into FTX Central v3.

4) Since Orbx  has requested and FSS has agreed, the current FSS wrappers will continue to work should the need to reinstall due to HDD or SSD catastrophic failure. This will aid those who have to reinstall OS, Sim and Orbx from scratch.

5) At some point in the future, when all the "box of rocks" have quit their panic downloads and bandwidth has once again returned to normal, backup downloads will be much quicker than before.

Orbx could have and should have presented the necessary procedure more clearly in a logical and business like manner: NO EXCUSE.

I would (did):
                   a) Setup an OrbxDirect account;
                   b) Transfer FSS licensces;
                   c) Install FTX Central v3;
                     c.1) Migrate and activate the scenery;
                   d) Do not update and scenery files, the library or FTX Central v3 itself at this  time.

* Note for c.1): Since I've got several custom installs and am running Orbx on different drive, my scenry.cfg files were completely altered. I simply used my cfg backups and all was well. I don't think this would happen to a default install, but I'd backup my cfg just in case.

Just don't update anything as noted in d).

General Discussion / Re: Prepar3D V3
« on: January 09, 2016, 07:59:19 PM »
I hope everyone had a joyous Christmas or Holiday and a happy New Year.

Another update and more "slicing & dicing" of Prepar3D v3.

I think I've taken this particular endeavor about as far as I can. I'm now running 3 separate directories:

E:\Prepar3D v3 (as core)
F:\Prepar3D v3 (as scenery)
G:\Prepar3D v3 (as content)

I don't have to change any registry settings and EMT can be directed to which ever directory I want to add content or scenery to. Also, by using 3 identical directory settings, the core, scenery or content directory can also be properly updated with new LM releases if needed.

The only area I haven't explored yet is setting up fully independent sub-directories. On Avsim and LM's sites, there are problems with various aircraft or scenery installs working properly outside of the root P3D directory. To a certain extent, I've overcome those problems; however, content and scenery still reside in primary P3D directories. In order to fully separate content and scenery from P3D proper, I believe this can be solved by creating new registry paths to the new sub-directories under the Lockheed Martin primary register and linking everything together in ProgramData profiles. It sounds complicated, but it's actually just more tedious to setup. So there's more "slicing & dicing" to do.

General Discussion / Re: Prepar3D V3
« on: December 18, 2015, 07:23:10 PM »
                                 !!!!!! IT'S ALIVE..........IT'S ALIVE !!!!!!

Final working install: F:\Prepare3D v3  F:\Prepar3D v3 RTMM

Although I was able to put the scenery files on another hdd, it was very difficult to update Orbx and add other scenery without having to continually trace down errors.

Retraction required; not final working install.

This is the FINAL working install (at least on my current hardware):

F:\Prepar3D v3                                           G:\Prepar3D v3 RTMM
                                                                 G:|Prepar3D v3 Oceania
                                                                 G:\Prepar3D v3 Scenery Tester
And last but not least:                                 G:\Prepar3D v3 SimObjects Tester

I've finally gotten all remote locations fully working and have run several Orbx updates both manually and through FTX Central 2.

I even went so far as to run Orbx update tests with G:\*** Scenery Tester on a USB 2.0 docking hub. I wouldn't recommend running as such; the hdd got really hot grinding away.

More importantly, I've moved SimObjects out of root P3Dv3 folder. This makes it much easier to trial fly and troubleshoot aircraft without directly impacting the other directories.

My quest is finished.

Thanks to all who have put up with my "blogs".


General Discussion / Re: Prepar3D V3
« on: December 18, 2015, 06:30:04 PM »
Good to hear Patrick.

The latest EMT version goes a long way in correctly installing FSX software. It looks like the terrain file is the only problematic file to be correctly identified and written to now.

General Discussion / Re: Prepar3D V3
« on: December 17, 2015, 10:38:26 PM »
Hi have you try with Tongass installation ?   :)

Yes, using latest EMT v3.0.1.953. Accept for the terrain dance (swapping in and out), the install of TFX is now fully automated. Nothing to add to any folders and the scenery file in Programdata/Lockheed Martin/Prepar3D v3 is written to and sequenced correctly.


General Discussion / Re: Prepar3D V3
« on: December 17, 2015, 11:13:38 AM »
stiletto2 (Rod),

The guide is spot on for the use of EMT.

I just wanted to confirm that the latest version of EMT writes to and correctly sequences the TFX scenery entries. They are written to and placed in correct order and above Orbx entries. There's no need to go back add them after TFX install.

You still have to do the terrain dance, but that's not bad.

aka Al

General Discussion / Re: Prepar3D V3
« on: December 16, 2015, 11:26:20 AM »
Since I'm running such a "ba$terd-mod" install of P3Dv3, I wanted to confirm something I had said in my last post regarding installing Tongass Fjords X.

I uninstalled/reinstalled box stock P3Dv3.

 I then:
1) Created simple "dummy" folders: Effects_texture; Scenery/World_scenery_texture; SimObjects/Airplanes_Boats_Rotorcraft; Sound;

2) Placed a copy of the terrain cfg.file in P3Dv3 root folder;

3) Reinstalled TFX using EMT v3.0.1.953.

I've reconfirmed that all folders are populated correctly and that the terrain file in P3Dv3 root folder has been updated with all 40 TFX entries and that they're correctly sequenced and that the scenery folder in Program Data/Lockheed Martin was also updated and sequenced correctly as well.

Both configurators (32bit and 64bit) work in the FSAddon folder as well.

No manual entries were made; this was a full, automated install of TFX.

ps...I still haven't given up fully locating scenery on a separate drive.

General Discussion / Re: Prepar3D V3
« on: December 15, 2015, 08:57:46 PM »
                                 !!!!!! IT'S ALIVE..........IT'S ALIVE !!!!!!

Final working install: F:\Prepare3D v3  F:\Prepar3D v3 RTMM

Although I was able to put the scenery files on another hdd, it was very difficult to update Orbx and add other scenery without having to continually trace down errors.

I have also moved both Autogen and Texture from root to remote. This eliminated having to swap those folders in and out for Orbx installs and maintenance.  So all in all, Autogen, all scenery and Texture now runs remotely. And on a side note, using the latest EMT beta, Tongass Fjords X install completely. I simply put a copy of terrain file remote directory and everything was fully written, even down to correct numerical sequence. Even scenery file in Program Data was updated correctly. I didn't have to do anything other copy terrain back to Program Data.

The sim runs flawlessly and I'm still very "old school" with Core 2 Duo X6800 @ 3.47ghz and multiple 10K WD raptors. This will now be changing since "proof-of-concept" works.

Currently, I'm running both F:\ directories as contiguous files running on the same hdd track using UltimateDfrag.

Scenery Tester was 5X5 and Misty's Place sure looked good.

If anyone is interested in the "how to" for splitting up P3Dv2 or 3, let me know. I'll put together a guide. 

KUDOS to all you guys that have devoted so much time, energy and love for "Return to Misty Moorings".


General Discussion / Re: Prepar3D V3
« on: December 07, 2015, 09:31:49 AM »

Thank you Sir.

P3Dv3 install, Program Data formats and Registry entries are completely different than P3Dv2. P3Dv2 can be fully "manipulated" like FSX; P3Dv3 can't. P3Dv3 is almost draconian.

Now for a another update: Good

P3Dv3 has been installed as E:\Prepar3D v3 _ F:\Prepar3Dv3_RTMM/Scenery

This is done because P3Dv3 "sees" Default folders and loads in a very rigid sequence.

I've run the install many times, changing various settings and it's been stable so far.

Now that I've got P3Dv3 Scenery fully remote, I'm going to start working on Orbx. I'm working on what Orbx installs natively, what's overwritten and Program Data entries using a box stock install of P3Dv3. From what I've seen, the Orbx P3Dv3 vs P3Dv2 install is dramatically different.

"for ORBX don't miss : if not upgrading 4installer to V3 some problem with the objects flow"

Head over to AVSIM and on page 4, look for post by z06z33. He's found a solution to objectflow running in P3Dv3. I had suspected that it had to do with something in the Libraries, but I've just had to much on my plate to investigate this myself. Kudos for a very elegant workaround and it does work, this I've tested.

General Discussion / Re: Prepar3D V3
« on: December 05, 2015, 09:55:33 AM »
Update on my quest: "The Good, The Bad and The Ugly"

The Bad:
           P3Dv3 will not run when Scenery is not in root folder. At 69% when terrain is initiallizing, the Shader rebuild crashes. I don't know if this is due all Scenery folders, part of them or some of the individual entries within the folders. So I'm back to square one on this front. If you haven't already, take a look at Prepar3D install using Control Panel/Uninstall Program. There are four P3D "modules" installed one of them being Scenery! The other, SimObjects, I feel will also cause fits.

The Good (sort of):
            P3Dv2 runs flawlessly with all of the Scenery folder and Orbx installed outside of root folder in a dedicated folder on a separate drive: Prepar3D v2 root on my F:\ drive and P3Dv2_RTMM on G:\.  FTX Central 2 activates and updates correctly, including Objectflow updates, and once the initial Shaders have been built, it loads quicker as well.
The complete P3Dv2/Orbx install was done without use of EMT. If you want to simplify the Tongass Fjords X install, it will cut down on some of the editing; however, TFX configurator will be functional in the remote location.
The Ugly:
       The initial install requires some time consuming edits, renaming of files during install and relocating one major folder, Texture, back into P3Dv2 root after Orbx is fully installed.
Future updating of Orbx will only require a simple temporary folder rename for maintenance; however, the Texture folder will have to be swapped in and out during the process.

** Side note; with P3Dv2 and P3Dv3 side-by-side install on same drive, I wasn't able to select P3Dv2 for Orbx install. I had to uninstall P3Dv3 to setup Prepar3d v2 / P3Dv2_RTMM.

My intent for this "exercise" was a proof-of-concept in helping me to define my new PC build focusing on a functional RamDrive to run Orbx and Scenery in system memory. At least this can be done with P3Dv2.

So I'm going to keep my current P3Dv2 / RTMM install for further 3rd Party scenery testing and dig back in to the P3Dv3 Scenery conundrum. Once I have this figured out, or at least working to an acceptable level, I'll nuke P3Dv2 start P3Dv3_RTMM all over again.

If you want a short video or two, I'll install the RTMM Libraries and Tester, but alas, there'll be no Avatar. Maybe BoB will work?

General Discussion / Re: Prepar3D V3
« on: December 02, 2015, 06:27:17 PM »
Thank you kindly NeptuneP2V7 for your P3D install workup; very inspirational. It's taken me several days of installing, running Process Lasso, reinstalling over and over and.... to get to this point:

ORBX has now been installed and is now residing in a directory outside of the P3D root folder along with the P3D Scenery files and Tongass Fjords X.

GOD willing and the creek doesn't rise (it's flooding up in NW Ga.) I'll commence re-linking all the Scenery, Effects, Texture, Sound and SimObject AI cfg. files this weekend. Initially, I'll only be using the RTMM Libraries, Scenery Tester and Misty's Place to run trials.

IF this pans out, I'll post a couple of videos, one showing the Scenery Test and one with the Avatar walking around Misty's Place.

Tested so far, FTX Central 2 as updated and applied the regions correctly.

Right now, I'm absolutely burned out.

Pages: [1] 2