Well, I also seen the same.... seems somebody missed jflpac

CF widescreen
- SWAT_OP-R8R
- Thread is marked as Resolved.
-
-
Quote
But, yeah, I know that Swat is the only place in the Freelancer universe where modding information is taboo
yes thats why we have modding boards, modding tutorials, discussions about modding, new modding concepts, modding tools, support areas for modders and a modding school for new SWAT Dev Team membersQuote(Obviously, the line in DaCom.ini should be "jflpac.dll" and the file in the EXE folder should be jflpac.dll.)
only of the AC version was not compiled under the original name without ac extension -
only of the AC version was not compiled under the original name without ac extension
Assuming that jflpac works correctly with the name changed, and that the dll was built correctly, then I do not have any other ideas without trying 1.82, which is not going to happen soon.
However, if it is not working, then I would examine the above assumptions (if you have not already done so).
Name changes are usually, but not always, harmless.
I think that I remember that Adoxa posted header files on his web site. I do not know whether they are required for building jflp(ac). If the standard jflp(ac) works but your recompiled version does not, then check the headers.
Also, if you built your new jflp(ac).dll with a recent version of Visual Studio, then make sure that it is not built for a specific version of Windows. That could, potentially, cause the dll to work on some systems but not on others. It may be easier to build with older versions of Visual Studio (2005 or earlier) than it is with new versions.
This is Off Topic, but IMHO Microsoft's best software was the 2003 versions. Since then there have been more problems than there have been improvements. The only reason to use newer versions is for 64-bit support (which is important for big memory, unfortunately).
2003... that was a great year for Microsoft!
-
jflp is working on the clients. I tested it - the only thing i was not able to test is and was the widescreen support. But as far i didnt changed anything on that piece of code i wouldnt see any reason it should not work.
I compiled the dll in VS2010 for X86 systems - as FL is not for x64 systems its useless to compile it for x64.going to have a look at it in debug mode. hope to figure out whats wrong if its not working. The current version is the AC version although it not named AC - as there is no need to name it this way.
If it not working that the setting in the cameras.ini for fovx and fovy needs to be set to 0 - I cant test this as i dont have a widescreen system - so that would need someone who could do the tests for me... -
jflp is working on the clients. I tested it - the only thing i was not able to test is and was the widescreen support.
Wait... so what did you test? The only important thing that jflp does is widescreen support!
I suppose there are a couple of smaller things you could test.
I cant test this as i dont have a widescreen system - so that would need someone who could do the tests for me...
If you still need this tested tomorrow night, then I will be able to test it for you, Huor. Just, please, don't be like OP and forget to tell me if somebody else does it, ok?
I have a project release tomorrow, and am busy with that until it is done (and accepted).
-
the more it test the better
There are other stuff that jflp.dll is including what i will tell when i have time. As the other stuff is working and the widescreen thingy not than i have no clue why - because like i told i didnt changed any code for the widescreen support and i didnt changed anything else on the other features. So it really could be that the values in the cameras.ini file have to be set to 0. <<< would need confirmation and so far the more it would try to verify the better... -
did i forget something?
-
the more it test the better
OK, let me put it another way... I do not want to test it. At least, not anytime soon. However, I am willing to help you if you need help, but not before tomorrow.
@OP: All I know is what I read on this thread. It appears that jflp is not working, but Huor cannot test it. So I volunteered to help you guys figure out what is wrong.
I am, however, busy in RL. So if somebody else can test for you, then I would prefer that.
I only ask that you let me know (or post it here) if you get it tested or figured out, so that I will not waste a couple of hours duplicating the effort (as I have already done once, on your behalf, regarding jflp).
-
its ok bullwinkle. I am also really busy these days in RL - so hence not much mood to do coding in the evening hours when i am doing that all the day long
And i guess we wont have a result until tomorrow. So when you are in the mood and have time to test it and you didnt found a result here than test it. If not then not. You are not forced to waste valuable time same as i am not forced to do so and OP is not forced to do so.So when we have the time and resources to solve it it will be done. If not than not^^ I am relaxed on this issue and hope so you are too
-
when you are in the mood and have time to test it and you didnt found a result here than test it. If not then not.
Cool. Sounds like a good plan, Huor.
-
when you are in the mood and have time to test it and you didnt found a result here than test it.
OK, I tested 1.82 and I am sorry to report that your version of jflpac does not appear to be functioning properly.
I tried multiple times to be sure:
- Added standard jflpac.dll (v 1.1) in EXE folder
- Changed DaCom.ini to say jflpac.dll rather than jflp.dll.
- Launched Single Player without Internet access.When I do the above, widescreen works correctly. (Easy test: In-flight HUD windows should be in the correct locations when jflp is working properly.)
When I launch normally, widescreen does not work correctly.
Also, I see that your DLL is less than half the size of the standard DLL. Since there are only a couple of small lines that need to be commented out for OP's logging requests, the small size of your DLL suggests that it may not have built correctly.
-
thanks Bullwinkel - when i am back at full health i will have a look into this. Currently i not in the mood to do any coding
Damn autumn