Ralf- just to confirm that it is transmitted Dumo and I flew the "C PlanesetTest" I set up which has the entire Malta campaign as Planset1. I set it to 1, Dumo's was 0, but it was transmitted and we both flew Malta


http://www.users.on.net/pam_biddell/PS.exe

Jel

Night Blitz is getting on a bit - must be 9 years old! Quite probably the "lights" had "unintended consequences"

Many of the airfields in Dunkirk had a "flarepath" (principally because there was a whole "night intercept" part of that scenario)and the lights there were better edited.



The relevant planes had nav lights, and the Defiant model had landing lights keyed into the undercart rather like the old "close cockpit" mod, which came on when the undercart went down



The thing with the nav lights is that they were always on. I did originally pursue the idea of having visible exhaust glow, which was what the original early nightfighters actually looked out for. But development of night blitz ended at Christmas 2001, and I never picked it up again afterwards. The control tower 3dz is dated 20th December 2001



Moggy DCM

Don't forget, I did a mod for the HR Hurricane, which gives you realistic glowing exhausts.

I did forget that. . But am glad to remember it now.

Remind me how you did it Col - did the exhaust sprites take the glowing colours?

I last edited that Ju88 with the prototype "glow" in November 2001.

Here's the original thread on lights: http://simhq.net/forum/ubbthreads.php/topics/793397/1.html 27th August 2000

If we are going to have more extensive night fighting, it would be good to have realistic glowing exhaust on all relevant planes.

Perhaps the nav lights could all be tied into the undercart code so they are only there on take off and landing?

The flare path could have its Tmod properties edited so that it only becomes visible within a short distance of the airfield.

Moggy DCM

Hi Moggy.

I changed the exhaust elements from code 5 to code 3, and added a glowing orange colour.

Your Tmod problem is easy, just use the H model for the lights, and use a blank for the L and M and S 3dz's then the light would only go on when you got close.

I was thinking of doing the same idea but in reverse for the houses. The L would be lit, and the H would be unlit, then as you approached a city, all the lights would go off.

UAW160 with the "Added searchlights ETO" theatre and the mission time set in parameters.


Runway with flarepath and searchlights F9:



Alt-N



A kill

More piccies



Being able to set the mission time based on sunrise and sunset really helps you to get just enough light intensity for your mission, and the new map is great for locating the enemy.
Each circle is a tile- 4.096 kilometres














Tracers often help to locate the action

I would add that the seachlights in this theatre do not come on unless the light intensity is low. Additionally they are triggered by nearby aircraft.

A view from my six moving away from a searchlight:

Tmod indicator and searchlight visible at 17000 feet


Shortly afterwards the TMod indicator switched off:


..and a short time later so did the searchlight:

I like that ,Jel. Always had a thing for EAW at night. Is actually playable if you do it in a darkened room and drink plenty of carrot juice

Yeah, it gave me quite a few headaches when I created those lights. My newest model can now also be attached to any 3D model and any target in any addon as described, anywhere in the EAW world, instead of coming out of the roofs of hangars at one specific location, like the old versions did. Hence I also gave it it's own dedicated 3D model, which in this picture ofcourse has the light switched off during daytime



and in the evening and nights remains on standby when no aircraft are near



VonBeerhofen

Neat
What controls the speed of rotation?

a few appropriate counters in the game's zero page for the lights, not the 3D object. The object uses rotation from the camera view, it doesn't actually rotate but uses a trick to make it appear to rotate when the camera is moved.

VonBeerhofen

I use an external file with the settings in it that the exe reads and uses.

I know, doesn't sound to me as a good reason to drag this particular 12 year old topic from the depths of the Underworld and open up old wounds in spite of the specific warnings from the SimHQ moderators. You better stay away from raking up these past attacks as you are risking the total annihilation of this EAW forum!


VonBeerhofen

Trip down memory lane. Some screenies from my first experiments with lights November 2001, over 21 years ago:





Here's the thread from the archive where I posted the first experimental night fighting package:

http://SimHQ.net/forum/ubbthreads.php/topics/790586/Experimental_Night_Flying_pack.html#Post790586

Things have come a long way since then,





VonBeerhofen

BTW the initiator of this thread hasn't been seen since 2014

Certainly have.

The facts are simple.
Two days ago when I checked to see who was online I saw a new member who was reading this thread. So I had a look too, and realising that it was way out of date I added some posts to update it.
Nothing more and nothing less

What an extra ordinary coincidence, I added a few more things too but more as a teaser for the general public. I hope your guy picks up on it and understands why my creations belong to me and will only be available for download when I choose so, irrespective of external pressure. Their campaigns are still far from finished. Just saying. Maybe some day he will even understand my difficulties when instructing dozens of online pilots in the art of file managing for a decade and to make what I consider the best choice for the Launchpad pilots, which is why we're still flying every other day and having fun. Things haven't changed much in that respect since then, and I doubt they ever will, we'll see,

VonBeerhofen

Since I hadn't had the opportunity to react in the original thread on Jelly's claims of none transmitted plane data in 1943 on line missions with FXEXE, I decided to have a look at that myself and ran 3 entirely different missions with two computers in an on line home environment.

First an observation of this thread which began with something about night fighting but soon started to change shape into something else which oozes intimidation, not uncommon in this 'forum' and a typical code group modus operandus. 5 dead horses on one single page, wow! It almost looks like an abattoir. A thread started by a guy who hasn't been seen since 2014 and revived after 12+ years, showing multiple pictures of MY old searchlights because some guy was caught browsing this particular thread from 12+ years ago, .

Anyway, I tested Mr. Jelly's claims and found that all v1.2 derivatives, including FXEXE and EAWPRO produced the exact same aircraft, same numer of planes, the same mission type in the exact same location in EAW, even human flown heavies, on either machine. So that proofs that these guys were just as little all knowing as anyone else at the time, including myself probably. I already believed it to sound weird as we spend a lot of time investigating these mishaps with Pobs and JG51, which even could result in flying in areas more then 500 miles apart. We used to call these missions Search and Rescue, since regularly one player had to deal with all enemies and his supports could only try to reach his location ASAP to help. Of course that could take a pretty long time so it wasn't something we did regularly. Anyway, the cause of these discrepancies was identified and from there on everything worked as it should, just as it does now with all v1.2 derivatives. It just shows that people aren't always right, even though they claim they are and that the other guy doesn't know what he's talking about, which is probably the lamest excuse for not entering an honest debate about these issues. I'm also sure that the entire EAW community took his word for granted, they just couldn't proof the opposite. I think I didn't even bother to respond knowing that Jels's claim was nonsense and left for 5 years of fun with my on line friends, that was until a guy who called himself Hector infiltrated the Launchpad in 2015 and ran off with my creation (including my searchlights).

So this once more leads to the question, where did this fake news about FXEXE and v1.2 come from? I mean, both versions work 100%OK, and if you don't believe me try hooking up 2 computers through your router with the game on it and start counting planes as I did. If the claim was not coming from a 1.2 version or it's source code, then the code is much more likely to be a 1.1 version, where not all AI were taken care of yet and all other things mentioned in the official v1.2 upgrade were also not implied. After all it's clear that the claim didn't come from testing existing versions, because that would have clearly shown they work fine. This is also much more in line with the v1.1 EXE's filesize of the first code group release, as I already mentioned long ago. Mind you I haven't tested v1.1 but I wouldn't be at all surprised to see it does have the problem Mr. Jelly is talking about and undoubtedly the first code group releases prior to this particular post probably will have too, although it's something which is very easy to deny, after all it can not be proven unless someone other then a code group member can still test those.

Not that it matters much today, but this attack on the FXEXE was clearly nonsense and just another attempt to glorify the code group's version. It highlight's the animosity which was playing out at the time and puts it right back in today's animosity, throwing more dirt on the FXEXE and EAWPRO for a 2nd time, and that goes entirely against SimHQ's ignored warnings. So I hope SimHQ doesn't mind me giving it all back to Mr.Jelly so justice can be served. Stop your silly attacks by using my creations Mr. Jelly and stop dragging old attacking posts from the past into the now!


VonBeerhofen