Bertrand Coconnier

@mike402 I think the 2nd kind of warning message has also been considerably reduced since the components are no longer tied to the property specified in `name=""` ? For the...

> I still see a million "already defined" warnings unless I comment out this message Well, unfortunately we are facing a problem here. When the message ` already defined` is...

@mike402 > And no, don't give me that "remove all those \" again Did I ever say/write that ? Could you point at the message where I asked you to...

> I did not say you said that, Nikolai said it. I only mean to say I am frustrated that this remains the only way to avoid these warnings. >...

> Why not simply use the already-existing value of to initialize the element (for example integrator or actuator) with that value? That would also help FlightGear implement full state saving...

@mike402 After giving more thoughts to your request, I think I jumped hastily to a false conclusion. Apologies for that. You are suggesting to use the existing value of a...

For the sake of completeness there is a second occurrence of `vOmegaLocal` in `src/initialization/FGInitialCondition.cpp`: https://github.com/JSBSim-Team/jsbsim/blob/d9df84593b40a5bddb67a94f51d57cd1e514c313/src/initialization/FGInitialCondition.cpp#L1414-L1419

The bug can be fixed by forcing `vOmegaLocal` to a null vector: ```diff --- a/src/initialization/FGInitialCondition.cpp +++ b/src/initialization/FGInitialCondition.cpp @@ -1191,10 +1191,7 @@ bool FGInitialCondition::Load_v1(Element* document) // Refer to Stevens and Lewis,...

The formula `-radInv*vUVW_NED(eEast)*tan(position.GetLatitude()` is really a big issue when the latitude is close to 90 degrees even for small velocities: it can initialize the vehicle with a huge spin velocity...

> In trying to get up to speed I've been reading my copy of Stevens & Lewis which happens to be the 3rd edition, I'm guessing you're quoting from the...