[TEC] undersea.GR2

[THE_MASK]

Originally Posted by Trevally.

Placing ships with the object editor will stop them being ships and make them objects instead

They will not be date related, so will be there at all dates

They will not belong to a country and thus will not update as the country war state changes - also no flags.

Z- ships are only in ports that lag when there are many objects (piers/houses/etc)

Exactly , they would be just a filler , the same as houses .

[Trevally.]

Originally Posted by sober

Exactly , they would be just a filler , the same as houses .

yes but more houses = more lag

[THE_MASK]

Where can I download the GR2 editor from ?

[oakdesign]

ok while I still not sure how the light effect through FX_Update was/is added to the lighthouses,
I made some progress in using the same settings as used with the imported buoys

here are some self illuminated small costal guns with flashing lights.



another finding with working with the bulid in GoblinEditorApp was that on Win7 with Aero design I could not change any controller values that are of type DropDownList. Has to change apperance to windows classic style in order to get those to work.

[TheDarkWraith]

Originally Posted by oakdesign

ok while I still not sure how the light effect through FX_Update was/is added to the lighthouses

It's all right there in the files in FX_Update. Unless you are VERY familiar with the files and controllers of the SH series it probably doesn't make any sense to you. It was all done via hex editor also I use the method of 'cloning' the node so that the effect is used only once for every lighthouse (special node type for this).

[THE_MASK]

[Fifi]

^^^^ Very nice Sober!

[oakdesign]

Originally Posted by TheDarkWraith

It's all right there in the files in FX_Update. Unless you are VERY familiar with the files and controllers of the SH series it probably doesn't make any sense to you. It was all done via hex editor also I use the method of 'cloning' the node so that the effect is used only once for every lighthouse (special node type for this).

TDW I already recognized your cloning if I just use a little offset on your modified files while comparing to the stock ones.

I was just wondering because in the Goblin Editor your changes won't show up.

Even so I have a master in computer science I'm a bit on war with Hex, and all the Low Level stuff. Being more in System architecture and managed code stuff.

Nevertheless I'll follow down the road getting more involved in the existing controller and their usage.

Is there any documentation on controllers available or have you all gone the hard way by either try and error or hooking into processes

[gap]

Originally Posted by oakdesign

As sober already stated back in 2011 if you try to merge the kiel.sim to kiel.gr2 as the GoblinEditorApp crashes or better to say any of the *.gr2 files from
\data\Terrain\Locations\CustomAreas
no matter if the stock *.sim file is used or any from TDW's FX update.

Are you sure that stock sim files are crashing Goblin Editor as well as their FXU version? While I was working together with Volodya on the new torpedo explosion effects for FX Updates, I have noticed that Goblin doesn't like TDW's hex edited controllers, though the game handles them correctly. They could be the reason of Goblin crashing while trying to merge GR2 and sim files

Originally Posted by oakdesign

If opening the sim file first it's at least possible to open the *.sim files and as I know wich ones are the controllers assigned to the light house I could look at.

What is scratching my head if I look at the controllers of the stock *.sim files and compare with the modified ones from FX_Update they are identical.

So next step was to compare them with HEX Editor. Ok it's clear that the *.sim files from FX_Update are HEX edited and all have an addidional XXX_LH_Flare_1 part but still no clue how the "light effect" is achived.

Try opening the sim file within s3d instead: it is capable to read TDW's new controllers. They are placement controllers, and they are used for linking the light effect by TDW (TDW_FXU_Lighthouse_flare.dat) with lighthouse models. I wonder if prt files and MergeCtrl controllers could have be used as well, as described by silentmichal in this post.

We should be able to do the same with any newly inported lighthouse model, and hopefully they would get working lights on them, as long as FX Updates is enabled. We could also duplicate TDW_FXU_Lighthouse_flare.dat and make the placement controllers to point to the new Id. Finally, we could even customize TDW's particles so to have different pulsing light frequencies, but again, we would need to edit them in Hex Editor, as neither Goblin Editor nor s3d can read them.

Originally Posted by oakdesign

Another idea of getting a "light effect" working is that I'm going to inspect the "lighting" of the imported OHII has been achived.
It's clear that the buoys have an a mesh consisting of a single face that has a controller attached. Maybe this might be the easier way to go on

Yes, this is a possible alternative. I am sure this is doable by assigning lighthouse lanterns their own material, and by setting its emissiveness property appropriately. Nonetheless, lighting effect achieved by this method would be static (i.e. no flashing light). All in all, I think the best way to set lighthouse effect is a mix of your and TDW's methods

Originally Posted by oakdesign

another finding with working with the bulid in GoblinEditorApp was that on Win7 with Aero design I could not change any controller values that are of type DropDownList. Has to change apperance to windows classic style in order to get those to work.

Right click on GoblinEditorApp.exe, select properties, go to the 'Compatibility' tab, and check 'Disable visual themes'

[volodya61]

Someone here mentioned HEX editors? specialists are needed?