Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ACagliano

Pages: [1] 2 3 ... 61
1
A few teasers from the upcoming 0.0.94 release.

1) Custom graphics packs supported. To indicate that the graphics pack is custom made (so the client doesn't do a normal version check), you use the following settings in convimg, in addition to the normal ones.
Code: [Select]
lut-entries: true
header-string: "\xff\xff"
Special thanks goes to MateoC for implementing the `lut-entries` option in convimg... it simply moves the offsets LUT into the appvar itself, rather than leaving it defined in the program. This allows the program to load any array of sprites as assets. You will still have to keep the same sprite order, however. Refer to the link I posted previously for details.

2) The splash screen has been completely reworked.

The menu interface is cleaner, and the networking status is indicated by icon now, instead of by text. A green USB icon indicates that the serial device is ready, a red icon indicates some error. If we implement nanotube, or internetce support, an icon will indicate if the program is preferring that connection.

3) The program now alerts you on the splash screen if your graphics version is incompatible.

The incompatible graphics is triggered in one of two ways:
 a) You are using a default sprite pack and the version header does not match the one set within the program's `reqd_version` array.
 b) You are using a custom sprite pack (version string 0xff, 0xff), and the number of sprites in the LUT does not match the number of sprites in the program build.
Either of these being the case causes the above alert to show up, and the "Play Game" menu option to just return you to the main menu.

All splash screen and error/alert icons are built directly into the program to ensure they are available... the asset pack only supplies stuff used for the game.

2
News / Open letter to TI
« on: June 09, 2020, 01:50:20 pm »
I posted this to Cemetech and now am here and will also on Codewalrus.

Quote
I would even propose calling TI's bluff on something. Write TI a letter, signed by a EVERY major calc development community - Cemetech, Omnimaga, Codewalrus (unity is important on this), informing them that if they do not revise their decision on C/asm, and implement exam security in a way that is conducive to teaching, learning, and doing programming, we the community will be designing, releasing and marketing our own calculator to compete with them. And if they do not walk it back.. actually follow through.

There is no action legally they could take to prevent this: it would be our own hardware and programming, no copying of names, symbols, anything. Free market, people can compete with whoever they want.

3
UPDATE

Project TI-Trek has now been successfully compiled with full USB support... using srldrvce. Due to wonkiness in CEmu's usb support, it is no longer possible to test networking on the emulator (the lib cannot initialize the driver properly). I will need to move to on-unit testing for the remainder of client-side development of this project. I have gotten written the ntwk_Login(), ntwk_Register(), and ntwk_Disconnect routines, which are the first aspects of gameplay that will be tested. While I have been hard at work on client-side things, commandblockguy has been working on a USB=>IP bridge similar to the one Kerm devised for gCn over DirectUSB. And last but not least, beckadamtheinventor has been hard at work developing the server side of things... from map generation to control codes and saving/loading data. For those interested, the server is written in Python, runs on port TCP 1701 (the registry number of the Enterprise), and uses json for long-term storage. It stores connection descriptors to an array of Client objects, which also contain the IP address, username, and some more information about the connected user.

The game will implement semi-accurate space physics. When the map generates, the server pre-generates some paths for celestial bodies using formulas for things like gravity and inertia. Those objects will follow those paths every tick, scaled to the time-rate of the game. In addition to fluidity in space (meaning planets, starbases, etc will not be in exactly the same spot every time you look for them), other objects will pose a threat... black holes will exist and end your journey very fast. Stars will tick their life cycle and then die in a manner determined by their size. Major celestial events, such as star death or planet destruction will result in a path-adjustment for entities within gravitational range of the changed section.

Also, after discussion with beck, another feature will be added to the game, called a synthesizer. This component will allow you to interact with materials you own on a molecular level to enhance them in certain ways. For example, say you place a piece of tempered steel into the synthesizer. You can then select from reserves of any type of element, and the properties they enhance/detract from will most reflect their actual chemical properties (toughness, deflection, malliability, heat resistance, etc). Say you choose to combine the tempered steel with a type of element that increases toughness but decreases heat resistance. You would wind up with steel (hull plating, for instance) that provides a boost against projectiles and physical impact, but is damaged more by heat sources, phasers, and the like. You could also, for instance, infuse your hull plating with a mineral that enhances magnetism, which in turn enhances your shield deflection. And if you attempt to combine unstable materials, you could, for example, wind up inflicting feedback damage to an attacking enemy, but also winding up with vastly increased damage to your own ship.

For anyone wishing to have a look at the code-base so far (yes, it will need some optimization), here it is. I will say, in my opinion, at least the network handling is remarkably well-organized... for what I usually do.
https://github.com/acagliano/titrek-calc

4
UPDATE

Progress has been made on the User Interface for TI-Trek. Here are some screenshots:
The Main Systems module overview screen


The Tactical Systems module overview screen


The module configuration/info popup, accessible by pressing [Enter] on chosen module


Some changes to the power system setup also. Module efficiency (how well it performs its task) will be a function of module battery charge (current power level * 100 / max power storage) multiplied by power draw setting (set power draw / base power draw). Power draw meaning how much power a module will take from its source (core, auxiliary, or internal reserve) every power cycle. Each module will also have a maximum draw, which is the maximum amount of power a module may be set to draw before the module incurs a damage penalty every power cycle. For instance, if the module's max draw is 8 and you have it set to 10, the module will take 2 points of damage every time it draws power. This means you can set a module to use as much power as you want, to super-boost it, but keep in mind the higher you set this, the faster the module takes damage.

5
TI-BASIC / Re: What is the point of those old TI-Basic "antivirus" programs?
« on: September 01, 2019, 10:57:42 am »
Placeboware... basically every antivirus software ever made :p

Back to the question, TI-Basic does not have the capacity to scan a program, even by name. So yes, they're just trolly, cool-looking things, that in reality do nothing.

My Blast File Integrity Software program does actually scan programs and appvars for user-contributed strings of malicious code, and retains checksums and file sizes to see if a file has changed, but this is more akin to a file integrity software than a malware scan. It's also written in C, which compiles into assembly, hence why it CAN do this.

Aside, considering the current impossibility of getting a "virus" on your calculator, all of these programs, including mine, are completely superficial. However, as the capabilities of these things improve, a time may arise when they may be at least partially useful.

6
Hey all. It's been a while. I haven't posted much in terms of this project here, but it's been ongoing.

1) The project page at http://clrhome.org/startrek now has a sister: http://titrek.us. This is mostly due to me wanting to host the site for it on the same server as the game itself.
2) There is a web frontend for the game server: http://srv.titrek.us. This lets players log in to their game account to change their in-game names, email, password, sub to notifications about the game, alter the appearance of their ships/etc. The frontend is in the very early stages, but it's coming along.
3) I'm no longer working solo on this project. A number of people are assisting (or involved somehow) in this project. I am tackling the client side and web frontend of this thing pretty much solo (with beckadam and whoever else is good with raycasting helping with the rendering aspect). For calc=>computer=>server communication, we are awaiting the functionality of the TI USB Device lib. For the server itself, me, GregsAStar, and beckadam are working on the Python. The save files are JSON, the server will be running on UDP 1701 (for the registry number of the Enterprise). I am also hosting this entire project... git for the projects, the websites, and the game server itself, on a Raspberry Pi 4.
4) Additional help has come from EaghanScarlette and Pieman in the form of sprite work, and Eaghan has agreed to assist me with formulae for the behavior of certain celestial entities, to make the behavior of space, and forces like gravity, as accurate as possible.

Screenshots available at: http://titrek.us/gallery.php
Pre-alpha (GUI test, no real functionality yet) available at: http://titrek.us/downloads.php

7
UPDATE -- 0.53 alpha-ish

Ok, update time!!
This game took a bit of a hiatus, as many of my projects do from time to time because of real life, skill building, and other stuff.
However, I did some code reorganization at the start of the summer, then set out on an endeavor to have a working demo of basic combat (single player) by the end of the summer.

Attached is the current pre-demo release. This version is functional but has no AI or rendering engine yet. That is what I'm working on now... 3d rendering, weapons and targeting, then wrapping everything up, optimizing, and releasing. That being said, I'll talk about some of the cool features already implemented:

1. Ship Status Icon
At the lower, left side of the screen there is an icon that shows your ship and your shields. As your ship takes damage, you'll notice the shields first. They start off electric blue, then degrade to yellow, then to red. Additionally, within the ship itself, which is normally grey, sections of the ship will turn red as systems are damaged. Hull integrity causes a small filled red circle when it reaches <50% in the saucer that gets larger when hull integrity fails. In addition to that, the nacelles turn red when the warp drive is below 50%, the aft of the ship turns red when impulse, life support, or the warp core fall below 50%. As of now, this icon is locked to an Enterprise-ish shape, as are the indicators. If/when I allow icons to be customized, I'll have to modify this to match.

2. Warp Core Failure
When the warp core system is damaged to less than 25% health, the program begins attempting to trigger a warp core breach. The odds of a core breach are 1 / system health * 10. So, for a warp core at 24% health, the odds of a breach occurring are 1/240. If the warp core is at 10% health, the odds become 1/100. Once a breach is successfully trigged, a timer begins. You get 1000 game cycles to avert the breach or your ship is destroyed. I have yet to clock how long that actually is. You can avert the breach by (1) Repairing the warp core to above 50% health (see Repair), or (2) Pressing the [Del] key to eject the warp core. The ejection occurs and spawns a critical warp core behind your ship, on a slow trajectory moving backwards (relative to you). Doing so immediately stops all power flow to your ship, meaning if you have no auxiliary power module installed or no warp core to refill the slot with, you'll lose power fast! The counter continues from whatever it was at when you ejected it, and then explodes in a MASSIVE detonation that can significantly damage your ship if you're too close.

3. Power, Inventory, Core Breach, Life Support Alerts
When any one of these four things need attention, there is an alert dedicated to them. The power icon appears when any module is unable to fulfill its power requirements, meaning that your power generation is no longer effective enough to keep your ship powered. This means that it is time to (1) Bring unessential systems offline, (2) Repair your warp core (the health of your core determines your ship's power output), or (3) Switch to an auxiliary power module (if installed).
The Inventory status alert appears when an active torpedo module has exhausted it's supply of selected torpedoes (unimplemented).
The core breach alert appears when a warp core breach has been triggered, and will disappear if the core is repaired or ejected.
The life support alert appears when the life support system hits 0% health or is turned offline. If life support is not repaired and brought back online within 2000 game cycles, your crew dies and you lose.

4. Repairing Your Ship
Any module may be repaired, including shields and hull integrity. Repairing a module stops it from being supplied power, stops it from functioning, and expends a lot of power to repair it. Every 5 game cycles, the module draws its current power default and gives itself 1 unit of health. For a starting ship, this means that it takes a module 250 game cycles to fully repair to 50 health, and costs 250 power to do so.
* A repairing module is treated as OFFLINE. This means that if you are repairing your shields, they will not function. If you're repairing your hull integrity, it will not give you extra damage protection. If you are repairing your warp core, it will stop generating power. The only modules that will function while being repaired are your engines (warp drive/impulse) and your weapon systems.*

5. Damage Calculation
Damage in game occurs as two factors: shield damage and hull damage. Phasers or other energy weapons deal more damage to your shields than to your hull, while torpedoes will deal more damage to your hull than your shields. Notable exceptions will be the Narada torpedoes that will deal staggering damage regardless and disruptor phasers, which will be somewhat balanced against both.
First, the current health and current power configuration of your shields are calculated and multiplied by the shield's damage resistance value. This is the amount of damage that your shield is capable of repelling at 100% health and 100% power. To start, this number is 5. Most weapons you'll encounter at first will deal 1-3 damage. If your shields are at, for example, 60% health, they will be capable of blocking only 3 damage. If you were to then set your shields to use 200% power, they would become able to block 6 damage. In this way, you can boost your systems to help you out in combat, but at a cost (see Boosting).
The shield damage value of the weapon is subtracted from the shield's health, resulting in shield damage. The calculated damage resistance value is subtracted from the weapon's hull damage. If this value becomes 0 or less at any time, we stop calculating damage.
We then read out the damage resistance value of your hull integrity module. If hull integrity is 50% or higher, that number is subtracted from the weapon damage. If hull integrity is <50% but above 0%, the damage resistance becomes 0. If hull integrity is 0%, the module's damage resistance is added to the incoming damage. This emulates a damaged hull becoming less effective at protecting the interior from damage. Any remaining damage is applied to a system currently chosen at random, but eventually to be chosen based on the direction of the incoming weapon compared to the direction of your ship, allowing you to target specific areas.

6. Boosting Systems
Any system, except the warp core, may be boosted to allow it to perform more effectively. Here's a list of what boosting a generic system will do:
Shields: Increase damage resistance
Hull integrity: increase damage resistance
Life Support: unable to be altered
Warp Core: unable to be altered
Warp Drive: Increases maximum attainable warp speed (to a max of +5 speed)
Impulse Drive: Increases maximum attainable impulse speed (to a max of +2 speed)
Sensors: Increases maximum sensor range/targeting range
Phasers: Increases phaser damage
Torpedoes: Increases torpedo speed
Transporters: Increases transporter range
* A boosted system will use power at a faster rate than it is being recharged, and eventually run out of power and stop working. Use boosting sparingly. *

7. Warp/Impulse Speeds
The ship has 4 average impulse speeds:
1 field / cycle = 1/4 impulse
2 fields / cycle = half impulse
3 fields / cycle = 3/4 impulse
4 fields / cycle = full impulse
certain ship types and a boosted impulse module will allow additional speeds < 10.
A damaged impulse module reduces the maximum impulse speed.
The ship has warp factors 1-9, with speeds in between the major warp factors. Each warp factor increases the speed by it's factor.
Warp 1 = 10 fields / cycle
Warp 2 = 12 fields / cycle
Warp 3 = 15 fields / cycle
Warp 4 = 19 fields / cycle
Warp 5 = 24 fields / cycle
Warp 6 = 30 fields / cycle
Warp 7 = 37 fields / cycle
Warp 8 = 45 fields / cycle
Warp 9 = 54 fields / cycle
boosted warp core max = 59 fields / cycle
Intermediary warp factors supported, for example, 16 fields / cycle equals Warp 3.5.
A damaged Warp Drive module decreases the maximum speed to a minimum of 10 (warp 1) unless the module is completely destroyed.



8
Update

An alpha demo is almost here. Got pretty much all the basic combat systems complete. Just have to add in phaser/torpedo sprites, rendering, and target tracking. Then work out any bugs in the firing/movement/rendering system. Here's an image with the demo opponent, a Borg sphere, rendered on screen.

9
I've been talking about it for a while. Asking questions about how to do this or that. But without any real progress.

Scroll down for a question I have about ship/terrain assets.

Well as of the past week or so, that has changed. I sat down, turned off my Minecraft (with great internal suffering) and got to work. Over the past week, I succeeded in creating the shields, the major non-combat systems, damage reception, power control, and more.

At this point in time, there is no networking implemented and the file is quite large (~15kb). Much of this is due to graphics and AI calculations which, when networking is implemented will no longer be present. The intent is also to hold graphics server-side and send the relevant sprites to the calc during runtime, which will be saved in a temporary assets file. Also, as Kerm told me that CALCnet will likely not be a thing for the CE due to differences in network protocol, I'll probably use the existing USB protocol on the CE with a computer side program to send data to the hub, which would have the ability to interact with connected CE's and CALCnet, allowing the color and monochromes to play on one server. I'll also open source this when done to allow it to be ported to the CSE.

But more on that later. I have very little left to do before I can release a demo. Basically just AI ship control, player ship control, rendering the viewscreen, and firing. In the scope of what I've done already, that shouldn't take too long.

Now, feast your eyes on some screenshots:









The Question:

This game is played in a virtual 3D world. The map objects and ships are technically 3D. My question is, would it be better, both in terms of rendering speed and data size, to create several versions of each sprite, to view the object from different angles, or to create full 3D models for the ships and the spherical map objects (the irregular objects will be rendered differently). For full 3D, I could make 16x16x16 models for each item, leading to an overhead of 4096 bytes per object, which if it's in an external assets file on the CE isn't a major issue. When this game eventually gets backwards-ported to the monochrome calcs, we'd be talking about 512 bytes per object.

If the common consensus is the latter (3d models), is there someone here who has experience making them?

10
TI Z80 / Re: Yahtzee, Axe edition RC 1
« on: July 31, 2016, 04:05:28 pm »
Sorry for the reply delay in this. Since my old calculator is broken, link wise, i cannot update this program myself so anyone who wants to can fix or modify anything needing it and repost and add their name to it.

On to the reported bugs/issues:
1. I could have sworn that was actually put in there and had no effect? I can have a look at the source later and update.
2. That is something that could be added, certainly.
3. I thought Enter was a more straightforward key for entering something lol. But if the lot of you agree it should be moved, we can move it.
4. Thats a RNG thing. I forget how I set up the seed. If memory serves, it was simply rand as provided in Axe.
5. Also, doable.
6. I was worried about screen space for a lot of stuff. In the current setup, the points tally next to the selection for the 1-6's is your indicator of whether or not you achieved that bonus. I could toss a character in it. There seems to be room.

Dice rolling: the program was already getting high in size, so i did without animations. I might make a version for the CE that is a little better.

Thanks for the feedback. Happy to finally have a decent, nice looking project out for people to use (i dont exactly count my polynomials program on that list haha)

That last issue is very strange. I thought all kinks with the SS/LS finding algorithm were worked out, but it seems to still be there. I'll look into it and report what i find.

11
TI Z80 / Re: Yahtzee, Axe edition RC 1
« on: February 11, 2016, 08:31:00 pm »
Ok, some changes.

1. A complete rework the GUI. The High and Low score is moved to the left half of the top of the screen, the combo score and bonus points are moved into an inset in that top roll.

2. The combo listing is moved down, and the selected combo box is inverted. Already used combos are rendered with an X across them. When hovered over, the scored combo for that item is rendered, rather than the point value for the current roll.

3. The last box on the top row now sums the points for the first 6.

4. Die are reset after a roll. Default is a ? symbol. Screenshot and version enclosed.

12
TI Z80 / Re: Yahtzee, Axe edition RC 1
« on: February 10, 2016, 10:15:26 am »
- highlight the combos you've used already (XOR a black square over them) so you can easily see which combos you've already used.
- Replace the 'used' text with the points you scored for that combo
I could do that.

- Perhaps up/down could move the cursor to the other row? If you want things to line up, you can make the USED/score box the same size as the YATZ box.
I could also do that. Not too concerned about lining up exactly, but we'll see.

- A way to see how many points you have in the top row (i believe it's 63 points you need to get the bonus)
- Turn off the run indicator. The hex code for bcall(_RunIndicOff) is EF7045. Axe may have another way to do this.
- It might be better to notify you that you're getting the +35, at first i thought it was a calculation glitch (eg. for 3 6's, it'd show 18+35 or something or have a text or button appear saying "BONUS").

I could create separate score and bonus boxes. However, currently, a + symbol appears to the far right of the score box when a bonus is being applied.

- After selecting a combo, it might be better to clear the dice. Also, a rolling animation would look nice :)
Sorry, but the program is already 6000 bytes. I wanted smaller, but animations are going to make the program even larger.

13
TI Z80 / Re: Yahtzee, Axe edition RC 1
« on: February 09, 2016, 10:52:43 am »
Ok, update.

- as I believe this version is stable, the b has been removed from the version string
- getKey^r switched to a getCSC loop (getKey)
- roll key changed to [2nd]. Help Screen updated to reflect this.
- Hold on Roll 0 bug fixed
- Multiple Yahtzees changed to a Yahtzee Bonus

Screenshot updated has some graphical glitches I think root in jStified, since they do not occur at all on my calculator. I'll poke Kerm and see what he has to say.

14
TI Z80 / Re: Yahtzee, Axe edition RC 1
« on: February 08, 2016, 09:56:29 pm »
Can I then store getKey to a variable? Like 
Code: [Select]
EndIf getKey->G

15
TI Z80 / Re: Yahtzee, Axe edition RC 1
« on: February 08, 2016, 08:29:36 pm »
Fixes for everything except the [2nd] + [ON] leak. GUI improvement. I'm waiting for Runer, so I can ask him about some of the other Axe keyscanning options.

Pages: [1] 2 3 ... 61