posted 05-29- 02:27 AM               

Hi guys, I wanted to use the 162 as my basis for my new project but it crashes OPS.

I have tried 3 versions of OPS and its all the same.

posted 05-29- 04:09 AM               

Wa man, that would rock.

All that new stuff plus this would really be some great stuff.

K here's the link.
http://greenforce.net/fs/fs.htm

posted 05-30- 12:19 PM               

------------------
-=TheReaper=-

posted 05-30- 12:22 PM               

TS

posted 05-30- 09:28 PM               

My new PC got delivered this morning so perhaps it will fail on that, when I try it tonight.

In the mean time, can say at what point it fails? i.e. Before the model tree window fills, after the model tree window fills, or when you do a particular thing etc etc. Does it fail if you manually set the viewport mode to 'Mono' via the preferences?

posted 05-30- 11:11 PM               

With the Huey, OPS is loading textures and then it stops responding so I have to close it with CTRL-ALT-DEL.

UPDATE:
Woah, it worked one time... got the Huey to load in OPS. Woohoo now I can line up the gunsight! Watch out, world!

------------------
-=TheReaper=-

posted 05-30- 11:15 PM               

I just open ops 1.2 then without doing anything to ops, i open the he 162 and it illegal ops while loading the plane.

OPENPLANESTUDIO caused an invalid page fault in
module KERNEL32.DLL at 015f:bff7a379.
Registers:
EAX=01313de4 CS=015f EIP=bff7a379 EFLGS=00010212
EBX=013145e8 SS=0167 ESP=0073eee4 EBP=0073ef08
ECX=20202020 DS=0167 ESI=00000934 FS=5787
EDX=01280000 ES=0167 EDI=002016ec GS=0000
Bytes at CS:EIP:
89 41 08 8b 53 04 8b 43 08 89 50 04 8d 04 33 50
Stack dump:
002016ec 00000000 0128000c 01280000 013145e8 00000000 00000000 00001516 00001315 0073ef30 bff7a541 01280000 013145e8 00000934 00000000 0000092a

posted 05-31- 02:14 AM               

One thing that might be interesting is to come up with a "FM" version of OPS. Rather than having a 3d viewer, LOD information, textures, DOFs, BodyPts; this version would be more like a tax form, where you modify values. There would be a list of every part on the left like in the current OPS, but each part would be associated with one of a few forms. There would be a form for engine(s), one for propellor(s), one for aircraft, one for airfoils, one for fuel cells, and one for generic parts. Clicking on a part in the browser on the left would bring up the form that should be associated with it, and pre populate it with whatever current data the part has.

The generic parts form would just allow you to specify a comment, and either phyLBS or phyRelDensity. The aircraft form would allow you to specify empty weight, and the aircVa, aircLandingSpeed, etc. The other forms would be similar. The forms could be further elaborated by allowing damage information to be input as well. So, basically I'm talking about the left pane and the right pane (properties) of OPS, but with less detail, and more user-friendly UI.

Or, the tool could come up with a list of all "important" models: engines, propellors, airfoils, and display them with their values in an editable form. This might be useful for people who are new to OPS, and don't really know where to look, and what to change. For instance, many of the WWI devs overlooked engSFC initially. If a form asked for maximum flight duration, and then calculated engSFC based off of that and the total fuel capacity, it might be more intuitive.

posted 05-31- 08:34 AM               

Try running the release version under windows 95/98 you'll find a lot of page faults.

TS

posted 05-31- 09:31 AM               

I'm using dx7a if that helps at all.

posted 05-31- 10:40 AM               

I will make a debug build with some usefull stuff in it, when I push out the next one. Hopefully that might help to track it down.